Template deployment methods in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is an ARM template in Azure?

An ARM template is a JSON file that defines the infrastructure and configuration for Azure resources. It helps deploy resources consistently and repeatedly.

beginner

Name two main methods to deploy ARM templates.

You can deploy ARM templates using the Azure Portal or Azure CLI/PowerShell commands.

intermediate

What is the benefit of using Azure CLI for template deployment?

Azure CLI allows automation and scripting of deployments, making it easy to deploy templates repeatedly and integrate with other tools.

beginner

How does the Azure Portal deployment method work for templates?

You upload or paste the ARM template in the Azure Portal, fill in required parameters, and start deployment through a guided interface.

beginner

What is a key advantage of using template deployment methods?

They ensure consistent, repeatable infrastructure setup, reducing manual errors and saving time.

Which file format is used for Azure ARM templates?

A JSON

B YAML

C XML

D TXT

ARM templates are written in JSON format to define Azure resources.

Which Azure tool allows you to deploy templates via command line?

A Azure Portal

B Azure CLI

C Azure Storage Explorer

D Azure Monitor

Azure CLI is used to deploy ARM templates from the command line.

What is required when deploying a template through the Azure Portal?

A Creating a virtual machine first

B Writing code in C#

C Installing Visual Studio

D Uploading or pasting the template and providing parameters

You upload or paste the ARM template and fill in parameters in the portal.

Why use template deployment methods instead of manual setup?

A To increase manual work

B To slow down deployment

C To ensure consistent and repeatable deployments

D To avoid using Azure services

Templates help automate and standardize deployments, reducing errors.

Which of these is NOT a deployment method for ARM templates?

A Microsoft Word

B Azure CLI

C Azure PowerShell

D Azure DevOps Pipelines

E Azure Portal

Microsoft Word is not a deployment method for ARM templates.

Explain the main ways to deploy ARM templates in Azure and their benefits.

Think about manual vs automated deployment options.

Describe why using template deployment methods is better than manual resource creation in Azure.

Consider what happens if you do the same task many times by hand.

Practice

1. What is the main purpose of using an Azure Resource Manager (ARM) template for deployment?

easy

A. To manually create resources one by one in the Azure portal

B. To write code for a web application

C. To automate the creation and configuration of cloud resources

D. To monitor resource usage and billing

Solution

1. Step 1: Understand ARM template purpose

   ARM templates are JSON files that define infrastructure and configuration in a repeatable way.

2. Step 2: Compare options

   Only To automate the creation and configuration of cloud resources describes automation of resource creation, which is the core use of ARM templates.

3. Final Answer:

   To automate the creation and configuration of cloud resources -> Option C

4. Quick Check:

   ARM templates automate deployments [OK]

Hint: Templates automate resource setup, not manual or monitoring tasks [OK]

Common Mistakes:

• Confusing templates with manual portal actions
• Thinking templates are for app coding
• Mixing deployment with monitoring

2. Which Azure CLI command correctly deploys a resource group using an ARM template file named template.json with parameters in params.json?

easy

A. az resource deploy --group MyGroup --template template.json --params params.json

B. az group create --template template.json --params params.json

C. az deployment create --resource MyGroup --template template.json --parameters params.json

D. az deployment group create --resource-group MyGroup --template-file template.json --parameters params.json

Solution

1. Step 1: Identify correct Azure CLI syntax for group deployment

   The correct command is az deployment group create with flags for resource group, template file, and parameters.

2. Step 2: Check each option

   Only az deployment group create --resource-group MyGroup --template-file template.json --parameters params.json uses the correct command and flags as per Azure CLI documentation.

3. Final Answer:

   az deployment group create --resource-group MyGroup --template-file template.json --parameters params.json -> Option D

4. Quick Check:

   Use az deployment group create for group deployments [OK]

Hint: Use 'az deployment group create' with --resource-group flag [OK]

Common Mistakes:

• Using 'az group create' which creates resource groups, not deploys templates
• Wrong command verbs like 'deploy' or 'resource deploy'
• Incorrect flag names like --template instead of --template-file

3. Given this Azure CLI command:
az deployment sub create --location eastus --template-file main.json --parameters storageAccountName=mystorage
What is the scope of this deployment?

medium

A. Deploys resources at the management group level

B. Deploys resources at the subscription level

C. Deploys resources inside a resource group

D. Deploys resources only in the eastus resource group

Solution

1. Step 1: Analyze the command scope

   The command uses az deployment sub create, which means deployment at the subscription scope.

2. Step 2: Understand location and parameters

   The --location flag is required for subscription deployments; parameters define resource details.

3. Final Answer:

   Deploys resources at the subscription level -> Option B

4. Quick Check:

   az deployment sub create = subscription scope [OK]

Hint: 'sub create' means subscription-level deployment [OK]

Common Mistakes:

• Confusing subscription with resource group scope
• Assuming location defines resource group
• Mixing management group with subscription

4. You run this command to deploy a template:
az deployment group create --resource-group MyGroup --template-file template.json
But you get an error saying parameters are missing. What is the likely cause?

medium

A. The template requires parameters but none were provided

B. The resource group MyGroup does not exist

C. The template file template.json is not valid JSON

D. The Azure CLI is not installed

Solution

1. Step 1: Understand error message

   The error about missing parameters means the template expects input values not given in the command.

2. Step 2: Check command and options

   The command does not include --parameters, so required parameters are missing.

3. Final Answer:

   The template requires parameters but none were provided -> Option A

4. Quick Check:

   Missing parameters cause deployment errors [OK]

Hint: Always provide required parameters with --parameters flag [OK]

Common Mistakes:

• Assuming resource group missing causes parameter error
• Ignoring template validation errors
• Not verifying Azure CLI installation

5. You want to deploy a template at the management group level to apply policies across multiple subscriptions. Which Azure CLI command should you use?

hard

A. az deployment mg create --management-group-id MyMgmtGroup --location eastus --template-file policy.json

B. az deployment group create --resource-group MyGroup --template-file policy.json

C. az deployment sub create --subscription MySubscription --template-file policy.json

D. az deployment create --template-file policy.json

Solution

1. Step 1: Identify deployment scope for management groups

   Management group deployments use az deployment mg create with the management group ID.

2. Step 2: Compare options

   az deployment mg create --management-group-id MyMgmtGroup --location eastus --template-file policy.json correctly uses the management group deployment command and specifies the management group ID.

3. Final Answer:

   az deployment mg create --management-group-id MyMgmtGroup --location eastus --template-file policy.json -> Option A

4. Quick Check:

   Use az deployment mg create for management group scope [OK]

Hint: Use 'az deployment mg create' for management group deployments [OK]

Common Mistakes:

• Using group or subscription commands for management group scope
• Omitting management group ID
• Using incomplete commands without scope