- A
Install the Application Insights SDK on all three services and ensure W3C Trace Context header propagation is enabled for both HTTP calls and Service Bus messages
The SDK propagates the traceparent header on outgoing HTTP requests automatically. For Service Bus, the SDK injects and reads correlation properties in the message's ApplicationProperties collection. With the same operation ID flowing through all three services, Application Insights assembles the calls into a single end-to-end trace in the Application Map and end-to-end transaction view.
- B
Use the same Application Insights instrumentation key for all three services — no additional configuration is needed
Why wrong: Sharing an instrumentation key sends all telemetry to the same resource but does not automatically correlate traces. Without header propagation, each service generates its own independent operation IDs, so the calls appear unrelated even in the same Application Insights resource.
- C
Add a custom x-correlation-id header in each service and log it with TelemetryClient.TrackEvent
Why wrong: A custom header logged as a custom event produces correlated log entries but does not integrate with Application Insights' built-in distributed tracing model. The Application Map, end-to-end transaction view, and dependency diagrams require the SDK's native W3C correlation, not custom event logging.
- D
Enable Azure Monitor cross-resource queries and write a KQL join across all three services' logs
Why wrong: KQL cross-resource joins can correlate log data after the fact but do not create live distributed trace relationships. This approach requires manual query authoring for every investigation and does not produce the automatic visual correlation that W3C Trace Context provides.
Quick Answer
The correct answer is to install the Application Insights SDK on all three services and ensure W3C Trace Context header propagation is enabled for both HTTP calls and Service Bus messages. This is required because distributed tracing correlation across microservices depends on a shared trace ID, which the W3C Trace-Context standard (via traceparent and tracestate headers) propagates through synchronous HTTP calls and asynchronous messaging like Service Bus. Without this standard, each service generates its own independent trace ID, breaking the parent-child relationship needed for a single end-to-end view. On the AZ-204 exam, this tests your understanding of telemetry correlation in distributed systems, a common scenario where candidates mistakenly assume Application Insights auto-magically links traces across different service types. A key trap is forgetting that Service Bus messages require explicit header propagation—they don’t inherit HTTP context. Memory tip: think “W3C for Woven Context”—the standard weaves separate service traces into one continuous thread.
AZ-204 Practice Question: Distributed tracing correlation across App…
This AZ-204 practice question tests your understanding of monitor, troubleshoot, and optimize azure solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: distributed tracing. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Three microservices collaborate on a single user transaction: an App Service API, an Azure Function that processes a Service Bus message, and a downstream storage service. Traces appear separately in Application Insights with no parent-child relationship. What is needed to correlate all three into a single end-to-end trace?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Install the Application Insights SDK on all three services and ensure W3C Trace Context header propagation is enabled for both HTTP calls and Service Bus messages
Option A is correct because distributed tracing across HTTP and asynchronous messaging requires the Application Insights SDK on each service and propagation of the W3C Trace-Context standard (traceparent and tracestate headers). This ensures that the App Service API, Azure Function, and downstream storage service share a single trace ID, enabling Application Insights to correlate all telemetry into one end-to-end transaction view.
Key principle: distributed tracing
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Install the Application Insights SDK on all three services and ensure W3C Trace Context header propagation is enabled for both HTTP calls and Service Bus messages
Why this is correct
The SDK propagates the traceparent header on outgoing HTTP requests automatically. For Service Bus, the SDK injects and reads correlation properties in the message's ApplicationProperties collection. With the same operation ID flowing through all three services, Application Insights assembles the calls into a single end-to-end trace in the Application Map and end-to-end transaction view.
Related concept
distributed tracing
- ✗
Use the same Application Insights instrumentation key for all three services — no additional configuration is needed
Why it's wrong here
Sharing an instrumentation key sends all telemetry to the same resource but does not automatically correlate traces. Without header propagation, each service generates its own independent operation IDs, so the calls appear unrelated even in the same Application Insights resource.
- ✗
Add a custom x-correlation-id header in each service and log it with TelemetryClient.TrackEvent
Why it's wrong here
A custom header logged as a custom event produces correlated log entries but does not integrate with Application Insights' built-in distributed tracing model. The Application Map, end-to-end transaction view, and dependency diagrams require the SDK's native W3C correlation, not custom event logging.
- ✗
Enable Azure Monitor cross-resource queries and write a KQL join across all three services' logs
Why it's wrong here
KQL cross-resource joins can correlate log data after the fact but do not create live distributed trace relationships. This approach requires manual query authoring for every investigation and does not produce the automatic visual correlation that W3C Trace Context provides.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume sharing an instrumentation key is sufficient for correlation, overlooking the necessity of W3C Trace-Context header propagation across both synchronous HTTP and asynchronous messaging protocols.
Detailed technical explanation
How to think about this question
Under the hood, the W3C Trace-Context specification defines the traceparent header (e.g., '00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01') to carry the trace ID, span ID, and trace flags. Application Insights SDKs automatically propagate this header across HTTP calls and Service Bus messages when configured, creating a hierarchical span tree. In a real-world scenario, if the Azure Function uses a Service Bus trigger, the SDK must extract the traceparent from the message's application properties to continue the trace from the App Service API's outgoing call.
KKey Concepts to Remember
- distributed tracing
- W3C Trace Context
- Application Insights correlation
- cross-service request tracing
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
distributed tracing
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review distributed tracing, then practise related AZ-204 questions on the same topic to reinforce the concept.
- →
Monitor, troubleshoot, and optimize Azure solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Monitor, troubleshoot, and optimize Azure solutions practice questions
Targeted practice on this topic area only
- →
All AZ-204 questions
997 questions across all exam domains
- →
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
- →
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-204 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Develop Azure compute solutions practice questions
Practise AZ-204 questions linked to Develop Azure compute solutions.
Develop for Azure storage practice questions
Practise AZ-204 questions linked to Develop for Azure storage.
Implement Azure security practice questions
Practise AZ-204 questions linked to Implement Azure security.
Connect to and consume Azure services and third-party services practice questions
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Monitor, troubleshoot, and optimize Azure solutions practice questions
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
AZ-204 fundamentals practice questions
Practise AZ-204 questions linked to AZ-204 fundamentals.
AZ-204 scenario practice questions
Practise AZ-204 questions linked to AZ-204 scenario.
AZ-204 troubleshooting practice questions
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Start a free AZ-204 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-204 question test?
Monitor, troubleshoot, and optimize Azure solutions — This question tests Monitor, troubleshoot, and optimize Azure solutions — distributed tracing.
What is the correct answer to this question?
The correct answer is: Install the Application Insights SDK on all three services and ensure W3C Trace Context header propagation is enabled for both HTTP calls and Service Bus messages — Option A is correct because distributed tracing across HTTP and asynchronous messaging requires the Application Insights SDK on each service and propagation of the W3C Trace-Context standard (traceparent and tracestate headers). This ensures that the App Service API, Azure Function, and downstream storage service share a single trace ID, enabling Application Insights to correlate all telemetry into one end-to-end transaction view.
What should I do if I get this AZ-204 question wrong?
Review distributed tracing, then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
distributed tracing
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More AZ-204 practice questions
- An app must store relational state and perform transactions across multiple tables with T-SQL support. Which Azure data…
- You are monitoring an Azure App Service using Application Insights. You notice that the server response time is high for…
- Which TWO services can be used to implement a publish-subscribe messaging pattern in Azure?
- You need to monitor the CPU utilization of an Azure VM in real-time and set up an alert when it exceeds 90%. Which Azure…
- You are monitoring an Azure web application with Application Insights. You notice a sudden increase in the number of fai…
- You are monitoring an Azure web app using Application Insights. You need to create a query that returns the average dura…
Last reviewed: Jun 11, 2026
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.