OpenTelemetry: Diagnose Broken Trace Context Propagation

OpenTelemetry: Diagnose Broken Trace Context Propagation

Choose one answer. All questions are included, with explanations after checking. No time limit. Training target: 24/30. A scenario-based test for developers diagnosing W3C trace headers, OpenTelemetry context handling, HTTP and message carriers, parent relationships, tracestate, sampling and baggage. Uses version-00 header rules and stable OpenTelemetry APIs; excludes vendor setup, full messaging semantic conventions and certification coverage. Sources: https://www.w3.org/TR/trace-context/ https://opentelemetry.io/docs/specs/otel/context/api-propagators/ https://opentelemetry.io/docs/specs/otel/trace/api/ https://opentelemetry.io/docs/specs/otel/context/ https://opentelemetry.io/docs/concepts/signals/baggage/
1 of 30
Exported span records show server B with the same trace ID as client A and parent span ID equal to A’s span ID. A UI still omits the connecting line. Which conclusion is best supported?