Bicep as ARM simplification in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a resource group in Bicep.

Azure

resource myResourceGroup '[1]' = {
  name: 'myResourceGroup'
}

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

AMicrosoft.Storage/storageAccounts@2021-06-01

BMicrosoft.Compute/virtualMachines@2022-01-01

CMicrosoft.Resources/resourceGroups@2021-04-01

DMicrosoft.Network/virtualNetworks@2021-05-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using a resource type for virtual machines or storage accounts instead of resource groups.

Omitting the API version.

The resource type for a resource group in Bicep is Microsoft.Resources/resourceGroups@2021-04-01. This defines the resource group itself.

2fill in blank

medium

Complete the code to declare a storage account resource in Bicep.

Azure

resource storageAccount '[1]' = {
  name: 'mystorageaccount',
  location: 'westus',
  sku: {
    name: 'Standard_LRS'
  },
  kind: 'StorageV2'
}

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

AMicrosoft.Storage/storageAccounts@2021-06-01

BMicrosoft.Network/virtualNetworks@2021-05-01

CMicrosoft.Resources/resourceGroups@2021-04-01

DMicrosoft.Compute/virtualMachines@2022-01-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using resource types for virtual machines or virtual networks instead of storage accounts.

Forgetting to specify the API version.

The correct resource type for a storage account in Bicep is Microsoft.Storage/storageAccounts@2021-06-01. This defines the storage account resource.

3fill in blank

hard

Fix the error in the Bicep code by completing the resource type for a virtual machine.

Azure

resource vm '[1]' = {
  name: 'myVM',
  location: 'centralus',
  properties: {}
}

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

AMicrosoft.Storage/storageAccounts@2021-06-01

BMicrosoft.Compute/virtualMachines@2022-01-01

CMicrosoft.Network/virtualNetworks@2021-05-01

DMicrosoft.Resources/resourceGroups@2021-04-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using storage account or resource group resource types for a VM.

Omitting the API version.

The resource type for a virtual machine in Bicep is Microsoft.Compute/virtualMachines@2022-01-01. This is required to correctly deploy a VM.

4fill in blank

hard

Fill both blanks to declare a virtual network with an address prefix and a subnet.

Azure

resource vnet '[1]' = {
  name: 'myVnet',
  location: 'eastus2',
  properties: {
    addressSpace: {
      addressPrefixes: [ '[2]' ]
    },
    subnets: [
      {
        name: 'default',
        properties: {
          addressPrefix: '10.0.0.0/24'
        }
      }
    ]
  }
}

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

AMicrosoft.Network/virtualNetworks@2021-05-01

BMicrosoft.Compute/virtualMachines@2022-01-01

C10.0.0.0/16

DStandard_LRS

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong resource type for virtual networks.

Using a subnet prefix as the main address prefix.

The resource type for a virtual network is Microsoft.Network/virtualNetworks@2021-05-01. The address prefix for the network is typically a larger range like 10.0.0.0/16 to include subnets.

5fill in blank

hard

Fill all three blanks to create a storage account with a SKU, kind, and access tier.

Azure

resource storage '[1]' = {
  name: 'storageacct',
  location: 'westus2',
  sku: {
    name: '[2]'
  },
  kind: '[3]',
  properties: {
    accessTier: 'Hot'
  }
}

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

AMicrosoft.Storage/storageAccounts@2021-06-01

BStandard_LRS

CStorageV2

DMicrosoft.Compute/virtualMachines@2022-01-01

Attempts:

3 left

💡 Hint

Common Mistakes

Using virtual machine resource types for storage accounts.

Mixing SKU names with kind values.

The storage account resource type is Microsoft.Storage/storageAccounts@2021-06-01. The SKU name Standard_LRS defines the replication type. The kind StorageV2 is the general-purpose v2 storage account.

Practice

1. What is the main purpose of Bicep in Azure infrastructure management?

easy

A. To monitor Azure resources in real-time

B. To replace Azure CLI commands

C. To create virtual machines automatically

D. To simplify writing and managing Azure resource templates

Solution

1. Step 1: Understand Bicep's role

   Bicep is designed to simplify the process of writing infrastructure as code for Azure by providing a cleaner syntax than raw ARM templates.

2. Step 2: Compare with other options

   Options A, B, and C describe other Azure tools or features, not Bicep's main purpose.

3. Final Answer:

   To simplify writing and managing Azure resource templates -> Option D

4. Quick Check:

   Bicep simplifies Azure templates = D [OK]

Hint: Bicep makes Azure templates easier to write and read [OK]

Common Mistakes:

• Confusing Bicep with Azure CLI
• Thinking Bicep creates resources automatically
• Assuming Bicep monitors resources

2. Which of the following is the correct way to declare a string parameter named location in a Bicep file?

easy

A. param location string

B. parameter location = 'string'

C. var location string

D. resource location string

Solution

1. Step 1: Recall Bicep parameter syntax

   In Bicep, parameters are declared using the keyword param followed by the name and type, e.g., param location string.

2. Step 2: Eliminate incorrect options

   parameter location = 'string' uses incorrect syntax; var location string uses var which is for variables, not parameters; resource location string uses resource which is for resources.

3. Final Answer:

   param location string -> Option A

4. Quick Check:

   Parameter declaration = param name type [OK]

Hint: Use 'param' keyword for parameters in Bicep [OK]

Common Mistakes:

• Using 'var' instead of 'param' for parameters
• Confusing resource declaration with parameter
• Incorrect assignment syntax for parameters

3. Given this Bicep snippet:

param storageAccountName string = 'mystorage'
resource storageAccount 'Microsoft.Storage/storageAccounts@2021-04-01' = {
  name: storageAccountName
  location: 'eastus'
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
}

What will be the name of the deployed storage account?

medium

A. mystorage

B. storageAccountName

C. Standard_LRS

D. eastus

Solution

1. Step 1: Identify the parameter value

   The parameter storageAccountName is set to the string 'mystorage'.

2. Step 2: Check resource name assignment

   The resource's name property uses the parameter storageAccountName, so the deployed storage account will be named 'mystorage'.

3. Final Answer:

   mystorage -> Option A

4. Quick Check:

   Resource name = parameter value 'mystorage' [OK]

Hint: Resource name uses parameter value directly [OK]

Common Mistakes:

• Confusing parameter name with its value
• Choosing SKU or location as name
• Assuming default resource name

4. You wrote this Bicep code:

param location string
var location = 'westus'
resource vm 'Microsoft.Compute/virtualMachines@2022-03-01' = {
  name: 'myVM'
  location: location
}

What is the error in this code?

medium

A. Missing SKU property in the resource

B. Resource name must be a parameter, not a string

C. Variable and parameter have the same name causing conflict

D. Location property cannot be a variable

Solution

1. Step 1: Identify naming conflict

   Both a parameter and a variable are named location, which causes a conflict in Bicep because names must be unique in the same scope.

2. Step 2: Check other options

   Resource name can be a string literal; SKU is not mandatory for all resources; location can be a variable if no conflict exists.

3. Final Answer:

   Variable and parameter have the same name causing conflict -> Option C

4. Quick Check:

   Duplicate names cause errors in Bicep [OK]

Hint: Avoid using same name for param and var [OK]

Common Mistakes:

• Thinking resource name must be a parameter
• Assuming SKU is always required
• Believing location cannot be variable

5. You want to deploy two storage accounts in different locations using Bicep. Which approach correctly uses a loop to create these resources?

hard

A. param locations string = 'eastus,westus'
resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = {
name: 'storage'
location: locations
kind: 'StorageV2'
sku: { name: 'Standard_LRS' }
}

B. var locations = ['eastus', 'westus']
resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = [for loc in locations: {
name: 'storage${loc}'
location: loc
kind: 'StorageV2'
sku: { name: 'Standard_LRS' }
}]

C. var locations = ['eastus', 'westus']
resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = {
name: 'storage'
location: locations
kind: 'StorageV2'
sku: { name: 'Standard_LRS' }
}

D. param locations array = ['eastus', 'westus']
resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = for loc in locations {
name: 'storage'
location: loc
kind: 'StorageV2'
sku: { name: 'Standard_LRS' }
}

Solution

1. Step 1: Understand Bicep loop syntax

   Bicep uses array loops with the syntax [for item in array: { ... }] to create multiple resources.

2. Step 2: Analyze each option

   var locations = ['eastus', 'westus'] resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = [for loc in locations: { name: 'storage${loc}' location: loc kind: 'StorageV2' sku: { name: 'Standard_LRS' } }] correctly uses a variable array and a loop to create multiple storage accounts with unique names and locations. Options B and C misuse the location property by assigning an array directly. param locations array = ['eastus', 'westus'] resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = for loc in locations { name: 'storage' location: loc kind: 'StorageV2' sku: { name: 'Standard_LRS' } } has incorrect loop syntax missing square brackets.

3. Final Answer:

   var locations = ['eastus', 'westus'] resource storageAccounts 'Microsoft.Storage/storageAccounts@2021-04-01' = [for loc in locations: { name: 'storage${loc}' location: loc kind: 'StorageV2' sku: { name: 'Standard_LRS' } }] -> Option B

4. Quick Check:

   Bicep loops use [for item in array: {...}] [OK]

Hint: Use [for item in array: {...}] for resource loops [OK]

Common Mistakes:

• Assigning array directly to location property
• Incorrect loop syntax without brackets
• Using string instead of array for multiple locations