ARM template structure in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the ARM template schema.

Azure

{
  "$schema": "[1]",
  "contentVersion": "1.0.0.0",
  "resources": []
}

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

Ahttps://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#

Bhttps://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#

Chttps://schema.management.azure.com/schemas/2017-05-01/deploymentTemplate.json#

Dhttps://schema.management.azure.com/schemas/2018-02-01/deploymentTemplate.json#

Attempts:

3 left

💡 Hint

Common Mistakes

Using a schema URL for a different Azure service

Using a schema URL with an incorrect version

The ARM template schema URL defines the structure and validation rules. The 2015-01-01 version is the base schema for ARM templates.

2fill in blank

medium

Complete the code to specify the ARM template content version.

Azure

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  "contentVersion": "[1]",
  "resources": []
}

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

A1.0.0.0

B2020-01-01

Clatest

Dv1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a date format instead of a version number

Using keywords like 'latest' instead of a version string

The contentVersion is a string that represents the version of the template content. It usually follows a numeric format like 1.0.0.0.

3fill in blank

hard

Fix the error in the ARM template by completing the missing key for resources.

Azure

{
  "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "[1]": []
}

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

Aparameters

Bvariables

Cresources

Doutputs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'parameters' or 'variables' instead of 'resources'

Omitting the 'resources' key entirely

The 'resources' key is required to define the Azure resources to deploy in the ARM template.

4fill in blank

hard

Fill both blanks to define parameters and variables sections in the ARM template.

Azure

{
  "[1]": {
    "location": {
      "type": "string",
      "defaultValue": "eastus"
    }
  },
  "[2]": {
    "storageAccountName": "mystorageaccount"
  }
}

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

Aparameters

Bresources

Cvariables

Doutputs

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping 'parameters' and 'variables' keys

Using 'resources' or 'outputs' in these places

'parameters' define inputs to the template, and 'variables' define reusable values inside the template.

5fill in blank

hard

Fill both blanks to define an output that returns the storage account name.

Azure

{
  "outputs": {
    "storageAccountNameOutput": {
      "type": "string",
      "value": "[[1]('[2]')]"
    }
  }
}

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

Areference

BstorageAccountName

C)

D(

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong function names like 'get' or 'output'

Incorrect parentheses placement

The output uses the reference function to get the property value. The syntax is reference('resourceName').

Practice

1. Which section in an ARM template is used to define the Azure resources you want to create?

easy

A. outputs

B. parameters

C. resources

D. variables

Solution

1. Step 1: Understand ARM template sections

   An ARM template has sections like parameters, variables, resources, and outputs.

2. Step 2: Identify the section for Azure resources

   The 'resources' section lists the Azure services and components to create.

3. Final Answer:

   resources -> Option C

4. Quick Check:

   Resources section defines Azure resources [OK]

Hint: Resources section always holds Azure resource definitions [OK]

Common Mistakes:

• Confusing parameters with resources
• Thinking variables define resources
• Mixing outputs with resource definitions

2. Which of the following is the correct way to start an ARM template JSON file?

easy

A. { "parameters": { }, "variables": { }, "resources": [ ] }

B. [ "parameters", "variables", "resources" ]

C.

D. parameters: {}, variables: {}, resources: []

Solution

1. Step 1: Recognize ARM template format

   ARM templates are JSON files with keys like parameters, variables, and resources.

2. Step 2: Check JSON syntax correctness

   { "parameters": { }, "variables": { }, "resources": [ ] } uses valid JSON object syntax with keys and empty objects/arrays.

3. Final Answer:

   { "parameters": { }, "variables": { }, "resources": [ ] } -> Option A

4. Quick Check:

   ARM templates start with JSON objects [OK]

Hint: ARM templates are JSON objects with keys, not arrays or XML [OK]

Common Mistakes:

• Using array brackets instead of object braces
• Writing XML tags instead of JSON
• Omitting quotes around keys

3. Given this ARM template snippet:

{ "parameters": { "vmName": { "type": "string" } }, "variables": { "location": "eastus" }, "resources": [ { "type": "Microsoft.Compute/virtualMachines", "name": "[parameters('vmName')]", "location": "[variables('location')]" } ] }

What will be the location of the virtual machine if the parameter vmName is set to "MyVM"?

medium

A. MyVM

B. westus

C. undefined

D. eastus

Solution

1. Step 1: Identify location value in variables

   The variable 'location' is set to "eastus" in the variables section.

2. Step 2: Understand resource location assignment

   The VM's location uses the variable 'location', so it will be "eastus" regardless of vmName.

3. Final Answer:

   eastus -> Option D

4. Quick Check:

   Location comes from variables, not parameters [OK]

Hint: Resource location uses variables, not parameters [OK]

Common Mistakes:

• Confusing vmName parameter with location
• Assuming location is from parameters
• Ignoring variable usage syntax

4. Identify the error in this ARM template snippet:

{ "parameters": { "storageName": { "type": "string" } }, "resources": [ { "type": "Microsoft.Storage/storageAccounts", "name": "storageName", "location": "eastus" } ] }

medium

A. The location value must be a variable, not a string

B. The resource name should use parameter syntax with brackets

C. Parameters section cannot be empty

D. Resource type is invalid

Solution

1. Step 1: Check resource name usage

   The resource name is set as "storageName" string, but it should reference the parameter.

2. Step 2: Correct parameter reference syntax

   Parameters are referenced with "[parameters('storageName')]" to use the parameter value.

3. Final Answer:

   The resource name should use parameter syntax with brackets -> Option B

4. Quick Check:

   Parameter references need brackets and function call [OK]

Hint: Use [parameters('name')] to reference parameters in resources [OK]

Common Mistakes:

• Using parameter name as plain string
• Thinking location must be variable
• Assuming resource type is wrong

5. You want to output the public IP address of a VM created in your ARM template. Which section should you add this output to, and what is the correct syntax to reference the IP address property named "ipAddress" from a resource named "myPublicIP"?

hard

A. Add to outputs section with "ip": { "value": "[reference('myPublicIP').ipAddress]" }

B. Add to variables section with "ip": "myPublicIP.ipAddress"

C. Add to parameters section with "ipAddress": { "type": "string" }

D. Add to resources section with "outputs": { "ip": "myPublicIP.ipAddress" }

Solution

1. Step 1: Identify output section usage

   Outputs section is used to return values after deployment, like IP addresses.

2. Step 2: Use correct syntax to reference resource property

   Use the reference() function with resource name and property: "[reference('myPublicIP').ipAddress]".

3. Final Answer:

   Add to outputs section with "ip": { "value": "[reference('myPublicIP').ipAddress]" } -> Option A

4. Quick Check:

   Outputs use reference() to get resource properties [OK]

Hint: Use outputs section and reference() function for resource properties [OK]

Common Mistakes:

• Putting outputs in variables or parameters
• Using dot notation without reference()
• Misplacing outputs inside resources