Technical Lab: Manage costs by using alerts, budgets, and Azure Advisor recommendations
Questions
Question 1 — Multiple Choice
An operations team configured a monthly budget of $10,000 for an Azure subscription. The budget has three alerts configured: 70%, 90%, and 100% of the amount. On the 20th of the month, the accumulated cost reached 91% of the limit.
What is the expected Azure behavior at this moment?
A) Azure automatically suspends all subscription resources when reaching 90%.
B) Azure sends an alert notification to the configured recipients, but does not interrupt any resources.
C) Azure triggers a mandatory automation runbook to shut down VMs.
D) Azure blocks the creation of new resources until the next billing cycle.
Question 2 — Technical Scenario
An administrator needs to be notified proactively when the forecasted cost for the month will exceed the defined budget, before this actually occurs. When reviewing the existing budget configurations, they see the following alert screen:
Alert condition:
Type: Actual
Threshold: 100%
The administrator claims that the current configuration already meets the requirement. What is the problem with this statement?
A) Actual type alerts only work with annual budgets, not monthly ones.
B) The Actual type triggers based on already incurred costs; for predictive alerts, the correct type is Forecasted.
C) The 100% threshold is invalid for Actual type alerts; the maximum allowed is 95%.
D) There is no problem. The Actual type with 100% threshold meets the advance notification requirement.
Question 3 — True or False
Azure Advisor generates cost recommendations based on actual resource utilization analysis, and these recommendations are updated in real-time as consumption changes throughout the day.
True or False?
Question 4 — Technical Scenario
An organization has multiple subscriptions managed by a Management Group. The FinOps team needs to create a single budget that controls the aggregated cost of all subscriptions in the group, without having to create individual budgets for each one.
The analyst opens the Azure portal and tries to create the budget directly in the Management Group, but cannot find the option. What is the most likely cause?
A) Budgets in Management Groups require the Owner role at the tenant root, which the analyst does not have.
B) Budgets cannot be created in Management Groups through the Azure portal; Azure CLI or ARM templates are required.
C) Azure Cost Management with Management Group support requires an Enterprise Agreement (EA) or Microsoft Customer Agreement (MCA) plan; the scope may not be enabled for the organization's contract type.
D) Budgets can only be created at Resource Group or Subscription scope, not in Management Groups.
Question 5 — Multiple Choice
When reviewing Azure Advisor recommendations in the cost category, an administrator finds the suggestion to resize a VM from Standard_D8s_v3 to Standard_D4s_v3. The recommendation indicates estimated savings of 47% per month.
What is the technical basis that Azure Advisor uses to generate this recommendation?
A) Comparison of list prices between the two SKUs, without considering the actual VM usage.
B) Analysis of the VM's CPU and memory utilization history over the last 7 days, identifying low utilization of allocated resources.
C) Verification that the current SKU is discontinued and does not have extended support from Microsoft.
D) Detection that another VM in the same Resource Group has identical configuration, characterizing resource duplication.
Answer Key and Explanations
Answer Key — Question 1
Answer: B
Budgets in Azure Cost Management are monitoring and notification tools, not access control or native automation tools. When reaching a configured threshold, Azure sends email alerts to the defined recipients. No resources are suspended, blocked, or automatically shut down as a direct consequence of the budget.
Alternative A confuses budget with access control policies or Azure Policy. Alternative C describes an optional integration with Azure Automation (via action group), which needs to be explicitly configured by the administrator. Alternative D describes non-existent behavior: budgets do not block resource creation. The main risk of confusing these concepts is believing that configuring a budget, by itself, protects the organization from excessive spending.
Answer Key — Question 2
Answer: B
Azure Cost Management offers two types of alert conditions in budgets:
| Type | Behavior |
|---|---|
| Actual | Triggers when already incurred cost reaches the threshold |
| Forecasted | Triggers when cost projection predicts exceeding the threshold |
The described requirement is explicitly predictive ("before this actually occurs"), which requires the Forecasted type. The current configuration with Actual type and 100% would only trigger when the budget is already exhausted, without sufficient time for corrective action.
Alternatives A and C describe non-existent technical limitations. Alternative D represents the central misconception of the question: confusing reactive monitoring with predictive monitoring.
Answer Key — Question 3
Answer: False
Azure Advisor analyzes resource utilization data, but recommendations are not updated in real-time. The Advisor processes historical usage data with a time window that varies by recommendation type (typically 7 to 30 days) and updates its recommendations periodically, not continuously throughout the day.
This behavior has practical implications: a recently resized VM may continue appearing as a candidate for optimization until the Advisor processes the new utilization history. Treating recommendations as an immediate reflection of the current state is a common operational error.
Answer Key — Question 4
Answer: C
Azure Cost Management supports Management Group scope, but this functionality is only available for accounts with Enterprise Agreement (EA), Microsoft Customer Agreement (MCA), or Microsoft Partner Agreement (MPA). Subscriptions linked to other contract types (such as Pay-As-You-Go) may not have this scope enabled, which prevents creating budgets at the Management Group level through the portal.
Alternative A describes a permission restriction that does not correspond to actual behavior. Alternative B is incorrect: the Azure portal supports budgets in Management Groups when the contract is compatible. Alternative D is the most common and most dangerous misconception: Management Group scope is indeed supported, but under specific contract conditions.
Answer Key — Question 5
Answer: B
Azure Advisor uses the CPU and memory utilization history of the VM, analyzing data collected by Azure Monitor over the last 7 days by default (configurable up to 60 days). When it identifies that the resource is consistently underutilized relative to the allocated SKU, it generates the resizing recommendation with estimated savings based on the cost difference between SKUs.
Alternative A describes a purely table price comparison, without considering usage patterns, which would make the recommendation irrelevant and potentially harmful. Alternatives C and D describe criteria that the Advisor does not use for VM resizing recommendations. The central point is that the Advisor recommendation is driven by observed usage data, not assumptions about the environment.