- A
Monitor CPU and memory metrics from kube-state-metrics and correlate with latency.
Why wrong: Resource metrics may not directly indicate request latency.
- B
Increase log verbosity for all services and search for error messages.
Why wrong: Logs may not capture latency across services.
- C
Implement distributed tracing using tools like Jaeger or Zipkin to trace requests across services.
Distributed tracing tracks request flow and identifies slow components.
- D
Check node-level metrics using Prometheus Node Exporter.
Why wrong: Node metrics are too granular for service-level latency.
Question 905 of 997
Distributed Tracing for Latency — Microservices Root Cause Analysis
This KCNA practice question tests your understanding of cloud native observability. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is running a microservices application on a Kubernetes cluster. They have noticed that one of the services, 'payment-api', is experiencing intermittent high latency. The team wants to identify the root cause without modifying the application code. Which approach should they take?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement distributed tracing using tools like Jaeger or Zipkin to trace requests across services.
Option C is correct because distributed tracing with tools like Jaeger or Zipkin allows you to follow a single request as it traverses multiple microservices, identifying exactly which service or call introduces latency. This approach does not require code changes (if the service mesh or sidecar proxy handles instrumentation) and is specifically designed to pinpoint performance bottlenecks in distributed systems, unlike CPU/memory metrics or log analysis which cannot trace a request's end-to-end path.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monitor CPU and memory metrics from kube-state-metrics and correlate with latency.
Why it's wrong here
Resource metrics may not directly indicate request latency.
- ✗
Increase log verbosity for all services and search for error messages.
Why it's wrong here
Logs may not capture latency across services.
- ✓
Implement distributed tracing using tools like Jaeger or Zipkin to trace requests across services.
Why this is correct
Distributed tracing tracks request flow and identifies slow components.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Check node-level metrics using Prometheus Node Exporter.
Why it's wrong here
Node metrics are too granular for service-level latency.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between observability tools that provide request-level context (distributed tracing) versus aggregate resource metrics (kube-state-metrics, Node Exporter) or unstructured logs, leading candidates to mistakenly choose CPU/memory correlation or log analysis for pinpointing intermittent latency in a microservices architecture.
Detailed technical explanation
How to think about this question
Distributed tracing works by injecting a unique trace ID into each request at the ingress point, which is then propagated via HTTP headers (e.g., Zipkin B3 propagation or W3C Trace-Context) across all service calls. Each service records spans with start and end timestamps, allowing tools like Jaeger to reconstruct the full call graph and calculate per-span latency. In a real-world scenario, a payment-api service might show high latency only when a downstream fraud-check service times out due to a slow database query, which would be invisible in CPU or log metrics but clearly visible as a single long span in the trace.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Cloud Native Observability — study guide chapter
Learn the concepts, then practise the questions
- →
Cloud Native Observability practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this KCNA question test?
Cloud Native Observability — This question tests Cloud Native Observability — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement distributed tracing using tools like Jaeger or Zipkin to trace requests across services. — Option C is correct because distributed tracing with tools like Jaeger or Zipkin allows you to follow a single request as it traverses multiple microservices, identifying exactly which service or call introduces latency. This approach does not require code changes (if the service mesh or sidecar proxy handles instrumentation) and is specifically designed to pinpoint performance bottlenecks in distributed systems, unlike CPU/memory metrics or log analysis which cannot trace a request's end-to-end path.
What should I do if I get this KCNA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More KCNA practice questions
- Which CNCF project provides a graduated service mesh implementation that includes features like traffic management, secu…
- A pod in the 'production' namespace is in a CrashLoopBackOff state. The pod has been running successfully for several da…
- You need to ensure that a pod runs on a node with SSD storage. How can you achieve this?
- Match each Kubernetes resource to its primary purpose.
- Match each Kubernetes security concept to its definition.
- Which three of the following are valid methods to create or update resources in Kubernetes? (Choose three.)
Last reviewed: Jun 30, 2026
This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.