Template deployment methods in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Azure Resource Manager (ARM) template deployment scopes

Which deployment scope allows you to deploy resources at the subscription level, such as creating resource groups or policies?

A Management group scope

B Resource group scope

C Tenant scope

D Subscription scope

💡 Hint

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.

❓ Configuration

intermediate

Determining the output of an ARM template deployment command

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

A Plain text confirmation message only

B JSON object with deployment details including outputs and provisioning state

C Error message about missing subscription ID

D List of all resource groups in the subscription

💡 Hint

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.

❓ Architecture

advanced

Choosing the correct deployment method for multi-region resource deployment

You need to deploy identical resources to multiple Azure regions using ARM templates. Which deployment method best supports this scenario?

A Use a subscription-level deployment with location parameters for each region

B Deploy the template once at the management group scope

C Deploy the ARM template separately to each resource group in each region

D Use Azure Blueprints instead of ARM templates

💡 Hint

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.

❓ security

advanced

Securing sensitive data in ARM template deployments

Which method is the most secure way to handle sensitive information like passwords in ARM template deployments?

A Hardcode passwords directly in the ARM template parameters

B Store passwords in plain text files alongside the template

C Use Azure Key Vault references in the ARM template parameters

D Pass passwords as command line arguments without encryption

💡 Hint

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.

❓ service_behavior

expert

Behavior of incremental vs complete deployment modes in ARM templates

What happens to existing resources in a resource group when you deploy an ARM template using the complete mode?

A Resources not in the template are deleted from the resource group

B Resources not in the template remain unchanged in the resource group

C All resources in the subscription are deleted except those in the template

D Deployment fails if resources exist outside the template

💡 Hint

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.

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