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/The correct answer is A. Tags.
Azure tags are name-value pairs that you can assign to your Azure resources. They help you organize and categorize your resources, and provide metadata that can be used for billing, monitoring, and automation purposes.
In this scenario, using tags is the best way to group and track the usage of Azure resources for each office. You can assign a tag to each resource that identifies the office to which it belongs. For example, you could use a tag called "Office" with values such as "Office1", "Office2", and so on.
Once you have assigned the tags, you can use Azure portal to generate the billing reports, and group the usage by office based on the tags. This makes it easy to analyze the usage and costs for each office separately.
Templates, locks, and policies are other features of Azure Resource Manager that are useful in different scenarios, but they are not directly relevant to generating billing reports based on office usage.
Templates are used to create and deploy Azure resources in a repeatable and automated way.
Locks are used to prevent accidental or unauthorized changes to Azure resources, by locking down the resource group or individual resources.
Policies are used to enforce rules and standards for Azure resources, such as requiring specific tags, or restricting the types of resources that can be created.