Which two conditions explain this behavior?

A host failure occurs in vSphere HA cluster, but virtual machines from the failed host are not restarted on the surviving nodes in the cluster.

Which two conditions explain this behavior? (Choose two)

Ha has been configured to use a dedicated failure host, and the failed host is designated failover host.

An anti-affinity rule configured and restarting the VMs would place them on the same host.

The virtual machines on the failed host are HA disabled.

Hot Monitoring is disabled.

7 Comments on “Which two conditions explain this behavior?

  1. Ryan M says:

    D should be host monitoring.

    B makes no sense – if a single host is down and it’s VM’s don’t start up due to anti-affinity rules, they wouldn’t have all been on the same host that failed in the first place.

  2. bue says:

    I tested this case in lab, B & C are correct, even if you have disabled host monitoring you can enable VM monitoring and VM will be restarted.
    When I set rule for VM to run on specific host and when this host went down VM didn’t started up.

  3. David says:

    A WRONG, no VM should be placed on a designated failover host
    B WRONG, anti-affinity is a DRS rules, the question is about an HA cluster, not HA/DRS cluster
    C CORRECT, VM can override cluster setting for HA (and DRS)
    D CORRECT, Host Monitoring needs to be enabled for the HA to vMotion VMs

Leave a Reply

Your email address will not be published. Required fields are marked *