Design identity, governance, and monitoring solutions →hardMultiple Choice

AZ-305 Practice Question: Design identity, governance, and monitoring solutions

Exhibit

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "location": {
      "type": "string",
      "defaultValue": "[resourceGroup().location]"
    }
  },
  "variables": {},
  "resources": [
    {
      "type": "Microsoft.Storage/storageAccounts",
      "apiVersion": "2021-02-01",
      "name": "[parameters('storageName')]",
      "location": "[parameters('location')]",
      "kind": "StorageV2",
      "sku": {
        "name": "Standard_LRS"
      },
      "properties": {
        "supportsHttpsTrafficOnly": true,
        "minimumTlsVersion": "TLS1_2"
      }
    }
  ],
  "outputs": {}
}

Refer to the exhibit. You are reviewing an ARM template for deploying a storage account. The template is missing the storage account name parameter definition. What will happen when you attempt to deploy this template?

⚠ Common exam trap

Many candidates assume Azure will automatically prompt for or generate a missing parameter, similar to how some Azure Portal experiences handle missing inputs, but ARM templates strictly enforce parameter definitions and fail fast on validation.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The deployment will fail with a validation error because the parameter is not defined.

In Azure Resource Manager (ARM) templates, all parameters must be explicitly defined in the `parameters` section of the template. If a parameter is referenced (e.g., in the `resources` section) but not defined, the deployment fails with a validation error before any resource provisioning begins. This is because ARM validates the template structure and parameter definitions during the pre-deployment validation phase, and an undefined parameter is considered a syntax error.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The deployment will prompt the user to provide the missing parameter.
Why it's wrong here
Azure Resource Manager deployments are fully declarative and non-interactive: the deployment engine does not pause to ask the user for values. A missing parameter can only be supplied via the command line, a parameter file, or a default value, and if none exists, template validation fails immediately rather than prompting.
✓
The deployment will fail with a validation error because the parameter is not defined.
Why this is correct
During the pre-deployment validation phase, Azure Resource Manager parses the template and evaluates all expressions that reference parameters. If a parameter is used in the resources section but is not declared in the parameters section—or has no default and is not provided—the template is considered malformed and the validation error rejection happens before any resource group changes are attempted.
✗
The deployment will succeed using a default name based on the resource group.
Why it's wrong here
ARM templates never synthesize a storage account name from the resource group name. Storage account names must be 3-24 characters, lowercase, alphanumeric only, and globally unique, so using the resource group name would violate those constraints; consequently, an undeclared parameter simply results in validation failure, not a derived default.
✗
The deployment will create a storage account with a random name.
Why it's wrong here
Random name generation occurs only when a template explicitly calls functions like uniqueString() or newGuid() to construct a name. Since the missing parameter is referenced directly with no function invocation and no declared source, the template fails validation and no storage account is created—randomness never enters the process.

Go deeper

AZ-305 Practice Question: Design identity, governance, and monitoring solutions

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question