Question 330
An application rotates its database secret but several services still use the retired value. What is the most appropriate architectural change?
Explanation
Correct Answer
The security outcome calls for centralize secret storage and implement version-aware rotation with consumer validation. Credential rotation must coordinate dependent consumers to prevent outages. The measurable confirmation is that all authorized workloads use the active secret and the revoked version fails.
Incorrect Answers
That recommendation concerns A security requirement mandates customer-controlled encryption keys for sensitive platform data. Key ownership and lifecycle controls are separate from data-at-rest encryption defaults. Here the required proof is that all authorized workloads use the active secret and the revoked version fails.
The alternative focuses on A recovery plan assumes secrets remain readable after the only Key Vault region is unavailable. A cryptographic service dependency can block application recovery. It is not the direct response needed to demonstrate all authorized workloads use the active secret and the revoked version fails.
It addresses a neighboring control requirement, not this one: A certificate renewal fails because no application owner monitors its expiration date. Certificate lifecycle management requires monitoring as well as initial deployment. The present scenario specifically needs all authorized workloads use the active secret and the revoked version fails.