Design infrastructure solutions →hardMultiple Choice

AZ-305 Design infrastructure solutions Practice Question

Exhibit

{
  "parameters": { "vmName": { "value": "prod-vm-001" } },
  "resources": [
    {
      "type": "Microsoft.Compute/virtualMachines",
      "apiVersion": "2023-03-01",
      "name": "[parameters('vmName')]",
      "location": "[resourceGroup().location]",
      "properties": {
        "hardwareProfile": { "vmSize": "Standard_D2s_v3" },
        "storageProfile": {
          "osDisk": { "createOption": "fromImage", "managedDisk": { "storageAccountType": "Premium_LRS" } },
          "dataDisks": [
            { "createOption": "empty", "diskSizeGB": 1023, "lun": 0, "managedDisk": { "storageAccountType": "StandardSSD_LRS" } }
          ]
        },
        "osProfile": {
          "computerName": "[parameters('vmName')]",
          "adminUsername": "azureuser",
          "adminPassword": "Password123!"
        },
        "networkProfile": {
          "networkInterfaces": [
            { "id": "[resourceId('Microsoft.Network/networkInterfaces', concat(parameters('vmName'), '-nic'))]" }
          ]
        }
      }
    }
  ]
}

Refer to the exhibit. The ARM template provisions a VM. The deployment succeeds but the VM fails to start. What is the most likely cause?

⚠ Common exam trap

It's easy for candidates to assume any deployment success means all configuration is valid, but Azure separates infrastructure provisioning from guest OS configuration, so password or other guest-level failures can occur after deployment succeeds.

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 VM size Standard_D2s_v3 is not available in the region

The VM size Standard_D2s_v3 may not be available in the specified region or subscription. ARM template deployments can succeed in provisioning the resource definition, but the VM fails to start if the scheduler cannot allocate a host that supports this VM size. This is a common issue when the size is restricted or not available in the region, causing a delayed failure after deployment.

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 admin password is in plaintext and does not meet complexity requirements
Why it's wrong here
In Azure, if the admin password does not meet complexity requirements, the deployment fails immediately with a validation error, so this cannot be the cause when the deployment succeeds.
✗
The data disk size 1023 GB exceeds the maximum for StandardSSD_LRS
Why it's wrong here
StandardSSD_LRS managed disks support up to 4095 GB (4 TB), so 1023 GB is well within the limit.
✗
The network interface resource ID is incorrectly formatted
Why it's wrong here
If the network interface resource ID is incorrectly formatted, the deployment would fail because it cannot reference a valid resource. Since the deployment succeeds, this is not the cause.
✓
The VM size Standard_D2s_v3 is not available in the region
Why this is correct
Correct. As explained, the VM size not being available in the region can lead to a successful deployment but the VM failing to start.

Go deeper

AZ-305 Design infrastructure solutions Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question