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.

• ✗

  Microsoft Sentinel

  Why it's wrong here

  Microsoft Sentinel is a cloud-native SIEM (Security Information and Event Management) and SOAR (Security Orchestration, Automation, and Response) tool. Its primary purpose is to ingest security telemetry—such as sign-in logs, audit logs, and threat intelligence—and to detect, investigate, and respond to security incidents. While Sentinel can connect to Azure Monitor's Log Analytics workspaces for its underlying data storage, it does not provide general resource performance monitoring like CPU utilization, memory, or disk I/O. Therefore, it is incorrect for a broad resource-monitoring requirement across subscriptions.

• ✗

  Azure Service Health

  Why it's wrong here

  Azure Service Health is a dashboard that provides personalized information about the health of Azure platform services, including service issues, planned maintenance, and health advisories. It focuses on incidents and outages within Microsoft's shared infrastructure—for example, "the SQL database regional endpoint is degraded"—not on the operational telemetry of your own resources such as a virtual machine's memory pressure or a web app's request failure count. Service Health does not collect metrics or logs from your workloads and does not support alerting on performance counters. Thus, it is not an appropriate tool for general resource monitoring.

• ✓

  Azure Monitor

  Why this is correct

  Azure Monitor is the central monitoring platform in Azure that collects, analyzes, and responds to telemetry from secure resources, applications, and even on-premises systems. It acquires platform metrics, custom logs, and diagnostics data via Azure Diagnostics extensions and Log Analytics agent, enabling comprehensive visibility into resource health, performance, and dependencies across all subscriptions in a tenant. Azure Monitor supports powerful querying with KQL, creating alert rules, and visualizing dashboards, making it the exact service for a requirement spanning multiple subscriptions. It is the correct answer because it is purpose-built for unified resource observability.

• ✗

  Azure Advisor

  Why it's wrong here

  Azure Advisor is a free, personalized advisor service that assesses your deployed Azure resources and creates recommendations based on industry-standard best practices across five categories: reliability, security, performance, operational excellence, and cost. It does not provide real-time metrics, log collection, alerting, or live dashboards; instead, it runs periodic analyses (often every 12-24 hours) and surfaces actionable recommendations for optimizing existing configurations. For example, Advisor might suggest rightsizing an underutilized VM or enabling geo-redundancy, but it cannot show you current CPU utilization or trigger alerts. Therefore, it should not be selected for a real-time resource monitoring requirement.

Go deeper

Related to this question