AZ-204 Application Insights Practice Question
A developer needs to run a Kusto query against application request data to identify 95th percentile latency by operation. Where should the query be run? The architecture review board prefers a managed Azure-native control.
⚠ Common exam trap
Watch out — candidates often confuse Azure Resource Graph with Log Analytics, thinking it can query telemetry data, but Resource Graph only returns resource inventory and configuration state, not performance metrics.
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
✓
Logs in Application Insights or the associated Log Analytics workspace
Application Insights stores telemetry data, including request latency, in a Log Analytics workspace. Kusto queries against this data can compute percentiles (e.g., 95th) using the `percentile()` function. This is the correct location because the architecture review board prefers a managed Azure-native control, and Log Analytics is the native Azure monitoring service for running such queries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Logs in Application Insights or the associated Log Analytics workspace
Why this is correct
Application Insights stores request telemetry in a Log Analytics workspace, queryable with KQL. Running the percentile query there uses the managed Azure-native control the review board prefers, avoiding self-hosted query infrastructure while still returning 95th percentile latency grouped by operation.
- ✗
Microsoft Entra audit logs
Why it's wrong here
Microsoft Entra audit logs record directory and sign-in activity, not application request durations, so percentile latency by operation cannot be derived from them. It is tempting because Entra audit logs are queried with Kusto, and would be correct for investigating suspicious sign-ins or consent grants.
- ✗
Azure Key Vault diagnostic settings
Why it's wrong here
Key Vault diagnostic settings route secret-access and vault audit events to a destination; they hold no application request telemetry, so latency percentiles cannot be computed. It is tempting because diagnostic settings do forward logs for Kusto analysis, and would be correct for auditing Key Vault access.
- ✗
Azure Resource Graph only
Why it's wrong here
Azure Resource Graph queries ARM resource metadata and configuration, not application request telemetry, so it cannot compute 95th percentile latency by operation. It is tempting because Resource Graph does use Kusto Query Language, and would be correct for inventorying or auditing Azure resources at scale.
Go deeper
Related to this question
Learn chapter
Azure SignalR Service for Real-Time Apps
Key term
Application Insights
Application Insights is an Azure monitoring service that helps developers detect, diagnose, and understand issues in live web applications by collecting telemetry data like requests, exceptions, and performance counters.
Key term
Azure Monitor Metrics
Azure Monitor Metrics is a feature of Azure Monitor that collects, stores, and analyzes numerical data from Azure resources to track performance, health, and usage over time.
About these practice questions
This AZ-204 question is part of Courseiva's 883-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.