Broadcom-VMware
2V0-620 · Question #144
2V0-620 Question #144: Real Exam Question with Answer & Explanation
The correct answer is A: The Orphaned virtual machines have HA restart disabled.. Virtual machines with HA restart priority set to Disabled are intentionally excluded from HA restart actions during a host reboot, and can appear orphaned when the host reconnects because no agent preserved or re-registered their running state.
Section 5 – Administer and Maintain vSphere
Question
Why are some virtual machines orphaned after rebooting a High Availability (HA) enabled host?
Options
- AThe Orphaned virtual machines have HA restart disabled.
- BThe Orphaned virtual machines moved recently and the change did not persist.
- CThe host is attached to failed storage.
- DThe host just came out of maintenance mode.
Explanation
Virtual machines with HA restart priority set to Disabled are intentionally excluded from HA restart actions during a host reboot, and can appear orphaned when the host reconnects because no agent preserved or re-registered their running state.
Common mistakes.
- B. A recent vMotion that did not persist would leave a registration inconsistency on a specific host, but this scenario is unrelated to the HA reboot event that triggers the orphan state.
- C. Failed storage would make VM disk files inaccessible and could cause VMs to fail, but this would affect all VMs using that storage - not selectively the subset that becomes orphaned after a host reboot.
- D. A host exiting maintenance mode causes DRS to potentially rebalance workloads across the cluster, but this process does not result in virtual machines becoming orphaned.
Concept tested. vSphere HA restart priority Disabled and VM orphan state
Topics
#High Availability#orphaned VMs#HA restart priority#host reboot
Community Discussion
No community discussion yet for this question.