Bitzu

AZ-305 ยท Authorization, secrets and keys

Key Vault design: boundaries, permissions and protection

Secrets, keys and certificates in Azure Key Vault, RBAC vs access policy permission model, soft delete and purge protection, private access, one vault per app per environment.

Key points

  • Azure Key Vault: secrets, keys, certificates. One vault per application, environment and region.
  • Azure RBAC model (default) over legacy access policies.
  • Key Vault Secrets User: data; Key Vault Contributor: control plane only.
  • Soft delete: on by default, 7-90 days (default 90).
  • Purge protection: optional, cannot be turned off.
  • Exposure: private endpoints, public access disabled, managed identities.

Source: https://learn.microsoft.com/en-us/azure/key-vault/general/secure-key-vault

Practice questions

Single choice

What retention period can you configure for soft-deleted objects in Azure Key Vault?

  1. 1 to 30 days, default 14
  2. 7 to 90 days, default 90
  3. 30 to 365 days, default 90
  4. 7 to 30 days, default 30
Show answer

Answer: B. 7 to 90 days, default 90

Soft-delete retention is set at vault creation to any value from 7 to 90 days, with 90 days as the default, and it cannot be changed afterwards. The same interval applies to purge protection.

Select all that apply

Which practices should a Key Vault design follow?

  1. Create separate vaults for each application and environment
  2. Disable public network access and connect through private endpoints
  3. Enable purge protection on vaults that hold encryption keys
  4. Store application configuration and customer records in the vault
  5. Assign roles on individual secrets as the default approach
Show answer

Answer: A. Create separate vaults for each application and environment, B. Disable public network access and connect through private endpoints, C. Enable purge protection on vaults that hold encryption keys

Separate vaults per application and environment limit the blast radius, private endpoints with public access disabled cut network exposure, and purge protection stops a deleted vault or key from being destroyed before retention ends. Key Vault is not a data store for customer content or configuration, and per-secret role assignments are only for a few exceptional cases.

True or false

If a team later needs to purge a vault immediately, it can turn purge protection off again.

Show answer

Answer: False

False. Enabling purge protection is irreversible. While it is on, a deleted vault or object cannot be purged until the retention period ends, although it can still be recovered.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module