Which deployment scope allows you to deploy resources at the subscription level, such as creating resource groups or policies?
Think about where resource groups are created in Azure.
The subscription scope allows deployment of resources that exist at the subscription level, including creating resource groups and policies. Resource group scope is limited to resources inside a specific group. Management group and tenant scopes are for broader organizational management.
What is the output of this Azure CLI command when deploying an ARM template to a resource group?
az deployment group create --resource-group MyGroup --template-file template.json
Consider what the CLI returns after a successful deployment.
The Azure CLI returns a JSON object containing details about the deployment, including outputs defined in the template and the provisioning state. It does not return plain text confirmation or unrelated lists.
You need to deploy identical resources to multiple Azure regions using ARM templates. Which deployment method best supports this scenario?
Think about how to deploy resources across multiple regions efficiently.
Subscription-level deployments allow you to deploy resources across multiple resource groups and regions by passing location parameters. Deploying separately is less efficient. Management group scope is for policies and governance, not resource deployment. Blueprints are for governance, not direct resource deployment.
Which method is the most secure way to handle sensitive information like passwords in ARM template deployments?
Consider Azure services designed for secret management.
Using Azure Key Vault references allows secure retrieval of secrets during deployment without exposing them in templates or scripts. Hardcoding or storing passwords in plain text is insecure. Passing passwords unencrypted on command line risks exposure.
What happens to existing resources in a resource group when you deploy an ARM template using the complete mode?
Think about how complete mode manages resources compared to incremental mode.
Complete mode deletes any resources in the resource group that are not defined in the ARM template, ensuring the resource group matches the template exactly. Incremental mode leaves existing resources untouched.