ARM Flashcards
NB: What are resource groups?
resource group is a logical container for resources deployed on Azure. These resources are anything you create in an Azure subscription like virtual machines, Application Gateways, and CosmosDB instances.
Resource can only be a member of one group
Groups cannot be nested
Before provisioning resource, must have a resource group to place it in
Resource groups - further functions/benefits
Logical grouping - By placing resources of similar usage, type, or location, you can provide some order and organization to resources you create in Azure.
Life cycle - Resource groups make it easy to remove a set of resources at once.
Authorization - By applying RBAC permissions to a resource group, you can ease administration and limit access to allow only what is needed.
How to Create a Resource Group
Azure portal Azure PowerShell Azure CLI Templates Azure SDKs (like .NET, Java)
NB: What are tags?
Tags are name/value pairs of text data that you can apply to resources and resource groups. Tags allow you to associate custom details about your resource, in addition to the standard Azure properties a resource has the following properties:
department (like finance, marketing, and more)
environment (prod, test, dev)
cost center
life cycle and automation (like shutdown and startup of virtual machines)
How are tags added?
Tags can be added and manipulated through the Azure portal, Azure CLI, Azure PowerShell, Resource Manager templates, and through the REST API.
Uses of tags
organize your resources (training, finance etc)
group your billing data. For example, if you’re running multiple VMs for different organizations, use the tags to group usage by cost center.
You can also use tags to categorize costs by runtime environment, such as the billing usage for VMs running in the production environment. When exporting billing data or accessing it through billing APIs, tags are included in that data and can be used to further slice your data from a cost perspective.
Tagging resources can also help in monitoring to track down impacted resources. Monitoring systems could include tag data with alerts, giving you the ability to know exactly who is impacted.
used in automation. If you want to automate the shutdown and startup of virtual machines in development environments during off-hours to save costs
NB: What are resource locks?
Resource locks are a setting that can be applied to any resource to block modification or deletion.
either Delete or Read-only.
Resource locks can be applied to subscriptions, resource groups, and to individual resources, and are inherited when applied at higher levels.
- Tags can be applied to any type of resource on Azure T/F
False
Not all resources support tags, so you will want to confirm that your resource type supports them.
- Tags applied at a resource group level are propagated to resources within the resource group. T/F
False
Tags are not inherited. Tags need to be applied to every supported resource that you want tagged.
- Which of the following features does not apply to 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.
Resource groups can be nested.
- Which of the following approaches 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
All of the above are good ways to use tags
- Which of the following approaches 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.
Create a policy with your naming requirements and assign it to the scope of your subscription
- Which of the following items would be good use of a resource lock?
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
An ExpressRoute circuit with connectivity back to your on-premises network
