Question 960
Following the issue — A Defender for Cloud recommendation remains open after remediation because the evaluation has not refreshed. — the team takes this action: Validate the actual resource configuration and the supported assessment refresh state before repeating changes. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Distinguish assessment latency from continuing configuration failure in ticket workflows. This mitigates the control weakness because: Posture recommendation status can lag behind recently changed resources. Keep the intervention, Validate the actual resource configuration and the supported assessment refresh state before repeating changes., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Security orchestration should apply proportional controls with auditability and human approval for high-impact actions. The continuing risk here is determined by: Posture recommendation status can lag behind recently changed resources. The targeted safeguard is “Distinguish assessment latency from continuing configuration failure in ticket workflows”.
“Record the chosen Key Vault permission model before operational access changes” addresses a different recurring failure: Vault RBAC mode and legacy vault access-policy mode represent different authorization paths. For the condition in this question, maintain “Distinguish assessment latency from continuing configuration failure in ticket workflows” because posture recommendation status can lag behind recently changed resources.
This safeguard is for the dependency described by: Multicloud security plan capabilities can differ by provider, workload and integration method. The continuing risk here is determined by: Posture recommendation status can lag behind recently changed resources. The targeted safeguard is “Distinguish assessment latency from continuing configuration failure in ticket workflows”.