Bird
0
0

A developer notices that Correlation IDs are missing in logs of downstream services. Which is the most likely cause?

medium📝 Analysis Q14 of 15
Microservices - Monitoring and Observability
A developer notices that Correlation IDs are missing in logs of downstream services. Which is the most likely cause?
AThe Correlation ID header is not forwarded in outgoing requests
BThe Correlation ID is too long and gets truncated
CThe logging system does not support string messages
DThe services are using different programming languages
Step-by-Step Solution
Solution:
  1. Step 1: Understand Correlation ID propagation

    Correlation IDs must be passed along with every outgoing request to maintain traceability.
  2. Step 2: Identify common propagation mistake

    If downstream logs miss the ID, it usually means the header was not forwarded properly.
  3. Final Answer:

    The Correlation ID header is not forwarded in outgoing requests -> Option A
  4. Quick Check:

    Missing ID in logs = header not forwarded [OK]
Quick Trick: Always forward Correlation ID header downstream [OK]
Common Mistakes:
MISTAKES
  • Blaming length truncation without evidence
  • Assuming logging system limitation
  • Thinking language differences cause missing IDs

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Microservices Quizzes