ARM template resources section in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a resource type in the ARM template resources section.

Azure

"resources": [ { "type": "[1]", "apiVersion": "2021-04-01", "name": "myStorageAccount" } ]

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

AMicrosoft.Network/virtualNetworks

BMicrosoft.Compute/virtualMachines

CMicrosoft.Storage/storageAccounts

DMicrosoft.Web/sites

Attempts:

3 left

💡 Hint

Common Mistakes

Using a compute or network resource type instead of storage account type.

Misspelling the resource type string.

The type field specifies the resource type. For a storage account, it must be Microsoft.Storage/storageAccounts.

2fill in blank

medium

Complete the code to specify the API version for the resource.

Azure

"resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "[1]", "name": "myStorageAccount" } ]

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

A2020-01-01

B2019-06-01

C2018-02-01

D2021-04-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using outdated or unsupported API versions.

Using API versions for other resource types.

The apiVersion must be a valid and recent version supported by Azure for the resource type. '2021-04-01' is a valid API version for storage accounts.

3fill in blank

hard

Fix the error in the resource name property to correctly reference a parameter named 'storageName'.

Azure

"resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2021-04-01", "name": "[1]" } ]

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

A'storageName'

B[parameters('storageName')]

Cparameters.storageName

D[variables('storageName')]

Attempts:

3 left

💡 Hint

Common Mistakes

Using dot notation instead of expression syntax.

Using variable syntax instead of parameter syntax.

Using quotes without expression brackets.

In ARM templates, to reference a parameter, use the expression syntax: [parameters('parameterName')].

4fill in blank

hard

Fill both blanks to define the location and sku name for the storage account resource.

Azure

"resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2021-04-01", "name": "[parameters('storageName')]", "location": "[1]", "sku": { "name": "[2]" } } ]

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

A[parameters('location')]

Beastus

CStandard_LRS

DPremium_LRS

Attempts:

3 left

💡 Hint

Common Mistakes

Hardcoding location instead of using a parameter.

Using an invalid sku name.

The location is usually set from a parameter for flexibility, and the sku name defines the storage account type, such as 'Standard_LRS'.

5fill in blank

hard

Fill all three blanks to add tags with environment and department to the storage account resource.

Azure

"resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2021-04-01", "name": "[parameters('storageName')]", "location": "[parameters('location')]", "sku": { "name": "Standard_LRS" }, "tags": { "environment": "[1]", "department": "[2]", "owner": "[3]" } } ]

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

A[parameters('envTag')]

Bproduction

C[parameters('ownerTag')]

Dfinance

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing parameter syntax and hardcoded strings incorrectly.

Using quotes incorrectly around parameters.

Tags can be set using parameters for flexibility or hardcoded values. Here, environment and owner use parameters, and department is hardcoded as 'finance'.

Practice

1. What is the main purpose of the resources section in an ARM template?

easy

A. To list all cloud parts to create or update

B. To write scripts for manual deployment

C. To store user credentials securely

D. To monitor cloud resource usage

Solution

1. Step 1: Understand the role of the resources section

   The resources section defines what cloud parts (like servers, databases) to create or update automatically.

2. Step 2: Compare options with this role

   Only To list all cloud parts to create or update correctly describes this purpose. Other options describe unrelated tasks.

3. Final Answer:

   To list all cloud parts to create or update -> Option A

4. Quick Check:

   Resources section = list cloud parts [OK]

Hint: Resources section always defines cloud parts to deploy [OK]

Common Mistakes:

• Thinking resources section stores credentials
• Confusing resources with monitoring tools
• Assuming resources section is for scripts

2. Which of the following is a required property inside each resource in the resources section of an ARM template?

easy

A. version

B. dependsOn

C. location

D. tags

Solution

1. Step 1: Identify required properties for each resource

   Every Azure resource requires type, apiVersion, and name. The location property is required for regional resources to specify where the resource is created.

2. Step 2: Check options for required property

   location (location) is required. version is incorrect; the correct property is apiVersion. tags and dependsOn are optional.

3. Final Answer:

   location -> Option C

4. Quick Check:

   Location is required for resource placement [OK]

Hint: Location is required for regional resources [OK]

Common Mistakes:

• Confusing apiVersion with version
• Assuming tags are mandatory
• Thinking dependsOn is always required

3. Given this resource snippet in an ARM template's resources section:

{
  "type": "Microsoft.Storage/storageAccounts",
  "apiVersion": "2022-09-01",
  "name": "mystorageaccount",
  "location": "eastus",
  "sku": { "name": "Standard_LRS" },
  "kind": "StorageV2"
}

What will happen when this template is deployed?

medium

A. Deployment fails due to missing 'dependsOn' property

B. A new storage account named 'mystorageaccount' is created in East US

C. The storage account is created but with default SKU

D. The template will error because 'kind' is invalid

Solution

1. Step 1: Analyze resource properties

   The resource defines a storage account with a valid type, apiVersion, name, location, sku, and kind. All required fields are present and valid.

2. Step 2: Understand deployment behavior

   Since all required properties are correct, deployment will create the storage account named 'mystorageaccount' in 'eastus' with the specified SKU and kind. dependsOn is optional here.

3. Final Answer:

   A new storage account named 'mystorageaccount' is created in East US -> Option B

4. Quick Check:

   Valid resource properties = successful creation [OK]

Hint: Check required fields; missing dependsOn is okay if no dependencies [OK]

Common Mistakes:

• Thinking dependsOn is always mandatory
• Assuming default SKU applies if specified
• Believing 'kind' property is invalid

4. You have this resource in your ARM template's resources section:

{
  "type": "Microsoft.Web/sites",
  "apiVersion": "2021-02-01",
  "name": "mywebapp",
  "location": "westus"
}

Deployment fails with an error about missing properties. What is the likely cause?

medium

A. Missing 'properties' section with site configuration

B. Missing required 'kind' property for web app

C. Missing 'dependsOn' property for resource order

D. Missing 'sku' property defining pricing tier

Solution

1. Step 1: Review required properties for Microsoft.Web/sites

   Besides type, apiVersion, name, and location, a web app resource requires a properties section to define site settings.

2. Step 2: Identify missing required section

   The snippet lacks the properties section, causing deployment failure. sku and dependsOn are optional, and kind defaults to 'app' if omitted.

3. Final Answer:

   Missing 'properties' section with site configuration -> Option A

4. Quick Check:

   Web app needs properties section [OK]

Hint: Web apps require properties section; check for it [OK]

Common Mistakes:

• Assuming dependsOn is mandatory
• Confusing kind as required
• Ignoring properties section necessity

5. You want to deploy two resources in an ARM template: a storage account and a web app that uses that storage. How do you ensure the web app deploys only after the storage account is ready?

hard

A. Use the same 'apiVersion' for both resources

B. Place the web app resource before the storage account in the resources array

C. Set the web app's 'location' to the storage account's location

D. Add the storage account's name in the web app's 'dependsOn' property

Solution

1. Step 1: Understand resource deployment order control

   ARM templates use the dependsOn property to specify that one resource must finish deploying before another starts.

2. Step 2: Apply dependsOn for correct order

   Adding the storage account's resource name in the web app's dependsOn ensures the web app waits for the storage account to be ready.

3. Final Answer:

   Add the storage account's name in the web app's 'dependsOn' property -> Option D

4. Quick Check:

   dependsOn controls deployment order [OK]

Hint: Use dependsOn to order resource deployment [OK]

Common Mistakes:

• Thinking resource order in array controls deployment
• Believing apiVersion affects deployment order
• Assuming location controls deployment sequence