Practice distributed tracing vocabulary: traces, spans, context propagation, instrumentation, and tools like Jaeger, Zipkin, and Grafana Tempo.
0 / 10 completed
1 / 10
What is a 'trace' in distributed tracing?
A trace represents the entire lifecycle of a single request as it travels through multiple services. It's composed of spans — each representing a single operation within the request's path.
2 / 10
'The ___ for the DB query took 280ms.' Which noun represents a single operation within a trace?
A 'span' represents a named, timed operation within a trace. Each span has a start time, duration, and metadata (tags/attributes). Multiple spans make up a trace.
3 / 10
What is 'context propagation' in distributed tracing?
Context propagation means forwarding trace context (trace ID, span ID, sampling flags) in request headers (like W3C traceparent) so downstream services can attach their spans to the same trace.
4 / 10
'We added ___ to the new service.' What is added to enable tracing?
'Instrumentation' is the code (or auto-instrumented library) that creates spans, sets attributes, and propagates context. Adding instrumentation to a service makes it visible in distributed traces.
5 / 10
Which three tools are commonly used for distributed tracing backends?
Jaeger (CNCF), Zipkin (open source, Twitter origin), and Grafana Tempo are the most common open-source distributed tracing backends. They store and visualize trace data collected via OpenTelemetry or native SDKs.
6 / 10
During a code review of the new payment service, Sarah mentioned that 'we need to add trace IDs to every request.' What is the primary purpose of adding trace IDs in this context?
Trace IDs are crucial for linking related operations together. They act as a unique identifier that's propagated through all services involved in a single transaction. This allows the distributed tracing system to group spans – representing individual operations – into a single trace, providing a comprehensive view of the request's journey. Adding them is about correlation, not just debugging.
7 / 10
You're reviewing a Slack message from Alex in DevOps: 'The trace context got lost during the API call to the external authentication service!'. What does 'trace context getting lost' most likely refer to?
'Trace context' contains vital information like the trace ID and baggage – used to link spans. When this context is lost, the system cannot correctly group related operations into a single trace. This happens when the trace ID isn't properly passed along during inter-service communication, typically via HTTP headers.
8 / 10
In a PR description for adding tracing to the order processing microservice, you see the following: 'We've implemented Baggage propagation to ensure all spans are correctly associated with the originating request.' What is the main function of 'Baggage propagation' within distributed tracing?
Baggage propagation is the mechanism for carrying non-trace ID information (like user IDs, session tokens, or other service-specific attributes) alongside the trace. This ensures that spans related to a single request are correctly associated and can be correlated even if different services handle them.
9 / 10
During a standup meeting, David says: 'We're using OpenTelemetry to instrument our backend.' What is the primary role of OpenTelemetry in this scenario?
OpenTelemetry provides a vendor-neutral set of APIs and SDKs to instrument applications and collect telemetry data. It allows you to generate traces from your code and export them to various backends (like Jaeger or Zipkin) without being locked into a specific tracing solution.
10 / 10
You're configuring a new distributed tracing system. Which of the following components is MOST likely to be used as a backend for storing and querying traces?
Trace backends are specialized systems designed to efficiently store and query large volumes of trace data. Jaeger and Zipkin are popular open-source options that provide indexing, querying, and visualization capabilities tailored for distributed tracing use cases – they aren't designed for general database workloads.
What will I practise in "Distributed Tracing Vocabulary"?
This module focuses on Observability Engineering — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Observability Engineering exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around observability engineering — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Observability Engineering exercises?
See the Observability Engineering hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.