Knowledge check

3 minutes

Your colleagues have asked you to help them work with this template:

param number int
param name string
param name2 string

var location = 'australiaeast'

resource virtualNetwork 'Microsoft.Network/virtualNetworks@2020-11-01' = {
  name: name
  location: location
  properties: {
    addressSpace:{
      addressPrefixes:[
        '10.0.0.0/16'
      ]
    }
    subnets: [for i in range(1, number): {
      name: 'subnet-${i}'
      properties: {
        addressPrefix: '10.0.${i}.0/24'
      }
    }]
  }
}

resource storageAccount 'Microsoft.Storage/storageAccounts@2021-01-01' = {
  name: name2
  location: location
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
}

You're refactoring the template to make it easier for other people in your organization to use.

Which of these steps should you take?

Rename the number, name, and name2 parameters.

Create a module for each resource.

Create a new output to pass the storage account key back to the user.

You want to ensure that your template's users provide valid inputs for the number parameter. How should you do this?

Apply parameter decorators.

Apply Azure role-based access control (RBAC) on your deployment scope.

Hard-code as many values into templates as possible.

What is one of the benefits of using configuration sets for your Bicep templates?

You can expose all of your resources' properties to your template's users as parameters.

You can abstract the internal complexity of the template by providing a simple set of options.

You can structure your template and group elements in any order.

You must answer all questions before checking your work.

Continue

Feedback