You will deploy identical Azure VMs via Resource Manager templates, where each deployment’s administrator password is stored as a secret in a different Key Vault. The Key Vault name and secret name will be provided as inline parameters. Which method lets you dynamically construct the resource ID that identifies the appropriate Key Vault during each deployment?

A linked template allows you to break down your Azure Resource Manager (ARM) template into smaller, reusable components. This is crucial here because you need to dynamically reference different Key Vaults and secrets for each VM deployment. The main template can call a linked template, passing the Key Vault name and secret name as parameters. The linked template can then construct the resource ID for the Key Vault secret using functions like resourceId() and concat(), ensuring the correct secret is retrieved for each specific VM. A key vault access policy defines who can access secrets within a Key Vault, not how to dynamically reference it in a template. A parameters file provides static input values for a template but doesn't offer the dynamic logic needed to construct resource IDs based on varying Key Vaults. An automation account is used for managing and automating Azure tasks, not for dynamically constructing resource IDs within an ARM template deployment.