Azure Resource Manager (ARM) concept - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the resource group location in an ARM template.

Azure

{
  "location": "[1]"
}

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

Avariables('location')

BresourceGroup()

Ceastus

Dparameters('location')

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function like resourceGroup() instead of a string.

Leaving the location blank or misspelling the region name.

The location property in an ARM template specifies the Azure region where the resource group or resource will be deployed. It must be a valid Azure region string like eastus.

2fill in blank

medium

Complete the code to reference a parameter named 'storageAccountName' in an ARM template.

Azure

"name": "[1]"

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

Aparameters('storageAccountName')

Bvariables('storageAccountName')

CresourceGroup().storageAccountName

Doutputs('storageAccountName')

Attempts:

3 left

💡 Hint

Common Mistakes

Using variables() instead of parameters().

Trying to access parameters as properties of resourceGroup().

To use a parameter value in an ARM template, you use the parameters() function with the parameter name.

3fill in blank

hard

Fix the error in the ARM template snippet to correctly define a resource type.

Azure

"type": "[1]"

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

AstorageAccounts/Microsoft.Storage

BMicrosoft.Storage/storageAccounts

CMicrosoft.Storage:storageAccounts

DstorageAccounts

Attempts:

3 left

💡 Hint

Common Mistakes

Reversing the order of provider and resource type.

Using a colon instead of a slash.

Using only the resource type without the provider namespace.

The type property must be the full resource provider namespace followed by the resource type, separated by a slash.

4fill in blank

hard

Fill both blanks to create a resource with a name from parameters and a location from variables.

Azure

{
  "name": "[1]",
  "location": "[2]"
}

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

Aparameters('vmName')

Bvariables('location')

Cparameters('location')

Dvariables('vmName')

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing parameters and variables for name and location.

Using parameters for location when it is stored in variables.

The resource name is usually set from a parameter like vmName, and location can be set from a variable holding the location string.

5fill in blank

hard

Fill all three blanks to define a resource with type, apiVersion, and dependsOn properties.

Azure

{
  "type": "[1]",
  "apiVersion": "[2]",
  "dependsOn": ["[3]"]
}

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

AMicrosoft.Compute/virtualMachines

B2021-07-01

CMicrosoft.Network/networkInterfaces/myNic

D2020-06-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong API version strings.

Incorrect resource type format.

Not specifying dependsOn or using wrong resource ID.

The type is the resource type, apiVersion is the API version string, and dependsOn lists resource IDs that must be created first.

Practice

1. What is the main purpose of Azure Resource Manager (ARM)?

easy

A. To write code for mobile applications

B. To manage and organize cloud resources as a group

C. To monitor network traffic only

D. To create virtual machines manually

Solution

1. Step 1: Understand ARM's role

   ARM is designed to help manage cloud resources together, not individually.

2. Step 2: Compare options

   Options B, C, and D describe unrelated tasks, while A correctly describes ARM's purpose.

3. Final Answer:

   To manage and organize cloud resources as a group -> Option B

4. Quick Check:

   ARM manages resources as a group = A [OK]

Hint: ARM groups resources for easy management [OK]

Common Mistakes:

• Thinking ARM is only for virtual machines
• Confusing ARM with monitoring tools
• Assuming ARM writes application code

2. Which of the following is the correct way to deploy resources using ARM templates?

easy

A. Using FTP to upload ARM templates

B. Writing scripts in Python only

C. Using Azure Portal or Azure CLI with the ARM template

D. Manually creating resources without templates

Solution

1. Step 1: Identify deployment methods

   ARM templates are deployed via Azure Portal or Azure CLI commands.

2. Step 2: Eliminate incorrect options

   Python scripts and FTP are not standard deployment methods for ARM templates; manual creation ignores automation benefits.

3. Final Answer:

   Using Azure Portal or Azure CLI with the ARM template -> Option C

4. Quick Check:

   Deploy ARM templates via Portal or CLI = D [OK]

Hint: Deploy ARM templates via Portal or CLI commands [OK]

Common Mistakes:

• Thinking ARM templates deploy only with scripts
• Assuming manual creation is deployment
• Confusing FTP with deployment method

3. Given this ARM template snippet:

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2021-04-01",
      "name": "mystorageaccount",
      "location": "eastus",
      "sku": { "name": "Standard_LRS" },
      "kind": "StorageV2"
    }
  ]
}

What resource will this template create when deployed?

medium

A. A storage account named mystorageaccount in East US region

B. A virtual machine named mystorageaccount

C. A database named mystorageaccount

D. A network interface named mystorageaccount

Solution

1. Step 1: Analyze resource type in template

   The resource type is "Microsoft.Storage/storageAccounts", which means a storage account.

2. Step 2: Check resource properties

   The name is "mystorageaccount" and location is "eastus", confirming the storage account details.

3. Final Answer:

   A storage account named mystorageaccount in East US region -> Option A

4. Quick Check:

   Resource type storageAccounts = storage account = A [OK]

Hint: Resource type defines what is created in ARM template [OK]

Common Mistakes:

• Confusing storage account with virtual machine
• Ignoring resource type and focusing on name
• Assuming location affects resource type

4. You try to deploy an ARM template but get an error saying the resource name is invalid. What is the most likely cause?

medium

A. The template schema URL is missing

B. The location is not specified

C. The API version is too old

D. The resource name contains unsupported characters

Solution

1. Step 1: Understand error message

   An invalid resource name error usually means the name has characters not allowed by Azure naming rules.

2. Step 2: Review other options

   Missing schema URL or old API version cause different errors; location missing usually triggers a different message.

3. Final Answer:

   The resource name contains unsupported characters -> Option D

4. Quick Check:

   Invalid name error = unsupported characters in name = B [OK]

Hint: Check resource name for invalid characters first [OK]

Common Mistakes:

• Assuming schema URL causes name errors
• Ignoring naming rules for resources
• Thinking location omission causes name errors

5. You want to deploy multiple resources together and ensure they are created in the right order using ARM templates. Which feature should you use?

hard

A. Define dependencies between resources using the "dependsOn" property

B. Deploy each resource separately in different templates

C. Use manual deployment steps outside ARM

D. Create resources without specifying order

Solution

1. Step 1: Identify how ARM manages resource order

   ARM uses the "dependsOn" property to specify which resources must be created first.

2. Step 2: Evaluate other options

   Deploying separately or manually loses automation benefits; no order risks deployment failures.

3. Final Answer:

   Define dependencies between resources using the "dependsOn" property -> Option A

4. Quick Check:

   Use dependsOn to control deployment order = C [OK]

Hint: Use dependsOn to set resource creation order [OK]

Common Mistakes:

• Deploying resources separately instead of together
• Ignoring dependsOn and causing deployment errors
• Relying on manual steps outside ARM