Book Image

The KCNA Book

By : Nigel Poulton
Book Image

The KCNA Book

By: Nigel Poulton

Overview of this book

There is a huge benefit in building small, specialized, single-purpose apps that can self-heal, auto scale, and update regularly without needing downtime. Kubernetes and cloud-native technologies come in handy in building such apps. Possessing the knowledge and skills to leverage Kubernetes can positively enhance possibilities in favor of architects who specialize in cloud-native microservices applications. ‘The KCNA Book’ is designed to help those working in technology with a passion to become certified in the Kubernetes and Cloud-Native Associate Exam. You will learn about containerization, microservices, and cloud-native architecture. You will learn about Kubernetes fundamentals and container orchestration. The book also sheds light on cloud-native application delivery and observability. It focuses on the KCNA exam domains and competencies, which can be applied to the sample test included in the book. Put your knowledge to the test and enhance your skills with the all-encompassing topic coverage. Upon completion, you will begin your journey to get the best roles, projects, and organizations with this exam-oriented book.
Table of Contents (12 chapters)
9
8: Sample test
Appendix B: Sample Test answers

Chapter 6: Cloud native observability

Question 1, answer D
Telemetry is log data, metrics, and traces that are output from a system.
Question 2, answers A, B, C
The three main classes of telemetry data are logs, metrics, and traces.
Question 3, answer D
Prometheus stores data in a timeseries format.
Question 4, answer B
Telemetry is used to troubleshoot and tweak performance of a system.
Question 5, answers B
The OpenTelemetry projects provides instrumentation and specifications for cloud native observability.
Question 6, answer B
Log data is application output that is usually output as text or JSON.
Question 7, answer C
Log events are often categorised from lowest to highest severity in the following order: info > warning > error > critical.
Question 8, answer A
High verbosity generates more output than low verbosity.
Question 9, answer C
Debug level is the most verbose and intended to dump out as much data as possible.
Question 10, answers...