Bicep syntax and modules in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Bicep in Azure?

Bicep is a simple language to write Azure infrastructure as code. It helps you create and manage Azure resources easily without complex JSON.

beginner

How do you declare a resource in Bicep?

You use the resource keyword followed by a name, type, and properties. For example:
resource storageAccount 'Microsoft.Storage/storageAccounts@2021-04-01' = { name: 'mystorage', location: 'eastus' }

intermediate

What is a module in Bicep?

A module is a separate Bicep file you can reuse. It helps organize code by splitting complex templates into smaller parts.

intermediate

How do you use a module in a Bicep file?

You declare it with the module keyword, give it a name, specify the path to the module file, and pass parameters if needed. Example:
module myModule './module.bicep' = { params: { param1: 'value' } }

intermediate

Why use modules in Bicep templates?

Modules make your templates easier to manage, reuse, and test. They help keep code clean and reduce mistakes by separating concerns.

Which keyword is used to declare a resource in Bicep?

A resource

B module

C param

D var

The resource keyword declares Azure resources in Bicep.

What file extension do Bicep files use?

A .azcli

B .json

C .bicep

D .yaml

Bicep files use the .bicep extension.

How do you include a module in a Bicep file?

A Using the <code>resource</code> keyword

B Using the <code>module</code> keyword

C Using the <code>import</code> keyword

D Using the <code>include</code> keyword

Modules are included with the module keyword.

What is the main benefit of using modules in Bicep?

A Faster deployment speed

B Automatic resource scaling

C Improved security

D Better code organization and reuse

Modules help organize code and allow reuse across templates.

Which of these is a valid way to pass parameters to a module?

A params: { param1: 'value' }

B parameters: { param1: 'value' }

C args: { param1: 'value' }

D inputs: { param1: 'value' }

Parameters are passed using the params property.

Explain how to declare and use a module in a Bicep template.

Think about how you include and configure reusable parts.

Describe the benefits of using Bicep modules in managing Azure infrastructure.

Consider how splitting code helps in real life projects.

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