Question 310
A new Azure Storage account must use a customer-managed encryption key held in Azure Key Vault. The storage account managed identity already has the required key permissions, and the vault has soft delete enabled, but purge protection is currently disabled. What additional vault setting is required?
Explanation
Correct Answer
Azure Storage customer-managed keys in Key Vault require both soft delete and purge protection so the key cannot be permanently purged while storage remains dependent on it. Soft delete is already enabled in the scenario, making purge protection the missing prerequisite.
Incorrect Answers
User-delegation SAS tokens authorize Blob requests; they neither protect Key Vault keys from permanent deletion nor meet Azure Storage customer-managed encryption prerequisites. Issuing them per container does not enable vault purge protection.
Disabling soft delete does not meet the documented configuration requirement and would weaken key recovery protections. Soft delete is required for supported Key Vault-backed storage customer-managed encryption, not a feature to turn off.
Azure Storage account access keys authenticate shared-key requests; they are unrelated to the Key Vault encryption key used for customer-managed server-side encryption. Regenerating them cannot enable Key Vault purge protection.