- A
Built-in request telemetry (server-side requests)
Why wrong: Request telemetry captures incoming HTTP requests to your web app, not outbound calls to external services.
- B
Dependency tracking feature
Dependency tracking automatically captures outbound HTTP calls (and other dependencies like databases) with duration, result code, and exception details.
- C
Custom events (TrackEvent)
Why wrong: Custom events are used for manual logging of business events and do not automatically capture external API call details.
- D
Page view tracking
Why wrong: Page view tracking is for client-side page loads in browser applications, not for server-side API calls.
Quick Answer
The answer is the dependency tracking feature in Application Insights. This feature is specifically designed to monitor calls your application makes to external services, automatically capturing the duration, status code, and success or failure of outbound HTTP requests to APIs, databases, or other endpoints. On the AZ-204 exam, dependency tracking tests your understanding of how to instrument distributed applications for performance monitoring, often appearing in scenarios where you need to isolate latency caused by third-party services versus your own code. A common trap is confusing dependency tracking with request tracking—remember that requests track incoming calls to your app, while dependencies track outgoing calls your app makes. For a quick memory tip, think of dependencies as the external services your app depends on, and the feature automatically logs their response times and status codes without requiring custom instrumentation.
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. 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: dependency tracking monitors outbound calls from your application.. 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 Web App using Application Insights. You need to track the duration and status code of an external API call made by the app. Which Application Insights feature should you use?
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
Dependency tracking feature
Dependency tracking in Application Insights is specifically designed to monitor calls made by your application to external services, such as APIs, databases, or HTTP endpoints. It automatically captures the duration, success/failure status, and response code of outbound HTTP requests, making it the correct choice for tracking an external API call's duration and status code.
Key principle: Dependency tracking monitors outbound calls from your application.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Built-in request telemetry (server-side requests)
Why it's wrong here
Request telemetry captures incoming HTTP requests to your web app, not outbound calls to external services.
- ✓
Dependency tracking feature
Why this is correct
Dependency tracking automatically captures outbound HTTP calls (and other dependencies like databases) with duration, result code, and exception details.
Related concept
Dependency tracking monitors outbound calls from your application.
- ✗
Custom events (TrackEvent)
Why it's wrong here
Custom events are used for manual logging of business events and do not automatically capture external API call details.
- ✗
Page view tracking
Why it's wrong here
Page view tracking is for client-side page loads in browser applications, not for server-side API calls.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'request telemetry' (incoming calls to the app) with 'dependency telemetry' (outgoing calls from the app), leading them to incorrectly select built-in request telemetry for monitoring external API calls.
Detailed technical explanation
How to think about this question
Application Insights dependency tracking works by instrumenting the HttpClient or other dependency calls via bytecode injection or SDK hooks, automatically generating a dependency telemetry item with fields like `target`, `type`, `data`, `duration`, `success`, and `resultCode`. Under the hood, it uses the W3C Trace-Context standard for distributed tracing, allowing end-to-end correlation of the external call with the parent request. In a real-world scenario, if the external API returns a 429 (Too Many Requests) status, dependency tracking will capture that as a failed call, enabling proactive throttling alerts.
KKey Concepts to Remember
- Dependency tracking monitors outbound calls from your application.
- It automatically captures duration, status code, and target of external API calls.
- Supports various dependencies including HTTP, databases, and message queues.
- Essential for understanding performance and failures in distributed systems.
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
Dependency tracking monitors outbound calls from your application.
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. Dependency tracking monitors outbound calls from your application. 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 dependency tracking monitors outbound calls from your application., 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 — Dependency tracking monitors outbound calls from your application..
What is the correct answer to this question?
The correct answer is: Dependency tracking feature — Dependency tracking in Application Insights is specifically designed to monitor calls made by your application to external services, such as APIs, databases, or HTTP endpoints. It automatically captures the duration, success/failure status, and response code of outbound HTTP requests, making it the correct choice for tracking an external API call's duration and status code.
What should I do if I get this AZ-204 question wrong?
Review dependency tracking monitors outbound calls from your application., then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Dependency tracking monitors outbound calls from your application.
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 →
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.