Brightwater Logistics stores an ARM template in a repository. The template contains the following fragments: "parameters": { "environment": { "type": "string", "allowedValues": [ "dev", "prod" ] } }, "variables": { "storageName": "[concat('bwl', parameters('environment'), uniqueString(resourceGroup().id))]" }, "resources": [ { "type": "Microsoft.Storage/storageAccounts", "apiVersion": "2023-01-01", "name": "[variables('storageName')]", "location": "[resourceGroup().location]", "sku": { "name": "Standard_LRS" }, "kind": "StorageV2" } ] A junior administrator asks how the storage account name is determined when the template is deployed to a resource group named rg-bwl-dev.
How is the storage account name produced?
- AThe deployer is prompted for a value for storageName at deployment time.
- BThe template concatenates the literal prefix bwl, the environment parameter value, and a hash derived from the resource group ID.
- CThe name is taken from the resource group name rg-bwl-dev with the hyphens removed.
- DThe name is randomly generated at each deployment, so repeated deployments create new storage accounts.