Template deployment methods in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to deploy an ARM template using Azure CLI.

Azure

az deployment group create --resource-group myResourceGroup --template-file [1]

Drag options to blanks, or click blank then click option'

Aconfig.yaml

Bdeploy.ps1

Cscript.sh

Dtemplate.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using a script file instead of the ARM template JSON file.

Confusing the template file with configuration or script files.

The --template-file parameter requires the ARM template file, which is usually a JSON file like template.json.

2fill in blank

medium

Complete the code to deploy a Bicep template using Azure CLI.

Azure

az deployment group create --resource-group myResourceGroup --template-file [1]

Drag options to blanks, or click blank then click option'

Amain.bicep

Btemplate.json

Cdeploy.ps1

Dconfig.yaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using a JSON template file instead of the Bicep file.

Trying to deploy script or config files as templates.

Bicep templates use the .bicep file extension and can be deployed directly with Azure CLI using the --template-file parameter.

3fill in blank

hard

Fix the error in the Azure PowerShell command to deploy an ARM template.

Azure

New-AzResourceGroupDeployment -ResourceGroupName myResourceGroup -TemplateFile [1]

Drag options to blanks, or click blank then click option'

Adeploy.ps1

Bscript.sh

Ctemplate.json

Dconfig.yaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using script or config files instead of the ARM template JSON file.

Confusing deployment scripts with template files.

The -TemplateFile parameter requires the ARM template JSON file, such as template.json.

4fill in blank

hard

Fill both blanks to deploy a Bicep template with parameters using Azure CLI.

Azure

az deployment group create --resource-group myResourceGroup --template-file [1] --parameters [2]

Drag options to blanks, or click blank then click option'

Amain.bicep

Bparameters.json

Ctemplate.json

Dconfig.yaml

Attempts:

3 left

💡 Hint

Common Mistakes

Using a JSON template file instead of a Bicep file for the template.

Using a config or script file as parameters.

The --template-file should be the Bicep file main.bicep, and --parameters should point to the parameters file parameters.json.

5fill in blank

hard

Fill all three blanks to deploy an ARM template with inline parameters using Azure PowerShell.

Azure

New-AzResourceGroupDeployment -ResourceGroupName myResourceGroup -TemplateFile [1] -TemplateParameterObject @{ [2] = '[3]' }

Drag options to blanks, or click blank then click option'

Atemplate.json

BstorageAccountName

Cmystorage123

Dparameters.json

Attempts:

3 left

💡 Hint

Common Mistakes

Using a parameters file instead of inline parameters.

Mixing up parameter names and values.

The -TemplateFile is the ARM template JSON file template.json. The -TemplateParameterObject uses a hashtable where the key is the parameter name storageAccountName and the value is the parameter value mystorage123.

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