AZ-104 · Question #94
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Option B (No) is correct because enabling Update Management only configures patch and update orchestration for the VM's operating system - it has no capability to migrate a VM to a different physical host. Why the distractor (A/Yes) is wrong: Update Management is a patching…
Question
Options
- AYes
- BNo
How the community answered
(47 responses)- A13% (6)
- B87% (41)
Explanation
Option B (No) is correct because enabling Update Management only configures patch and update orchestration for the VM's operating system - it has no capability to migrate a VM to a different physical host.
Why the distractor (A/Yes) is wrong: Update Management is a patching service; it schedules and deploys OS updates (Windows/Linux), not infrastructure-level operations. Clicking "enable" there simply onboards the VM to patch management, leaving its physical host completely unchanged.
What you should do instead: To immediately move a VM to a different host in response to a maintenance notification, use the Redeploy option found in the VM blade under Support + troubleshooting → Redeploy. This shuts down the VM and restarts it on a new Azure host node right away. Alternatively, if the VM is in an Availability Set, Planned Maintenance events support self-service migration via the Azure portal.
Memory tip: Associate Update Management with software updates (patches), and Redeploy with hardware/host changes. Anytime a question says "move to a different host immediately," think Redeploy - not any update or management blade.
Topics
Community Discussion
No community discussion yet for this question.