Your company has 10 offices. You plan to generate several billing reports from the Azure portal. Each report will contain the Azure resource utilization of each office.
Which Azure Resource Manager feature should you use before you generate the reports?
Click on the arrows to vote for the correct answer
A. B. C. D.A
You can use resource tags to 'label' Azure resources. Tags are metadata elements attached to resources. Tags consist of pairs of key/value strings. In this question, we would tag each resource with a tag to identify each office. For example: Location = Office1. When all Azure resources are tagged, you can generate reports to list all resources based on the value of the tag. For example: All resources used by Office1.
https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/decision-guides/resource-tagging/To generate billing reports for the Azure resource utilization of each office, you need to first organize your Azure resources in a way that you can easily filter and group them by office.
The Azure Resource Manager (ARM) provides several features to help you manage and organize your Azure resources effectively. Of the options listed in the question, the most appropriate feature to use in this scenario is "tags" (option A).
Tags are name-value pairs that you can assign to Azure resources to logically organize them. Tags allow you to categorize resources in a way that is meaningful to your organization, such as by office, environment, or application. You can then use tags to filter and group resources in the Azure portal, Azure CLI, Azure PowerShell, or through Azure Resource Graph queries.
To use tags in this scenario, you would need to assign a unique tag to each Azure resource based on the office it belongs to. For example, you could assign a tag named "Office" with the value "New York" to all resources that belong to the New York office, and a tag named "Office" with the value "Seattle" to all resources that belong to the Seattle office.
Once you have assigned tags to your resources, you can use the Azure Cost Management and Billing service to generate billing reports that group resources by their tags. This allows you to easily see the resource utilization and cost for each office.
Templates (option B) are used to automate the deployment of Azure resources. They are not relevant to generating billing reports.
Locks (option C) are used to prevent accidental deletion or modification of Azure resources. They are not relevant to generating billing reports.
Policies (option D) are used to enforce rules and standards for Azure resources within your organization. They are not directly relevant to generating billing reports, although they can help you ensure that resources are tagged correctly.