Day 18: Microsoft Module 900 XP Control and organize Azure resources with Azure Resource Manager

Knowledge check:

1. Tags can be applied to any type of resource on Azure

• True
• False

Not all resources support tags, so you will want to confirm that your resource type supports them.

2. Tags applied at a resource group level are propagated to resources within the resource group.

• True
• False

Tags are not inherited. You need to apply tags to every supported resource that you need tagged.

3. Which of the following is not a feature of resource groups?

• Resources can be in only one resource group.
• Resources can be moved from one resource group to another resource group.
• Resource groups can be nested.
• Role-based access control can be applied to the resource group.

4. Which of the following might be a good usage of tags?

• Using tags to associate a cost center with resources for internal chargeback
• Using tags in conjunction with Azure Automation to schedule maintenance windows
• Using tags to store environment and department association
• All of the above are good ways to use tags

5. Which of the following would be the most efficient way to ensure a naming convention was followed across your subscription?

• Send out an email with the details of your naming conventions and hope it is followed
• Create a policy with your naming requirements and assign it to the scope of your subscription
• Give all other users except for yourself read-only access to the subscription. Have all requests to create resources sent to you so you can review the names being assigned to resources, and then create them.

6. Which of the following would be good to put a resource lock on?

• An ExpressRoute circuit with connectivity back to your on-premises network
• A non-production virtual machine used to test occasional application builds
• A storage account used to temporarily store images processed in a development environment