ARM template structure in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the main sections of an ARM template

Which of the following lists the main sections you will find in a valid ARM template?

A settings, modules, scripts, outputs

B parameters, variables, resources, outputs

C inputs, functions, services, results

D configurations, templates, deployments, logs

💡 Hint

Think about the parts that define inputs, reusable values, what to create, and what to return.

An ARM template typically contains parameters for inputs, variables for reusable values, resources to define what Azure services to deploy, and outputs to return information after deployment.

❓ Configuration

intermediate

Determine the output value from an ARM template snippet

Given this ARM template output section, what will be the value of the output named 'storageAccountName' after deployment?

{
  "outputs": {
    "storageAccountName": {
      "type": "string",
      "value": "mystorageaccount123"
    }
  }
}

A null

B "storageAccountName"

C "mystorageaccount123"

D An error occurs because the value is not a parameter

💡 Hint

Outputs return the value specified in the 'value' field.

The output named 'storageAccountName' returns the string value exactly as defined: "mystorageaccount123".

❓ Architecture

advanced

Choose the correct resource declaration in an ARM template

Which option correctly declares a resource of type 'Microsoft.Storage/storageAccounts' with API version '2022-09-01' and name 'mystorageaccount'?

A

{
  "type": "Microsoft.Storage/storageAccounts",
  "apiVersion": "2022-09-01",
  "name": "mystorageaccount",
  "location": "eastus",
  "properties": {}
}

B

{
  "resourceType": "Microsoft.Storage/storageAccounts",
  "version": "2022-09-01",
  "resourceName": "mystorageaccount",
  "region": "eastus",
  "settings": {}
}

C

{
  "type": "Microsoft.Storage/storageAccounts",
  "apiVersion": "2022-09-01",
  "name": "storageaccount",
  "location": "eastus",
  "properties": {}
}

D

{
  "type": "Microsoft.Storage/storageAccounts",
  "apiVersion": "2021-04-01",
  "name": "mystorageaccount",
  "location": "eastus",
  "properties": {}
}

💡 Hint

Check the exact property names and values for resource declaration.

Option A uses the correct property names: 'type', 'apiVersion', 'name', 'location', and 'properties'. It also uses the correct API version and resource name.

Option A uses incorrect property names. Option A uses an older API version. Option A uses a different resource name.

❓ security

advanced

Identify the security risk in an ARM template snippet

What is the main security risk in this ARM template parameter declaration?

{
  "parameters": {
    "adminPassword": {
      "type": "string",
      "defaultValue": "P@ssw0rd123",
      "metadata": {
        "description": "Admin password"
      }
    }
  }
}

A There is no security risk in this declaration

B The parameter type should be 'secureString' instead of 'string'

C The metadata description reveals the password

D The password is hardcoded as a default value, exposing sensitive data

💡 Hint

Think about how sensitive information should be handled in templates.

Hardcoding passwords in defaultValue exposes them in the template, which is a security risk. Instead, use parameters without default values or use 'secureString' type.

❓ service_behavior

expert

Predict the deployment behavior with missing required properties

If an ARM template resource declaration for a virtual machine omits the 'location' property, what will happen during deployment?

A Deployment fails with an error indicating the missing 'location' property

B Azure assigns a default location automatically

C Deployment succeeds but the VM is created in an undefined location

D Deployment is queued until the location is specified manually

💡 Hint

Consider required properties for Azure resources in ARM templates.

The 'location' property is required for most Azure resources. Omitting it causes deployment to fail with an error.