Vanguard Systems manages an Azure subscription named sub-vanguard-secure. An administrator deploys a storage account named savanguarddata and an Azure Key Vault named kv-vanguard-secrets with the following configurations:
savanguarddata:
- Identity: Configured with a User-Assigned Managed Identity named uami-encrypt.
- Firewall: Enabled, with 'Allow trusted Microsoft services to access this storage account' set to Yes.
kv-vanguard-secrets:
- Properties: Soft-delete is Enabled; Purge protection is Enabled.
- Permission model: Azure role-based access control (Azure RBAC).
- Firewall: Enabled from selected networks, with 'Allow trusted Microsoft services to bypass this firewall' set to No.
The administrator assigns the Key Vault Crypto Service User role to uami-encrypt at the key vault scope.
When attempting to enable customer-managed keys (CMK) on savanguarddata using a key from kv-vanguard-secrets, the configuration fails. What is the cause of the configuration failure?
- The Key Vault firewall blocks the Azure Storage service because the bypass for trusted Microsoft services is disabled on kv-vanguard-secrets.Cevap
- BThe User-Assigned Managed Identity (uami-encrypt) requires the Owner or Contributor role assigned on the kv-vanguard-secrets control plane.
- CThe storage account firewall is blocking incoming connections because the 'Allow trusted Microsoft services' bypass is enabled on savanguarddata but disabled on the Key Vault.
- DAzure Key Vault is configured with Azure RBAC, which requires the storage account's system-assigned managed identity to be granted the Key Vault Administrator role.