Question 880
Following the issue — An Azure Policy assignment appears compliant despite a newly added subscription not being in the intended management group. — the team takes this action: Correct management group membership or assign required policy at the appropriate target scope. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Check policy coverage whenever subscriptions are moved between management groups. This mitigates the control weakness because: Policy inheritance follows Azure scope hierarchy and does not cover subscriptions outside that hierarchy. Keep the intervention, Correct management group membership or assign required policy at the appropriate target scope., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Include external service discovery in development environment shutdown processes” addresses a different recurring failure: Unknown exposed services can bypass standard production security lifecycle controls. For the condition in this question, maintain “Check policy coverage whenever subscriptions are moved between management groups” because policy inheritance follows Azure scope hierarchy and does not cover subscriptions outside that hierarchy.
That review protects the control associated with: Automated compliance mappings indicate control posture rather than a complete legal determination. It does not directly prevent the stated recurrence, which concerns: Policy inheritance follows Azure scope hierarchy and does not cover subscriptions outside that hierarchy. The appropriate guardrail is “Check policy coverage whenever subscriptions are moved between management groups”.
“Map monitoring data sources to actual detection and response requirements” addresses a different recurring failure: Performance measures and security events describe different aspects of a system's behavior. For the condition in this question, maintain “Check policy coverage whenever subscriptions are moved between management groups” because policy inheritance follows Azure scope hierarchy and does not cover subscriptions outside that hierarchy.