Question 1080
Following the issue — A Defender plan sends duplicate alerts after re-onboarding a server through two management paths. — the team takes this action: Inspect device and resource identity mapping and remove unintended duplicate onboarding. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Reconcile server identity records during Azure Arc and VM migrations. This mitigates the control weakness because: Overlapping management identities can fragment security evidence for the same workload. Keep the intervention, Inspect device and resource identity mapping and remove unintended duplicate onboarding., in the approved deployment, monitoring and change governance process.
Incorrect Answers
“Version-control benchmarking sources used in executive dashboards” addresses a different recurring failure: Comparability depends on stable benchmark definitions and resource coverage. For the condition in this question, maintain “Reconcile server identity records during Azure Arc and VM migrations” because overlapping management identities can fragment security evidence for the same workload.
That review protects the control associated with: Policy conditions need accurate resource property selectors to match the intended type and configuration. It does not directly prevent the stated recurrence, which concerns: Overlapping management identities can fragment security evidence for the same workload. The appropriate guardrail is “Reconcile server identity records during Azure Arc and VM migrations”.
This safeguard is for the dependency described by: Automated response needs data minimization and role-based security alongside workflow correctness. The continuing risk here is determined by: Overlapping management identities can fragment security evidence for the same workload. The targeted safeguard is “Reconcile server identity records during Azure Arc and VM migrations”.