Examkin

Question

Difficulty: HardAzure Subscription Management and Cost Control

You manage an Azure environment that contains a management group named `Corp-MG` and two subscriptions named `Sub-Prod-01` and `Sub-Prod-02` under `Corp-MG`. A resource group named `RG-Operations` in `Sub-Prod-01` contains an Azure Automation runbook that deallocates virtual machines. A resource group named `RG-Resources` in `Sub-Prod-02` contains critical virtual machines with `ReadOnly` resource locks applied. You need to configure a cost control solution that monitors the combined monthly spending of both subscriptions and automatically triggers the runbook in `RG-Operations` to deallocate the virtual machines when the combined monthly spending reaches $10,000\$10,000. You attempt to create an Azure budget at the `Corp-MG` scope and link it to an action group that executes the runbook. Why does this configuration fail to meet the requirements?

  1. Action groups are not supported for budgets configured at the management group scope.Answer
  2. B
    The ReadOnly resource locks on the virtual machines prevent the action group from executing the runbook.
  3. C
    The action group cannot access resources across subscription boundaries without an explicit Owner role assignment at the management group root level.
  4. D
    The budget alert fails because action groups require at least one budget threshold configured to send an email notification to a billing administrator.

Answer

Action groups are not supported for budgets configured at the management group scope.
The correct answer is that action groups are not supported for budgets configured at the management group scope. In Azure Cost Management, budgets created at the management group scope support only email alerts (notifications). Automated actions via action groups (such as triggering Azure Automation runbooks, Azure Functions, or Logic Apps) are only supported for budgets defined at the subscription or resource group scopes.

Step-by-Step Solution

1
Analyze the scope requirements for Azure Cost Management budgets and action groups.
Identify that the requirements demand monitoring combined costs across multiple subscriptions (which requires a management group scope) and triggering an automated action via an action group (which requires subscription or resource group scopes).
Understanding scope capabilities and limitations is key to identifying why the proposed configuration fails.
2
Evaluate the capabilities of budgets defined at the Management Group level.
Determine that budgets scoped to management groups can only send email notifications and cannot be linked to action groups.
This identifies the technical block in the administrator's configuration.
3
Differentiate between control plane restrictions (resource locks) and budget alert execution.
Confirm that the ReadOnly lock on the target VMs does not prevent the budget alert configuration from being saved or executing, as the restriction is purely at the budget scope level.
This rules out resource lock inheritance as the root cause of the budget configuration failure.

Key Concept

Azure Cost Management Budget Scopes and Action Group Limitations
Rate this question

Topics

Azure Subscription Management and Cost Control

More questions from this topic