Practise vocabulary for distributed trace sampling: head vs tail sampling, sample rate, retention of error traces, and probabilistic sampling.
0 / 10 completed
1 / 10
Deciding whether to keep a trace at the moment it starts, before knowing its outcome, is ___ sampling.
Head-based sampling decides up front (e.g. keep 10% of traces) cheaply, but it can't preferentially keep traces that later turn out to be errors.
2 / 10
Deciding which traces to keep after they complete, so you can retain slow or failed ones, is ___ sampling.
Tail-based sampling buffers spans and decides at the end, letting you keep all error/high-latency traces while dropping boring ones.
3 / 10
The fraction of traces retained out of all generated is the ___.
The sample rate (e.g. 1%) controls cost and data volume; lower rates save money but reduce visibility into rare events.
4 / 10
A policy that always keeps traces containing an error regardless of base rate is called error ___.
Keeping all error traces ensures you never sample away the failures you most need to debug, even at a low overall sample rate.
5 / 10
Keeping each trace with a fixed independent probability is ___ sampling.
Probabilistic sampling keeps traces with a set chance (e.g. p=0.1), giving a statistically representative subset at predictable volume.
6 / 10
Sarah from QA just flagged a slow API response during testing. She suggests using trace sampling to reduce the load on our system while still investigating potential bottlenecks. Which sampling strategy would be most appropriate for Sarah's immediate needs?
Consider: We need to quickly identify and analyze potentially problematic traces without overwhelming the monitoring infrastructure.
Fixed Percentage Sampling is the most suitable initial response. It's straightforward to implement and immediately captures a consistent sample size, allowing for a quick overview. Adaptive sampling requires more complex scoring logic initially, while error-based sampling could flood the system with irrelevant traces, and time decay might miss critical issues occurring recently. This approach provides an immediate, manageable snapshot of trace data.
7 / 10
David, the performance engineer, is reviewing a new PR that implements a complex distributed tracing system. He notes that the team is using a '5%' trace retention policy. What does this typically indicate?
The system automatically removes traces after 5% of requests have been processed.
'5%' in this context refers to a percentage retention rate. It means that out of all the traces created, 5% are kept for further examination. The other options misinterpret '5%' as either a time duration or a latency threshold. This is a common phrasing used when describing trace sampling strategies.
8 / 10
During a standup meeting, Maria explains that the team has been using trace sampling to monitor its microservices. She states, 'We're retaining 20% of traces with high latency.' What metric is Maria primarily referencing?
Consider: This indicates how the sampling strategy is influenced by performance.
Maria is referring to the 'error rate' or 'latency rate', as defined by the sampling policy. The 20% retention reflects that 20% of the traces with the highest latencies are kept for investigation – this is a key parameter in controlling the cost and effectiveness of trace sampling. The other options represent different metrics related to tracing but aren't directly linked to the retention rate itself.
9 / 10
Ben is designing a new trace sampling policy for an e-commerce platform. He wants to automatically discard traces that consistently result from failed transactions. What type of sampling strategy would best align with this goal?
The system should prioritize retaining traces related to specific events.
Error-based sampling is the most appropriate choice because it specifically targets and retains traces that represent problematic events – failed transactions in this case. This proactive approach ensures that resources aren't wasted analyzing irrelevant traces. The other options don't directly address the need to focus on error conditions.
10 / 10
Chloe is investigating a performance issue in a distributed system and notices that the team has implemented trace sampling with a probability of 0.5 for retaining each trace. What does this mean?
Consider: This describes how the traces are selected for retention.
A probability of 0.5 (or 50%) indicates an independent sampling approach. This means that each trace has an equal likelihood of being selected for retention, irrespective of its latency, error status, or any other characteristics. This contrasts with adaptive sampling which uses dynamic rules, and error-based sampling which prioritizes errors.
What will I practise in "Trace Sampling Strategies 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.