Master the IT-English vocabulary of distributed tracing: traces, spans, trace context propagation, latency and sampling.
0 / 10 completed
1 / 10
In distributed tracing, what is a 'trace'?
A trace captures the whole journey of a request across services, tying the operations together.
2 / 10
What is a 'span' within a trace?
A span represents one operation (with start/end time); spans nest to form the full trace.
3 / 10
Services pass a 'trace context' between them. Why?
Propagating the trace context (trace ID, span ID) lets the backend stitch spans into a single trace.
4 / 10
An engineer finds a service adding high 'latency' in the trace. What does latency mean?
Latency is the time a span takes; tracing pinpoints which service contributes the most delay.
5 / 10
Which sentence correctly uses 'sampling'?
Sampling records only a subset of traces to limit performance and storage overhead.
6 / 10
During a code review of the new user onboarding microservice, Sarah mentions that the trace shows a long delay between the initial API call and the database query. She asks Mark, 'What's the significance of this 'span' duration?'
The key here is understanding that a 'span' represents a single operation or unit of work within the distributed trace. A common misconception is to think spans only relate to database calls; they can represent any code execution – an API call, a function invocation, or even a message queue interaction. The duration reflects the time spent on *that specific* activity.
7 / 10
In a Slack channel discussing performance issues with our payment processing service, David writes: 'I'm seeing high latency in the trace, and I've enabled full sampling to capture more data.' What is the primary purpose of enabling 'full sampling'?
'Full sampling' means that *every* request passing through the service will be captured and added to the trace. This is crucial when troubleshooting high latency because it provides a complete picture of the entire flow, rather than relying on probabilistic sampling which might miss critical traces. It's important to note that this increases trace volume significantly.
8 / 10
During a standup meeting, Alex reports: 'We're using OpenTelemetry and setting the `trace.sampled` context header to 0.1 for our microservices.' What is Alex primarily configuring?
The `trace.sampled` context header controls the *sampling rate* of distributed tracing. Setting it to 0.1 (10%) means that only 10% of requests will be fully traced – a common strategy for reducing trace volume while still providing valuable insights during troubleshooting. This is a crucial parameter for balancing observability and performance.
9 / 10
You're reviewing the PR description for a change to our order processing service that incorporates distributed tracing. The description states: 'We've added trace context propagation and are using Zipkin to visualize the traces.' What does 'trace context propagation' refer to?
'Trace context propagation' is the fundamental process of automatically passing trace information (like Trace ID and Span ID) across service boundaries. This allows each span to be correlated with its parent spans, forming a complete picture of the request flow – without developers manually managing this context in every service. It's the backbone of distributed tracing.
10 / 10
The trace for an e-commerce transaction shows a large delay between the 'Checkout' API call and the 'Payment Processing' service. Analyzing the trace data, you identify that the Payment Processing service is consistently adding excessive latency. Which of the following best describes this latency?
Latency, in the context of distributed tracing, specifically refers to the time taken for a *single* operation (a 'span') to complete. It's a key metric used to identify potential bottlenecks and performance issues within your system's trace. High latency indicates that the Payment Processing service is taking longer than expected to fulfill its task – something you would investigate further.
What will I practise in "Distributed Tracing Vocabulary"?
This module focuses on Microservices Language — 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 Microservices Language exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around microservices language — 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 Microservices Language exercises?
See the Microservices Language 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.