Describe Azure management and governance practice questions

Microsoft Cost Management monitors and controls actual Azure spend with cost analysis, budgets, and alerts.

Setting a budget with an alert on real, running resources is a Cost Management capability. The Pricing Calculator and TCO Calculator are pre-deployment planning tools that never see actual usage, and Blueprints deploy governance settings rather than tracking cost.

1. Identify the phrase: monitor and control actual spend, with a budget and alert.
2. Match ongoing spend tracking to Microsoft Cost Management.
3. Exclude the pre-deployment calculators and governance tools.

Exam tip: Monitor and control real spend after deployment with Microsoft Cost Management budgets and alerts.

Outbound data transfer (egress) is a cost factor, while inbound data is typically free.

Azure generally bills data that leaves its network to the internet (egress), while inbound data is usually free. That is why egress is a recognized cost factor and the other options, which describe free or non-existent charges, are wrong.

1. Recall that network traffic affects Azure cost.
2. Remember egress (outbound) is billed and ingress (inbound) is usually free.
3. Select outbound data transfer to the internet.

Exam tip: Outbound data transfer (egress) is generally billed; inbound data is typically free.

Prices vary by Azure region for the same service.

Region is a genuine cost factor because Azure charges different rates for the same service in different regions. Tags, names, and descriptions are metadata that never change a resource's price.

1. Recognize the same size costs different amounts in different places.
2. Attribute this to regional price variation.
3. Reject metadata like tags and names, which do not affect cost.

Exam tip: Azure prices vary by region for the same service, so region is a cost factor.

Azure Reservations give a discount for a 1-year or 3-year commitment.

A steady VM that will run for years is the classic case for a reservation, which trades a term commitment for a lower rate. Spot VMs can be evicted (wrong for always-on), pay-as-you-go offers no commitment discount, and Hybrid Benefit reduces cost through licensing rather than a term commitment.

1. Note the trigger: discount for a 1 or 3 year commitment.
2. Match a term commitment on a steady workload to Reservations.
3. Distinguish it from evictable Spot VMs and license-based Hybrid Benefit.

Exam tip: Azure Reservations discount a resource for a 1-year or 3-year commitment.

Azure Spot Virtual Machines run interruptible workloads on spare capacity at a deep discount.

A tolerant, interruptible batch job that wants the deepest discount is the textbook Spot VM use case, because Spot trades eviction risk for a steep price cut. Reservations reward long commitments on steady workloads, Hybrid Benefit is a licensing discount, and pay-as-you-go carries no discount at all.

1. Spot the cues: interruptible workload plus deepest discount.
2. Match spare-capacity, evictable pricing to Spot VMs.
3. Rule out Reservations, Hybrid Benefit, and pay-as-you-go.

Exam tip: Spot VMs give deep discounts on spare capacity for interruptible workloads, but can be evicted.

Azure Hybrid Benefit reuses existing licenses to reduce Azure resource cost.

Reusing owned Windows Server or SQL Server licenses to cut Azure cost is precisely what Hybrid Benefit does. Reservations and savings plans are commitment-based discounts, and Spot VMs are about spare capacity, so none of those involve existing licenses.

1. Identify the cue: reuse existing on-premises licenses.
2. Match license reuse to Azure Hybrid Benefit.
3. Separate it from commitment discounts and spare-capacity pricing.

Exam tip: Azure Hybrid Benefit reuses existing licenses to lower matching Azure resource costs.