Bicep syntax and modules in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a string parameter named 'location'.

Azure

param location [1]

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

Astring

Bint

Cbool

Dobject

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong type like int or bool for a text parameter.

Forgetting to specify the type after the parameter name.

The param keyword declares a parameter. To specify its type as text, use string.

2fill in blank

medium

Complete the code to create a resource of type 'Microsoft.Storage/storageAccounts' with the name 'storageAccount1'.

Azure

resource storageAccount1 '[1]' = {
  name: 'storageaccount1'
  location: 'eastus'
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
}

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

AMicrosoft.Compute/virtualMachines@2021-04-01

BMicrosoft.Network/virtualNetworks@2021-02-01

CMicrosoft.Storage/storageAccounts@2021-04-01

DMicrosoft.Web/sites@2021-01-15

Attempts:

3 left

💡 Hint

Common Mistakes

Using a resource type for a different service like virtual machines.

Omitting the API version after the '@' symbol.

The resource type for Azure Storage accounts is Microsoft.Storage/storageAccounts. The version specifies the API version.

3fill in blank

hard

Fix the error in the module declaration by completing the missing keyword.

Azure

module myModule '[1]' = {
  name: 'exampleModule'
  params: {
    location: 'westus'
  }
}

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

Adeploy.bicep

Bmodule.bicep

Cstorage.bicep

Dmain.bicep

Attempts:

3 left

💡 Hint

Common Mistakes

Using an incorrect or non-existing file name.

Forgetting to include the file extension '.bicep'.

The module keyword is followed by the path to the Bicep file to deploy. Here, main.bicep is the correct file name.

4fill in blank

hard

Fill both blanks to define an output named 'storageAccountId' that returns the resource ID of 'storageAccount1'.

Azure

output storageAccountId [1] = storageAccount1[2]

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

Astring

B.id

C.name

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong output type like int.

Accessing the resource name instead of its ID.

Outputs need a type, here string. The resource ID is accessed with .id.

5fill in blank

hard

Fill both blanks to declare a parameter 'tags' as an object with a default empty value.

Azure

param tags [1] = [2]

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

Aobject

B{}

C[]

Dstring

Attempts:

3 left

💡 Hint

Common Mistakes

Using array brackets [] instead of object braces {}.

Setting the type to string instead of object.

The parameter type is object and the default empty object is {}.

Practice

1. What is the main purpose of a module in Bicep?

easy

A. To reuse and organize infrastructure code by calling other Bicep files

B. To define variables inside a Bicep file

C. To store output values only

D. To create a new Azure subscription

Solution

1. Step 1: Understand what a module does

   A module in Bicep is a way to include and reuse other Bicep files, helping organize code.

2. Step 2: Compare options to the definition

   Only To reuse and organize infrastructure code by calling other Bicep files correctly describes modules as reusable code blocks. Variables and outputs are different concepts, and creating subscriptions is unrelated.

3. Final Answer:

   To reuse and organize infrastructure code by calling other Bicep files -> Option A

4. Quick Check:

   Module = reusable code block [OK]

Hint: Modules call other files to reuse code easily [OK]

Common Mistakes:

• Confusing modules with variables
• Thinking modules only store outputs
• Believing modules create Azure subscriptions

2. Which of the following is the correct syntax to declare a module in Bicep?

easy

A. module myModule = 'module.bicep' {}

B. module myModule 'module.bicep' = {}

C. module 'myModule' = module.bicep {}

D. module 'myModule' 'module.bicep' {}

Solution

1. Step 1: Recall module declaration syntax

   The correct syntax is: module <name> '<path>' = {}.

2. Step 2: Match options to syntax

   module myModule 'module.bicep' = {} matches the correct syntax exactly. Other options have misplaced quotes or assignment operators.

3. Final Answer:

   module myModule 'module.bicep' = {} -> Option B

4. Quick Check:

   module name 'file' = {} [OK]

Hint: Use: module name 'file.bicep' = {} [OK]

Common Mistakes:

• Putting quotes around the module name
• Using = before the file path
• Omitting the equals sign

3. Given this Bicep code snippet, what will be the output value of moduleOutput?

module storageModule 'storage.bicep' = {
  name: 'storage1'
}

output moduleOutput string = storageModule.outputs.storageAccountName

medium

A. An error because outputs cannot be accessed from modules

B. The module file path 'storage.bicep'

C. The name of the storage account defined inside storage.bicep

D. The string 'storage1'

Solution

1. Step 1: Understand module outputs

   Modules can expose outputs which can be accessed using moduleName.outputs.outputName.

2. Step 2: Analyze the code snippet

   The output moduleOutput gets the value of storageAccountName from the module's outputs, which is the storage account name defined inside storage.bicep.

3. Final Answer:

   The name of the storage account defined inside storage.bicep -> Option C

4. Quick Check:

   module.outputs = module data access [OK]

Hint: Access module outputs with moduleName.outputs.outputName [OK]

Common Mistakes:

• Thinking outputs can't be accessed from modules
• Confusing module name with file path
• Assuming output is the module instance name

4. Identify the error in this Bicep module usage:

module webAppModule 'webapp.bicep' = {
  name: 'webApp1'
  params: {
    location: 'eastus'
  }
}

medium

A. Incorrect keyword 'params' should be 'parameters'

B. Module name cannot contain numbers

C. Module file path must be absolute

D. Missing equals sign after 'name'

Solution

1. Step 1: Check parameter passing syntax in modules

   In Bicep, module parameters can be passed directly as properties (e.g., location: 'eastus') or nested under parameters: { ... }. params is not a valid keyword.

2. Step 2: Identify the error

   The code uses invalid params:, which should be parameters: for nested parameters.

3. Final Answer:

   Incorrect keyword 'params' should be 'parameters' -> Option A

4. Quick Check:

   parameters: { } for nested params [OK]

Hint: Use 'parameters:' not 'params' for nested params [OK]

Common Mistakes:

• Using 'params' instead of 'parameters'
• Thinking module names cannot contain numbers
• Believing file paths must be absolute

5. You want to create a reusable Bicep module for a virtual network that accepts a parameter for the address prefix and outputs the subnet ID. How should you define the module's parameter and output to follow best practices?

hard

A. Declare the address prefix as an output and subnet ID as a parameter

B. Use a variable for address prefix and no output since subnet ID is internal

C. Hardcode the address prefix and output the subnet name instead of ID

D. Declare a param addressPrefix string and an output subnetId string in the module file

Solution

1. Step 1: Define parameters for input values

   Best practice is to declare inputs as parameters so the module is flexible. Here, param addressPrefix string allows passing different address prefixes.

2. Step 2: Define outputs for important results

   Outputs share useful info back to the caller. The subnet ID is important to output as output subnetId string.

3. Final Answer:

   Declare a param addressPrefix string and an output subnetId string in the module file -> Option D

4. Quick Check:

   Parameters input, outputs share results [OK]

Hint: Use param for inputs, output for results [OK]

Common Mistakes:

• Using variables instead of parameters for inputs
• Not outputting needed resource IDs
• Mixing parameters and outputs roles