KCNA Cloud Native Observability Practice Question
What is context propagation in distributed tracing?
⚠ Common exam trap
The trap is conflating the different pillars of tracing — sampling, storage, visualization, and propagation — and picking a plausible-sounding but functionally distinct option like sampling or storage.
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
✓
Carrying trace context (trace ID, span ID) across services
Context propagation is the mechanism by which trace context — primarily the trace ID and the current span ID — is passed from one service to the next across network calls, so all spans belonging to the same request are stitched into a single distributed trace. This is typically done via HTTP headers (e.g., W3C `traceparent`) or message metadata. Without it, each service would create an isolated trace and the end-to-end picture would be lost.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Sampling traces to reduce data volume
Why it's wrong here
Sampling decides which traces are retained, not how trace and span identifiers travel between services. Context propagation injects and extracts trace context across process and network boundaries, typically via headers, so spans join one trace. Sampling would be the right concern when reducing storage or ingest volume.
- ✗
Visualizing traces in a user interface
Why it's wrong here
A UI renders completed traces; it plays no part in carrying trace context between services. Context propagation transfers trace and span IDs across process boundaries, usually through request headers, so downstream spans attach to the originating trace. Visualisation would be the correct focus when presenting trace data to engineers.
- ✓
Carrying trace context (trace ID, span ID) across services
Why this is correct
Context propagation is the mechanism that carries trace context, specifically the trace ID and span ID, across service boundaries. Each downstream service continues the same trace rather than starting a new one, which is what makes a distributed trace reconstructable end to end.
- ✗
Storing trace data in a centralized database
Why it's wrong here
Centralised storage is where spans are persisted for querying, not how trace context travels between services. It would be the correct concern when designing a tracing backend, but context propagation is the mechanism passing trace and span identifiers across process and network boundaries.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-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 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.