Your company has an Azure environment with a management group named `MG-Corp` and two subscriptions named `Sub-App` and `Sub-Shared`. `Sub-Shared` contains a resource group named `RG-Monitoring` which hosts a storage account named `saexportdata`.
You need to configure Azure Cost Management to meet the following requirements:
- Automatically export daily cost data of `Sub-App` to the `saexportdata` storage account.
- Trigger an automated runbook located in `Sub-Shared` to stop non-production workloads when the monthly costs of `Sub-App` exceed USD.
Which two actions should you perform? (Select two.)
- In `Sub-App`, create a budget and configure an alert threshold associated with an action group that targets the runbook.Cevap
- BIn `Sub-App`, create a budget with a limit of USD and associate the action group directly to the budget scope without defining alert thresholds.
- In `Sub-App`, configure a Cost Management export that targets the `saexportdata` storage account.Cevap
- DApply a `ReadOnly` lock to `RG-Monitoring` to prevent accidental deletion of `saexportdata` while permitting the daily export.
Cevap
The correct actions are: (1) In the source subscription, create a budget and configure an alert threshold associated with an action group that targets the runbook; and (2) In the source subscription, configure a Cost Management export that targets the storage account.
To meet the requirements, you must perform two actions. First, to automatically export daily cost data of one subscription to a storage account in another subscription within the same tenant, you can configure a Cost Management export in the source subscription pointing to the target storage account. Second, to trigger an automated runbook when the monthly cost exceeds a threshold, you must create a budget in the source subscription and configure an alert threshold (such as ) linked to an action group that targets the runbook.
Adım Adım Çözüm
Anahtar Kavram
Azure Cost Management budgets require alert thresholds to trigger action groups. Cost exports can target storage accounts in different subscriptions within the same tenant, but control-plane blocking configurations like `ReadOnly` locks will prevent the export from writing data by blocking key retrieval.