- A
Use the Application Insights Map to visualize dependencies.
Why wrong: The Application Map shows dependencies and their health, but it does not provide code-level profiling to identify the exact line of code causing slowness.
- B
Enable Application Insights Profiler.
Correct. Profiler captures detailed execution traces for requests and shows the time spent in each method, enabling you to pinpoint the slow code path.
- C
Use the Snapshot Debugger to capture debug snapshots on exceptions.
Why wrong: Snapshot Debugger is used to debug exceptions, not performance issues. It captures the state when an exception is thrown, not during normal execution.
- D
Create a custom telemetry event in the slow endpoint to log timing data.
Why wrong: Custom telemetry can help track timing, but it requires manual instrumentation and does not provide automatic call stack traces at the code level.
Quick Answer
The answer is to enable Application Insights Profiler. This feature is the correct choice because it captures detailed call stacks and per-line execution timing for production requests without requiring any code changes or the ability to reproduce the issue locally. When users report a slow endpoint that you cannot replicate in development, the Profiler automatically traces the CPU and wall-clock time spent on each method call, pinpointing the exact line of code causing the delay. On the AZ-204 exam, this question tests your understanding of production diagnostics versus development debugging tools—a common trap is choosing Application Insights Map or Snapshot Debugger, but remember that Map shows dependencies, not code lines, while Snapshot Debugger catches exceptions, not slow performance. The key distinction is that Profiler is purpose-built for identifying slow code lines in production. Memory tip: think “Profiler for Performance, Snapshot for Exceptions.”
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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 using Application Insights to monitor an ASP.NET Core web API. Users report that a specific endpoint is slow, but you cannot reproduce the issue in development. You need to identify which line of code is causing the delay in production. 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
Enable Application Insights Profiler.
Application Insights Profiler is designed specifically to trace code-level performance issues in production without requiring code changes or reproducing the problem. It captures detailed call stacks and timing for each request, allowing you to identify exactly which line of code is causing the delay. This makes it the correct choice for diagnosing a slow endpoint that cannot be reproduced in development.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the Application Insights Map to visualize dependencies.
Why it's wrong here
The Application Map shows dependencies and their health, but it does not provide code-level profiling to identify the exact line of code causing slowness.
- ✓
Enable Application Insights Profiler.
Why this is correct
Correct. Profiler captures detailed execution traces for requests and shows the time spent in each method, enabling you to pinpoint the slow code path.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use the Snapshot Debugger to capture debug snapshots on exceptions.
Why it's wrong here
Snapshot Debugger is used to debug exceptions, not performance issues. It captures the state when an exception is thrown, not during normal execution.
- ✗
Create a custom telemetry event in the slow endpoint to log timing data.
Why it's wrong here
Custom telemetry can help track timing, but it requires manual instrumentation and does not provide automatic call stack traces at the code level.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the Snapshot Debugger (for exceptions) with the Profiler (for performance), or assume custom telemetry is the only way to get timing data, missing that the Profiler provides automatic, line-level diagnostics without code changes.
Trap categories for this question
Command / output trap
The Application Map shows dependencies and their health, but it does not provide code-level profiling to identify the exact line of code causing slowness.
Detailed technical explanation
How to think about this question
The Profiler works by sampling requests at a configurable rate (default 5%) and using ETW (Event Tracing for Windows) to capture CPU and wall-clock time per method. It correlates these traces with Application Insights request telemetry, enabling you to see the exact method and line number where time is spent, even in async code. In a real-world scenario, this is invaluable for identifying a slow database query or a blocking I/O call that only manifests under production load.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. 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.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
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 — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable Application Insights Profiler. — Application Insights Profiler is designed specifically to trace code-level performance issues in production without requiring code changes or reproducing the problem. It captures detailed call stacks and timing for each request, allowing you to identify exactly which line of code is causing the delay. This makes it the correct choice for diagnosing a slow endpoint that cannot be reproduced in development.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Same concept, more angles
1 more ways this is tested on AZ-204
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are developing a web app that experiences intermittent slow responses. You enable Application Insights and notice that the server-side request duration is normally under 200ms, but some requests take over 5 seconds. Which diagnostic tool should you use to identify the root cause?
medium- A.Availability Tests
- ✓ B.Application Insights Profiler
- C.Snapshot Debugger
- D.Live Metrics Stream
Why B: Option B is correct because Profiler traces the specific line of code that causes slow requests. Option A (Snapshot Debugger) is for exceptions, not performance. Option C (Live Metrics) shows real-time data but doesn't pinpoint code. Option D (Availability Tests) checks endpoint availability, not performance.
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.