- A
Enable snapshot debugging for the application.
Why wrong: Snapshot debugger captures a snapshot of the application state on exceptions but does not show dependency-level failure rates across all requests.
- B
Use Application Insights Profiler to capture code-level traces.
Why wrong: Profiler is for diagnosing performance bottlenecks in code, not for identifying external dependency failures.
- C
Configure Application Insights dependency tracking and view the Dependency Metrics blade.
Dependency tracking records each call to external services, and the metrics blade aggregates failures and durations for each dependency, making it easy to spot failures.
- D
Set up a custom event telemetry for each external call.
Why wrong: While possible, custom events require manual instrumentation and do not automatically provide the aggregated failure metrics that built-in dependency tracking does.
Quick Answer
The answer is to configure Application Insights dependency tracking and view the Dependency Metrics blade. This is correct because Application Insights automatically instruments outgoing HTTP calls, SQL queries, and other external dependencies as dependency telemetry, capturing failure rates, durations, and dependency names without requiring code changes. When standard server response time remains normal but HTTP 500 errors spike, the issue is likely in an external API call, and the Dependency Metrics blade isolates exactly which dependency is failing by showing its failure count and average duration. On the AZ-204 exam, this tests your understanding of distributed tracing and dependency monitoring in Azure App Service—a common trap is to focus on server-side metrics like request rates or exceptions, which won’t reveal external call failures. Remember the mnemonic: “Dependency Metrics for external defects” to quickly recall that dependency tracking, not server metrics, diagnoses failing third-party APIs.
AZ-204 Practice Question: Monitor, troubleshoot, and optimize Azure solutions
This AZ-204 practice question tests your understanding of monitor, troubleshoot, and optimize azure solutions. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: application Insights dependency tracking automatically monitors outgoing calls to external services.. 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.
You are monitoring an Azure App Service using Application Insights. You notice that HTTP 500 errors are increasing, but the standard server response time metric remains normal. You suspect that the errors are occurring in an external API call made by the application. How can you identify the dependency that is failing?
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
Configure Application Insights dependency tracking and view the Dependency Metrics blade.
Option C is correct because Application Insights dependency tracking automatically monitors HTTP calls, SQL queries, and other external dependencies made by your application. By viewing the Dependency Metrics blade, you can see failure rates, durations, and dependency names, allowing you to identify which external API call is failing without modifying code.
Key principle: Application Insights dependency tracking automatically monitors outgoing calls to external services.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable snapshot debugging for the application.
Why it's wrong here
Snapshot debugger captures a snapshot of the application state on exceptions but does not show dependency-level failure rates across all requests.
- ✗
Use Application Insights Profiler to capture code-level traces.
Why it's wrong here
Profiler is for diagnosing performance bottlenecks in code, not for identifying external dependency failures.
- ✓
Configure Application Insights dependency tracking and view the Dependency Metrics blade.
Why this is correct
Dependency tracking records each call to external services, and the metrics blade aggregates failures and durations for each dependency, making it easy to spot failures.
Related concept
Application Insights dependency tracking automatically monitors outgoing calls to external services.
- ✗
Set up a custom event telemetry for each external call.
Why it's wrong here
While possible, custom events require manual instrumentation and do not automatically provide the aggregated failure metrics that built-in dependency tracking does.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse dependency tracking with custom event telemetry or think that snapshot debugging or profiling can identify external API failures, but only dependency tracking provides automatic, aggregated metrics for outbound calls.
Trap categories for this question
Command / output trap
Snapshot debugger captures a snapshot of the application state on exceptions but does not show dependency-level failure rates across all requests.
Detailed technical explanation
How to think about this question
Application Insights dependency tracking works by instrumenting the application's HTTP client (e.g., System.Net.Http.HttpClient) and other out-of-band calls using the Application Insights SDK. It automatically generates dependency telemetry with fields like dependency type, target, duration, and success/failure status, which are aggregated in the Dependency Metrics blade. In a real-world scenario, if an external API returns HTTP 500, the dependency telemetry will show a failure count increase while the server response time remains normal, isolating the issue to the external call.
KKey Concepts to Remember
- Application Insights dependency tracking automatically monitors outgoing calls to external services.
- It collects duration, success/failure, and target information for each dependency call.
- The Dependency Metrics blade aggregates and visualizes dependency health and performance.
- Dependency tracking is crucial for diagnosing issues originating from external API integrations.
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
Application Insights dependency tracking automatically monitors outgoing calls to external services.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Application Insights dependency tracking automatically monitors outgoing calls to external services. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Review application Insights dependency tracking automatically monitors outgoing calls to external services., 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 — Application Insights dependency tracking automatically monitors outgoing calls to external services..
What is the correct answer to this question?
The correct answer is: Configure Application Insights dependency tracking and view the Dependency Metrics blade. — Option C is correct because Application Insights dependency tracking automatically monitors HTTP calls, SQL queries, and other external dependencies made by your application. By viewing the Dependency Metrics blade, you can see failure rates, durations, and dependency names, allowing you to identify which external API call is failing without modifying code.
What should I do if I get this AZ-204 question wrong?
Review application Insights dependency tracking automatically monitors outgoing calls to external services., then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Application Insights dependency tracking automatically monitors outgoing calls to external services.
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.