A municipal ops center wants one Azure platform for collecting and analyzing metrics and logs from resources and applications. Which service is designed for that purpose?
Select an answer to reveal the explanation.
Short Explanation
Azure Monitor is the big collection bowl for metrics and logs from your Azure world. Service Health and Advisor are helpful neighbors, but Monitor is where resource and app telemetry lives.
Full Explanation
Azure Monitor is the Azure platform service designed to collect and analyze metrics and logs from resources and applications for a municipal ops center. It acts as the umbrella for resource metrics, log ingestion and querying patterns, alerting, and related application monitoring capabilities. When the requirement is one place for telemetry collection and analysis—not merely outage notices or best-practice tips—Monitor is the correct fundamentals answer.
Azure Service Health only fails because it focuses on Azure platform service issues and maintenance, not full metrics and log analytics for customer workloads. Azure Advisor only fails because Advisor issues personalized recommendations rather than serving as the primary metrics and logs platform. Azure Policy initiative definitions only fail because Policy defines and assigns governance rules; it does not collect application and resource telemetry for operations analysis.
Exam caveat: AZ-900 describes Monitor as the broad monitoring service; deeper authoring of Kusto queries or custom workbooks is beyond typical fundamentals coding expectations, but knowing Monitor's purpose is required.
Operational check: enable or verify diagnostic settings/metrics for a key municipal resource, open Azure Monitor to view metrics and confirm logs are reaching a Log Analytics workspace, and create a simple alert to prove collection and analysis are wired.