ARM template parameters and variables in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding ARM Template Parameters

In an ARM template, what is the main purpose of parameters?

A To define the output values after deployment

B To store fixed values that never change in the template

C To execute scripts during deployment

D To define values that can be provided during deployment to customize resources

💡 Hint

Think about what you want to change each time you deploy the template.

Parameters allow you to pass different values when deploying the template, making it reusable and flexible.

❓ Configuration

intermediate

Variable Usage in ARM Templates

Which option correctly defines a variable named storageAccountName that concatenates 'stor' with a parameter uniqueString?

A "variables": { "storageAccountName": "[concat('stor', parameters('uniqueString'))]" }

B "variables": { "storageAccountName": "[concat('stor', uniqueString)]" }

C "variables": { "storageAccountName": "[concat('stor', parameters['uniqueString'])]" }

D "variables": { "storageAccountName": "[concat('stor', parameters.uniqueString)]" }

💡 Hint

Remember the correct syntax to reference parameters inside variables uses parameters('name') or parameters['name'].

Option C uses the correct syntax to access a parameter inside a variable definition in ARM templates.

❓ Architecture

advanced

Parameter and Variable Scope in Nested ARM Templates

You have a main ARM template that calls a nested template. Which statement is true about passing parameters and using variables in the nested template?

A Parameters must be explicitly passed from the main template to the nested template; variables are local to each template.

B Variables defined in the main template are automatically available in the nested template.

C Parameters and variables are shared globally across all nested templates without passing.

D Variables can be passed to nested templates but parameters cannot.

💡 Hint

Think about how data flows between templates during deployment.

Parameters must be passed explicitly to nested templates. Variables are local and cannot be shared directly.

❓ security

advanced

Secure Parameter Usage in ARM Templates

Which parameter type should you use in an ARM template to securely accept a password without exposing it in deployment logs?

A "type": "string"

B "type": "secureString"

C "type": "password"

D "type": "secureObject"

💡 Hint

Consider how ARM templates handle sensitive data.

The secureString type encrypts the value and prevents it from appearing in logs.

❓ service_behavior

expert

Output Value Behavior with Variables in ARM Templates

Given this ARM template snippet, what will be the value of the output finalName after deployment?

{
  "parameters": {
    "prefix": { "type": "string", "defaultValue": "app" }
  },
  "variables": {
    "name": "[concat(parameters('prefix'), 'svc')]"
  },
  "outputs": {
    "finalName": {
      "type": "string",
      "value": "[variables('name')]"
    }
  }
}

A appsvc

B ${parameters('prefix')}svc

C [parameters('prefix')]svc

D svc

💡 Hint

Variables can use functions to combine parameter values.

The variable name concatenates the parameter prefix value 'app' with 'svc', resulting in 'appsvc'.