KCNA Cloud Native Observability Practice Question
Which THREE of the following are valid use cases for distributed tracing in a microservices architecture?
⚠ Common exam trap
The KCNA exam often tests the distinction between observability pillars (metrics, logs, traces) and expects candidates to recognize that distributed tracing is not a catch-all for monitoring or logging tasks, so the trap is confusing request-level tracing with infrastructure metrics or detailed error logging.
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
✓
Understanding the dependency graph between microservices
Distributed tracing is designed to track the flow of a single request across multiple microservices, recording timing and causality. Option B is correct because tracing systems like Jaeger or Zipkin automatically build a dependency graph by analyzing the parent-child relationships between spans, which reveals how services interact. This is a core use case for understanding service topology and identifying bottlenecks in a distributed system.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Monitoring CPU and memory usage of each service instance
Why it's wrong here
Resource metrics are better for Prometheus.
- ✓
Understanding the dependency graph between microservices
Why this is correct
Traces reveal service call relationships.
- ✓
Pinpointing the root cause of an error in a distributed transaction
Why this is correct
Tracing shows where errors occur in the flow.
- ✓
Identifying which service contributes the most latency to an end-user request
Why this is correct
Tracing shows time spent in each span.
- ✗
Capturing detailed error messages and stack traces
Why it's wrong here
Distributed tracing focuses on propagating trace context across service boundaries to reconstruct end-to-end request flows, not on capturing the payload of individual errors. Detailed error messages and stack traces belong to structured logging or exception-handling frameworks, which record local failure details without the cross-service correlation identifiers that tracing requires. This option is tempting because observability tools often bundle tracing with logging, but the specific mechanism of trace propagation—span IDs and parent-child relationships—is absent from raw error capture.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 833-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.