Question 800
The cloud operations team reviews the following risk: A production application silently continues using a legacy connection secret near its expiration date because nobody owns renewal procedures. Which result confirms the relevant security control is effective?
Explanation
Correct Answer
This validates the specific control for key vault secret expiry lifecycle: Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. The associated corrective action is: Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications. Testing a different component would not establish this result.
Incorrect Answers
Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers” would address that alternative cause, not the condition in this question: secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.
“Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” responds to this separate finding: an immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. This question instead needs “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications”, so the alternative does not meet the stated condition.
Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope” applies to that separate problem. The observed case is a production application silently continues using a legacy connection secret near its expiration date because nobody owns renewal procedures; choosing this alternative would address the wrong failure mode.