Microservices - Monitoring and ObservabilityIn distributed tracing, which HTTP header is typically used to carry the trace identifier between microservices?AtraceparentBAuthorizationCContent-TypeDUser-AgentCheck Answer
Step-by-Step SolutionSolution:Step 1: Identify trace context propagation headerThe W3C Trace Context specification defines 'traceparent' as the standard header.Step 2: Eliminate unrelated headers'Authorization' is for auth, 'Content-Type' for payload type, 'User-Agent' for client info.Final Answer:traceparent -> Option AQuick Check:Trace context uses 'traceparent' header [OK]Quick Trick: 'traceparent' header carries trace IDs per W3C spec [OK]Common Mistakes:MISTAKESUsing 'Authorization' header for trace contextConfusing 'Content-Type' with tracing infoAssuming 'User-Agent' carries trace data
Master "Monitoring and Observability" in Microservices9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepArchTryChallengeDesignRecallScale
More Microservices Quizzes Authentication and Authorization - API key management - Quiz 14medium Authentication and Authorization - Role-based access control - Quiz 5medium Authentication and Authorization - Role-based access control - Quiz 7medium Event-Driven Architecture - Event types (domain, integration, notification) - Quiz 8hard Event-Driven Architecture - Event types (domain, integration, notification) - Quiz 10hard Event-Driven Architecture - Idempotent event consumers - Quiz 5medium Event-Driven Architecture - Event-driven vs request-driven - Quiz 7medium Monitoring and Observability - Dashboards (Grafana) - Quiz 2easy Monitoring and Observability - Correlation IDs - Quiz 10hard Resilience Patterns - Timeout pattern - Quiz 3easy