Knowledge check

Completed

Consider the following two Bicep files.

main.bicep:

module storage1 'modules/stor.bicep' = {
  name: 'my-storage'
}

modules/stor.bicep:

resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' = {
  name: 'mystorageaccount'
  location: resourceGroup().location
  kind: 'StorageV2'
  sku: {
    name: 'Premium_LRS'
  }
}

1.

You deploy the main.bicep file with the default settings. You open the Azure portal and look at the deployment history for the resource group. What do you see?

A single deployment named main.

Two deployments. One is named main and the other is named storage1.

Two deployments. One is named main and the other is named my-storage.

2.

You plan to update the main.bicep file to add another resource. The new resource needs access to the key of the storage account created in the module. What should you do?

Create an output in the module and set its value to the storage account's connection string.

Use a key vault to create a secret.

You don't need to do anything. Properties for all the resources defined in the module are automatically available to the parent template.

3.

Your colleague has created a large Bicep file that you want to decompose into modules. You want to identify the resources that should be defined together in each module. Which tool can you consider using to help you achieve this task?

Use the Bicep visualizer.

Use the Bicep linter.

Use the Azure documentation for ARM templates.

You must answer all questions before checking your work.