Azure Monitor and Azure Advisor sit next to each other in the Management & Governance domain, and the AZ-900 pairs them on purpose — because candidates mix them up. The distinction is one clean line, drawn in the diagram above: Monitor tells you what IS happening; Advisor recommends how to improve. Learn that sentence, learn the pieces under each name, and this cluster of questions turns into free points.
Azure Monitor: the four building blocks
Azure Monitor is the observability platform. It has four parts worth knowing cold:
- Metrics — near-real-time numeric data (CPU %, request count, disk IOPS). You chart them in Metrics Explorer. Think “numbers over time.”
- Logs — richer, structured records stored in a Log Analytics workspace and queried with Kusto Query Language (KQL). This is where you ask questions like “how many failed sign-ins per hour?”
- Alerts — a rule that watches a signal (a metric or a log query) against a threshold and fires an action group (email, SMS, webhook, automation) when the condition is met. This is the “notify me when…” engine.
- Application Insights — Application Performance Monitoring (APM). It instruments a running app to capture request rates, response times, dependencies, and exceptions — the view from inside the application, not the VM underneath it.
Dashboards and Workbooks then draw metrics and logs together into one visual. Keep the split straight: Metrics = numbers, Logs = KQL records, Alerts = notifications, App Insights = app-level telemetry.
Azure Advisor: five categories, one to-do list
Azure Advisor is the recommendations engine. It inspects the resources you already run and returns a prioritized to-do list — not raw data. Its recommendations fall into exactly five categories:
- Cost — trim spend (idle or under-used resources, reservations).
- Security — surfaced hardening actions.
- Reliability — resilience and business-continuity improvements.
- Operational Excellence — process, monitoring, and best-practice gaps.
- Performance — speed and responsiveness of your resources.
Know those five as a set: any category not on the list (Sustainability, Compliance, Scalability) is a classic distractor. And Advisor itself is free — you pay only if you act on a suggestion.
Monitor vs Advisor — never confuse them
The one distinction the exam tests over and over: Monitor measures, Advisor advises. Monitor gathers the raw signal of what is happening right now; Advisor interprets your estate and hands you a checklist of what to do about it. They are complementary, and often used together — Monitor’s data can even feed the picture Advisor reasons over.
Service Health vs Resource Health
One more pair the exam likes to slip in. When something breaks, you need to know whose problem it is:
- Service Health — Azure-side events: outages, planned maintenance, and advisories affecting a service or region. Microsoft’s side.
- Resource Health — the availability of one specific resource you own, such as a single VM, and why it might be down. Your side.
Ask “is it Azure or is it my resource?” and the answer picks the tool.
The real exam mixes multiple-choice, true/false, and drag-and-drop formats; the seven questions below are standard multiple-choice, and every explanation carries a “why not the others” so the wrong options teach you as much as the right one.
Updated for AZ-900 (July 2026). The sample questions above are our own work
in the style of the exam — not real exam items. The exam itself is set and marked
by the certification body.