KCNA Cloud Native Observability Practice Question
A developer is investigating a performance issue in a microservices application. They want to trace a single request as it flows through multiple services, including a database call. Which OpenTelemetry concept allows them to correlate all these operations under a single logical unit?
⚠ Common exam trap
It's easy for candidates to confuse a span with a trace; a span is a single operation, while a trace is the complete end-to-end journey of a request.
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
✓
Trace
In OpenTelemetry, a trace is the overarching structure that ties together all spans associated with a single request. Each span represents a unit of work, and spans within the same trace share a trace ID, enabling correlation across service boundaries. This allows developers to visualize the entire request flow, including database calls, and identify bottlenecks or failures. Metrics and logs serve different purposes and do not provide this end-to-end request context.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Trace
Why this is correct
A trace represents the entire journey of a request through a distributed system, composed of multiple spans that share a common trace ID. It allows developers to see the full path and timing of a request across services. This is exactly what is needed to correlate operations from different services and a database call under a single logical unit.
- ✗
Span
Why it's wrong here
A span represents a single operation within a trace, such as an HTTP request or a database query. While spans are the building blocks of a trace, they do not by themselves correlate multiple operations across services. The question asks for the concept that groups all operations for a request, which is a trace, not an individual span.
- ✗
Metric
Why it's wrong here
Metrics are numerical measurements aggregated over time, such as request counts or latency percentiles. They are not designed to track individual requests across services. Metrics provide aggregate views but lack the context to follow a single request through a distributed system, so they cannot fulfill the requirement for request-level correlation.
- ✗
Log record
Why it's wrong here
A log record is a timestamped message emitted by a service, often including contextual details. While logs can be correlated using trace IDs, they are not the primary mechanism for tracing a request's path. Logs are discrete events and do not inherently provide the causal relationships between operations that a trace does.
Go deeper
Related to this question
About these practice questions
One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
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.