AZ-305 Practice Question: Design identity, governance, and monitoring solutions

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure Monitor Workbooks

  Why it's wrong here

  Azure Monitor Workbooks are designed for creating rich, interactive reports and dashboards by querying data from Log Analytics and metrics stores. They are a presentation and analysis layer, not an active detection service — they don't continuously evaluate conditions or generate alerts. Consequently, while workbooks can surface historical trends and aid in post-incident analysis, they cannot by themselves detect or notify about performance issues in real time.

• ✗

  Azure Policy

  Why it's wrong here

  Azure Policy is a governance service that enforces compliance rules on Azure resources, such as allowed VM SKUs or tagging conventions, using denial or audit effects. It operates on the Azure control plane and does not ingest application runtime telemetry, so it cannot detect performance bottlenecks, exceptions, or latency issues within an application. Its purpose is regulatory or organizational compliance, not operational diagnostics or monitoring.

• ✓

  Live Metrics Stream in Application Insights

  Why this is correct

  Live Metrics Stream in Application Insights delivers real-time telemetry with sub-second latency, enabling you to see incoming requests, failures, and performance counters as they occur. Crucially, it uses live sampling and filtering, allowing you to isolate specific operations or attribute values on demand, which makes it an essential tool for detecting issues immediately during a deployment or incident. Unlike other tools, it does not persist data for retrospective analysis, but it is unmatched for live detection and validation.

• ✓

  Application Insights Profiler

  Why this is correct

  Application Insights Profiler captures detailed execution traces for requests that exhibit high latency, revealing where time is spent in code—such as database calls, I/O waits, or CPU-bound operations. It helps detect performance bottlenecks by pinpointing the exact method that causes slowness, rather than merely showing aggregate metrics. Profiler is reactive, analyzing recorded traces after requests occur, making it ideal for root-causing performance issues that are already happening.

• ✓

  Application Map in Application Insights

  Why this is correct

  Application Map provides a visual topology of your distributed application, showing the dependencies between components and their health statuses, including failure rates, average response times, and alert states. It detects issues by highlighting components with elevated error rates or degraded performance, allowing you to spot failing dependencies across service boundaries. By grouping components by telemetry type and cloud role, it helps you quickly localize which external service or internal service is causing an application-wide impact.

Go deeper

Related to this question