Microservices - Monitoring and Observability
Why should downstream microservices avoid generating new Correlation IDs if one is already present in the incoming request?
Why should downstream microservices avoid generating new Correlation IDs if one is already present in the incoming request?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand Correlation ID purpose
Correlation IDs link logs from all services handling the same request.Step 2: Impact of generating new IDs downstream
If downstream services generate new IDs, the original request trace is fragmented, making debugging difficult.Step 3: Evaluate other options
New IDs do not inherently improve security, reduce payload size, or prevent duplicate logging.Final Answer:
Generating new IDs breaks the traceability of the original request across services -> Option DQuick Check:
New IDs break request traceability [OK]
Quick Trick: New Correlation IDs break request traceability [OK]
Common Mistakes:
MISTAKES- Believing new IDs enhance security
- Thinking new IDs reduce payload size
- Assuming new IDs prevent duplicate logs
Master "Monitoring and Observability" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes