Observability KCNA Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A startup has services written in Python, Go, and Java. They want to collect metrics, logs, and traces from all services and send them to a central backend. They want to avoid vendor lock-in and use a single standard for instrumentation. Which approach should they take?

   • AWrite custom instrumentation code in each service to send data to a central database.
   • BUse a different proprietary SDK for each language and send data directly to the vendor's backend.
   • CUse OpenTelemetry SDKs in each service to generate telemetry and export it to a collector.
   • DUse Prometheus client libraries for metrics, OpenTracing for traces, and a logging library for logs.
   Reveal Solution Discussion Select an answer first
2. 17expert · hard · select all that apply

   A team is building an observability solution for a microservices application. They want to ensure they can effectively troubleshoot issues that involve multiple services. Which of the following are essential components of a comprehensive observability strategy? (Select all that apply.)

   • ACollecting logs from all services in a centralized location.
   • BEnsuring that all services are instrumented with the same programming language.
   • CCollecting metrics that indicate system health, such as request rates and error rates.
   • DUsing a single tool that provides all three pillars in one platform.
   • EImplementing distributed tracing to follow requests across services.
   Check answers Discussion Select an answer first
4. 18foundation · easy

   Why is observability particularly important for cloud native applications?

   • ABecause cloud native applications always run in containers, which cannot be monitored
   • BBecause cloud providers require observability for billing purposes
   • CBecause microservices are distributed and ephemeral, making it harder to predict all failure modes in advance
   • DBecause observability eliminates the need for logging and metrics
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A company has an existing observability stack using Prometheus for metrics and Jaeger for traces. They want to adopt OpenTelemetry to standardize instrumentation across new services. They also want to keep using their existing backends. What is the best approach?

   • AReplace Prometheus and Jaeger with a single OpenTelemetry backend.
   • BUse OpenTelemetry SDKs to send data directly to Prometheus and Jaeger without a collector.
   • CUse OpenTelemetry only for traces and keep using Prometheus client libraries for metrics.
   • DInstrument services with OpenTelemetry SDKs and configure the OpenTelemetry Collector to export metrics to Prometheus and traces to Jaeger.
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A team is implementing distributed tracing for a microservices application. They want to ensure that traces are propagated across service boundaries. Which of the following is essential for this to work?

   • AThe tracing backend must be deployed in the same Kubernetes cluster as the services.
   • BAll services must be written in the same programming language.
   • CEach service must forward the trace context (trace ID and span ID) in the headers of outgoing requests.
   • DEach service must write its logs to the same file.
   Reveal Solution Discussion Select an answer first