You design a microservices system where each service generates its own Correlation ID if none is provided. What is a potential problem with this approach?

hard📝 Trade-off Q15 of 15

Microservices - Monitoring and Observability

AIt ensures better security by hiding original IDs

BIt improves performance by reducing header size

CIt simplifies logging by having unique IDs per service

DIt breaks the traceability because multiple IDs exist for the same request

Step-by-Step Solution

Solution:

Step 1: Analyze the effect of generating new IDs per service
If each service creates a new Correlation ID, the original request's trace is lost.
Step 2: Understand impact on traceability
Multiple different IDs for one request make it impossible to follow the full request path across services.
Final Answer:
It breaks the traceability because multiple IDs exist for the same request -> Option D
Quick Check:
Multiple IDs = broken traceability [OK]

Quick Trick: One Correlation ID per request across services only [OK]

Common Mistakes:

MISTAKES

Thinking multiple IDs improve security
Assuming performance improves with new IDs
Believing unique IDs per service simplify logs

Master "Monitoring and Observability" in Microservices

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Arch Try Challenge Design Recall Scale

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Microservices Quizzes

You design a microservices system where each service generates its own Correlation ID if none is provided. What is a potential problem with this approach?

Step 1: Analyze the effect of generating new IDs per service

Step 2: Understand impact on traceability

Final Answer:

Quick Check:

Want More Practice?