Bicep as ARM simplification in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Bicep Resource Declaration

Which of the following Bicep resource declarations correctly creates an Azure Storage Account with the name 'mystorageacct' in the 'eastus' region?

A

resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
  name: 'mystorageacct'
  location: 'eastus'
  sku: {
    name: 'Standard_LRS'
  }
}

B

resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
  name: 'mystorageacct'
  location: 'westus'
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
}

C

resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
  name: 'mystorageacct'
  location: 'eastus'
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
}

D

resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
  name: 'mystorageacct'
  location: 'eastus'
  kind: 'BlobStorage'
  sku: {
    name: 'Standard_LRS'
  }
}

💡 Hint

Remember that the location must be 'eastus' and the kind should be 'StorageV2' for a general-purpose storage account.

Option C correctly declares a Storage Account resource with the required properties: name, location 'eastus', kind 'StorageV2', and sku 'Standard_LRS'. Option C uses the wrong location 'westus'. Option C is missing the 'kind' property which is required. Option C uses 'BlobStorage' kind which is a different SKU type.

❓ Configuration

intermediate

Bicep Module Parameter Passing

Given a Bicep module that requires a parameter 'vmName' of type string, which option correctly passes the value 'myVM01' to this module?

Azure

module vmModule './vm.bicep' = {
  name: 'deployVM'
  params: {
    vmName: 'myVM01'
  }
}

A

module vmModule './vm.bicep' = {
  name: 'deployVM'
  params: {
    vmName: 'myVM01'
  }
}

B

module vmModule './vm.bicep' = {
  name: 'deployVM'
  vmName: 'myVM01'
}

C

module vmModule './vm.bicep' = {
  name: 'deployVM'
  parameters: {
    vmName: 'myVM01'
  }
}

D

module vmModule './vm.bicep' = {
  name: 'deployVM'
  args: {
    vmName: 'myVM01'
  }
}

💡 Hint

Check the correct keyword for passing parameters to a module in Bicep.

Option A uses the correct 'params' keyword to pass parameters to the module. Options B, C, and D use incorrect keywords ('vmName' directly, 'parameters', or 'args') which are invalid in Bicep module syntax.

❓ Architecture

advanced

Bicep Deployment Scope Selection

You want to deploy a Bicep template that creates a resource group and resources inside it in a single deployment. Which deployment scope should you use in your Bicep file to achieve this?

A Use 'targetScope = 'managementGroup'' to deploy the resource group and nested resources.

B Use 'targetScope = 'subscription'' to deploy the resource group and nested resources.

C Use 'targetScope = 'resourceGroup'' to deploy the resource group and nested resources.

D Use 'targetScope = 'tenant'' to deploy the resource group and nested resources.

💡 Hint

Creating a resource group requires subscription-level deployment scope.

To create a resource group and resources inside it in one deployment, the Bicep file must have 'targetScope = 'subscription'' because resource groups are subscription-level resources. 'resourceGroup' scope cannot create resource groups, only deploy inside existing ones.

❓ security

advanced

Secure Parameter Handling in Bicep

Which Bicep parameter declaration ensures that a sensitive value like an admin password is not logged or exposed during deployment?

A param adminPassword securestring

B param adminPassword string = 'P@ssw0rd!'

C param adminPassword string { secure: true }

D param adminPassword string

💡 Hint

Bicep has a special type for sensitive parameters.

Option A uses the 'securestring' type which marks the parameter as sensitive, preventing it from being logged or exposed. Option A is invalid syntax. Options B and D declare a normal string parameter which is not secure.

❓ service_behavior

expert

Bicep Output Behavior After Deployment

After deploying a Bicep template that outputs a storage account's primary endpoint URL, what will be the value of the output if the deployment fails halfway and the storage account resource was not created?

Azure

output storageEndpoint string = storageAccount.properties.primaryEndpoints.blob

A The output will be null because the resource was not created.

B The output will be an empty string.

C The output will contain the endpoint URL from the previous deployment.

D The deployment will fail and no outputs will be returned.

💡 Hint

Consider what happens to outputs when deployment fails.

If the deployment fails, no outputs are returned because the deployment did not complete successfully. Therefore, option D is correct. Outputs depend on successful resource creation.