A network failure of a host occurred in a VMware vSphere Foundation (VVF) vSphere cluster. None of the virtual machines (VMs) restarted on unaffected hosts and the VMs were unreachable until the…

Question

Options

• AHost Isolation Response is disabled in vSphere HA.
• BThe VMs have "should run on" host affinity rule applied.
• CvSphere DRS has not been enabled on the cluster.
• DvSphere HA has not been enabled on the cluster.

• A
  48% (15)
• B
  29% (9)
• C
  6% (2)
• D
  16% (5)

Explanation

Option A is correct because a network failure causes the host to become isolated from the cluster - the host and its VMs are still running, but unreachable. vSphere HA's Host Isolation Response specifically governs what happens in this scenario; when it is disabled, HA takes no action (VMs remain stranded on the isolated host rather than being restarted elsewhere). The successful power-off tests confirm HA itself works for true host failures, but isolation is a separate trigger entirely.

B is wrong because a "should run on" DRS affinity rule is a soft recommendation that influences placement but does not block HA from restarting VMs on other hosts during a failure event. C is wrong because the question explicitly states DRS is enabled, and DRS governs load balancing/migration - not HA restart behavior anyway. D is wrong because the question explicitly states HA is enabled, and the power-off tests passed, proving HA detects and responds to actual host failures correctly.

Memory tip: Think of two distinct HA triggers - "host dead" (heartbeat loss from a powered-off/crashed host) and "host isolated" (host is alive but network-partitioned). Host Isolation Response is the second switch; if it's off, isolated VMs just sit there unreachable. The clue in the question is network failure, not host failure - that word swap is the exam trap.

No community discussion yet for this question.