- A
Use Log Analytics and run a query on the 'requests' table to aggregate by URL and sort by avg(duration).
Why wrong: Writing a custom query can achieve this, but it's not the most straightforward feature for this common task. The Performance blade provides the same information with better UX and built-in drill-downs.
- B
Use the 'Performance' blade under 'Investigate' in the Application Insights resource.
The Performance blade is specifically designed for this purpose. It shows the top operations (requests) by their average duration over a selected time range, along with request count and other metrics.
- C
Use the 'Application Map' feature to visualize dependencies and endpoints.
Why wrong: Application Map shows the topology of components and their interactions, but does not directly list slow endpoints with aggregated metrics.
- D
Configure Smart Detection to automatically identify slow API endpoints.
Why wrong: Smart Detection raises anomaly alerts based on patterns, but it does not provide a ranked list of consistently slow endpoints.
Quick Answer
The answer is to use the Performance blade under Investigate in the Application Insights resource. This blade is the correct choice because it provides a pre-built, optimized view that automatically aggregates request data by endpoint URL, displaying average response time and request count without requiring any custom query. For the AZ-204 exam, this tests your ability to navigate Azure Monitor tools efficiently rather than writing KQL queries from scratch; a common trap is reaching for the Logs blade to write a custom query when the Performance blade already offers the exact sortable table needed to find the top slowest API endpoints. Remember the memory tip: “Performance for pre-built, Logs for custom” — when you need to quickly identify the top 5 slowest API endpoints over the last 7 days, the Performance blade is your one-stop shop for endpoint URL, average duration, and request count.
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. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. A key principle to apply: the Performance blade is part of Application Insights' 'Investigate' section.. 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 application with Application Insights. You need to identify the top 5 slowest API endpoints over the last 7 days. The results should show the endpoint URL, average response time, and request count. Which feature or query 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
Use the 'Performance' blade under 'Investigate' in the Application Insights resource.
Option B is correct because the 'Performance' blade in Application Insights provides a pre-built, optimized view that automatically aggregates request data by endpoint URL, displaying average response time and request count. It allows you to sort by average duration to quickly identify the top 5 slowest API endpoints over the last 7 days without writing any custom query.
Key principle: The Performance blade is part of Application Insights' 'Investigate' section.
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 Log Analytics and run a query on the 'requests' table to aggregate by URL and sort by avg(duration).
Why it's wrong here
Writing a custom query can achieve this, but it's not the most straightforward feature for this common task. The Performance blade provides the same information with better UX and built-in drill-downs.
- ✓
Use the 'Performance' blade under 'Investigate' in the Application Insights resource.
Why this is correct
The Performance blade is specifically designed for this purpose. It shows the top operations (requests) by their average duration over a selected time range, along with request count and other metrics.
Related concept
The Performance blade is part of Application Insights' 'Investigate' section.
- ✗
Use the 'Application Map' feature to visualize dependencies and endpoints.
Why it's wrong here
Application Map shows the topology of components and their interactions, but does not directly list slow endpoints with aggregated metrics.
- ✗
Configure Smart Detection to automatically identify slow API endpoints.
Why it's wrong here
Smart Detection raises anomaly alerts based on patterns, but it does not provide a ranked list of consistently slow endpoints.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Log Analytics is always the best tool for any custom aggregation, overlooking that Application Insights provides purpose-built blades (like Performance) that offer the same functionality with zero query effort and faster results.
Trap categories for this question
Command / output trap
Application Map shows the topology of components and their interactions, but does not directly list slow endpoints with aggregated metrics.
Detailed technical explanation
How to think about this question
The Performance blade in Application Insights uses pre-aggregated telemetry stored in the 'requests' table, but it leverages optimized indexing and caching to render charts and tables instantly. Under the hood, it runs a Kusto query similar to 'requests | where timestamp > ago(7d) | summarize avg(duration), count() by name, url | top 5 by avg_duration desc', but abstracts the complexity. In real-world scenarios, this blade is ideal for quick triage during incidents, while Log Analytics is better for custom drill-downs like filtering by specific HTTP status codes or correlating with exceptions.
KKey Concepts to Remember
- The Performance blade is part of Application Insights' 'Investigate' section.
- It automatically aggregates and displays application operations (requests).
- Users can sort operations by average duration, count, and other metrics.
- It provides drill-down capabilities for detailed transaction analysis.
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
The Performance blade is part of Application Insights' 'Investigate' section.
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. The Performance blade is part of Application Insights' 'Investigate' section. 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 the Performance blade is part of Application Insights' 'Investigate' section., 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 — The Performance blade is part of Application Insights' 'Investigate' section..
What is the correct answer to this question?
The correct answer is: Use the 'Performance' blade under 'Investigate' in the Application Insights resource. — Option B is correct because the 'Performance' blade in Application Insights provides a pre-built, optimized view that automatically aggregates request data by endpoint URL, displaying average response time and request count. It allows you to sort by average duration to quickly identify the top 5 slowest API endpoints over the last 7 days without writing any custom query.
What should I do if I get this AZ-204 question wrong?
Review the Performance blade is part of Application Insights' 'Investigate' section., then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
The Performance blade is part of Application Insights' 'Investigate' section.
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.