Build fluency in the vocabulary of tying logs from many services back to one originating request.
0 / 5 completed
1 / 5
At standup, a dev mentions attaching a unique identifier to a request at its entry point and propagating it through every downstream service call, so logs from different services can be tied back to that same request. What is this identifier called?
A correlation ID is a unique identifier attached to a request at its entry point and propagated through every downstream service call, letting logs from disparate services be tied back to that same original request. A timestamp recorded independently by each service is ambiguous under concurrent traffic, since many requests can share nearly the same timestamp. This shared identifier is what makes tracing one request's full path through a distributed system actually feasible.
2 / 5
During a design review, the team wants the correlation ID carried not just through a synchronous service call but also through an asynchronous message placed onto a queue. Which capability supports this?
Propagation of the correlation ID across both a synchronous service call and an asynchronous queue message ensures the same identifier survives the entire request's journey, however it travels between services. Propagating it only through synchronous calls loses the connection the moment a request's processing crosses into an async, queue-based boundary. This broader propagation is what keeps a correlation ID useful across a genuinely distributed, mixed synchronous-and-asynchronous system.
3 / 5
In a code review, a dev notices every structured log line emitted by a service includes the correlation ID as one of its fields, rather than logging it only occasionally. What does this represent?
Including the correlation ID as a consistent field in every structured log line means every single log entry related to a request can be found and grouped together, no matter which service emitted it. Logging it only occasionally leaves gaps where a log line can't be tied back to its originating request at all. This consistent inclusion is what lets a team reconstruct a request's complete path across a distributed system's logs.
4 / 5
An incident report shows a production bug took hours to diagnose because one service in the call chain dropped the correlation ID header, breaking the ability to trace that specific request end-to-end across the remaining services. What practice would prevent this?
Enforcing correlation ID propagation consistently across every service in the call chain, including through an asynchronous boundary, prevents exactly the kind of broken trace this incident describes. Allowing any individual service to drop it without consequence leaves the entire tracing effort fragile, since one gap breaks the chain for every service downstream of it. This consistent enforcement is what makes a correlation ID reliably useful during an actual production investigation.
5 / 5
During a PR review, a teammate asks why the team propagates a dedicated correlation ID through every service instead of just matching up log entries across services using their recorded timestamps. What is the reasoning?
Timestamp-based matching is ambiguous under concurrent traffic, since many unrelated requests can share nearly identical timestamps, especially in a busy production system. A correlation ID uniquely ties every related log line to one specific request regardless of how many other requests are happening at the same moment. The tradeoff is the discipline needed to ensure every service in a call chain actually propagates the identifier correctly, rather than silently dropping it.
What does the "Correlation ID Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to correlation id vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.