AZ-900 Describe Azure management and governance Practice Question

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 Application Insights

  Why it's wrong here

  Application Insights is an application performance management (APM) service that drills into a live web application's request rates, response times, dependency failures, and user page views. While it can forward its telemetry to a Log Analytics workspace, its purpose is not to collect and consolidate logs from multiple Azure infrastructure resources. It is therefore scoped to application-level insight rather than the broad, cross-service log analysis that the question describes.

• ✓

  Azure Log Analytics

  Why this is correct

  Azure Log Analytics is the core data-collection and querying service in Azure Monitor, ingesting logs and metrics from many Azure resources through diagnostic settings and agents. It stores everything in a central Log Analytics workspace and uses Kusto Query Language (KQL) to perform complex searches, join data sets, and surface trends across sources. This centralized, multi-source capability is exactly what makes it the correct choice for analyzing custom log data.

• ✗

  Azure Service Health

  Why it's wrong here

  Service Health is a notification and reporting surface that tracks the real-time condition of Microsoft's Azure platform itself, including active incidents, planned maintenance events, and service advisories. It does not consume custom resource logs or telemetry from your own subscriptions because it is not a data-ingestion pipeline. As a result, it cannot provide the kind of organization-specific log analysis that the question is asking for.

• ✗

  Azure Network Watcher

  Why it's wrong here

  Network Watcher is a regional diagnostic and monitoring tool for network infrastructure, offering packet captures, connection monitors, NSG flow logs, and VPN diagnostics. Its telemetry is frequently sent to a Log Analytics workspace for persistence, but Network Watcher itself is not a general-purpose log warehouse. Its focus on network-level troubleshooting means it cannot aggregate application and platform logs from all resource types, which is the core function being tested.