A microservice architecture uses 20 different secrets. Which Key Vault design approach reduces operational overhead?
- A One Key Vault per microservice (20 vaults)
- B One shared vault for all microservices with RBAC controlling access per service
- C One vault per environment (dev/staging/prod) (correct answer)
- D Store secrets in Azure Table Storage with encryption
Shortcut: One vault per environment (dev, staging, prod) balances operational simplicity with security isolation. RBAC within each vault controls which services/identities access which secrets. One per microservice creates excessive management overhead.