A company's finance department wants to track and limit cloud spending for a new data warehousing project. The project's resources are deployed inside an Azure resource group named rg-data-warehouse. An administrator applies a tag named Project with a value of DataWarehouse directly to rg-data-warehouse, but does not apply any tags to the individual resources inside the group. To monitor this project's costs, the administrator configures a monthly budget in Azure Cost Management filtered by the tag Project: DataWarehouse. What is the result of this budget configuration on the tracking of the virtual machines and databases inside rg-data-warehouse?
- The budget will not track the costs of the virtual machines or databases because resources do not inherit tags from their resource group.Cevap
- BThe budget will successfully track the costs of the virtual machines and databases because tags applied to a resource group are automatically inherited by all resources within it.
- CThe budget will only track the virtual machine costs because compute resources automatically inherit resource group tags, while database resources do not.
- DThe budget will fail to trigger alerts because budgets in Azure Cost Management only apply to Capital Expenditures (CapEx) rather than consumption-based Operational Expenditures (OpEx).
Cevap
The budget will not track the costs of the virtual machines or databases because resources do not inherit tags from their resource group.
The correct answer is correct because Azure resources do not inherit tags applied to their containing resource group. Since the budget is filtered by the tag Project: DataWarehouse and the resources inside the group do not have this tag, their costs will not be tracked by the budget.
Adım Adım Çözüm
Anahtar Kavram
Azure resource tags are not inherited from resource groups or subscriptions, and Azure Cost Management filters based on these tags will exclude untagged child resources.