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)

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)

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

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

C.
The virtual machines on the failed host are HA disabled.

D.
Hot Monitoring is disabled

Explanation:
Prior: B and D After: C and D Because B makes no sense H/A does not account for DRS rules.
You can disable HA at the VM level.



Leave a Reply 5

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


TJ

TJ

are A & B not the correct answer ?
is HA not enabled/disabled on cluster level ???

networkmanagers

networkmanagers

Explanation:
Prior: B and D After: C and D Because B makes no sense H/A does not account for DRS rules.
You can disable HA at the VM level.

Gary

Gary

A is not the answer because if you use a dedicated host, no VMs can run on that.

foreignbishop

foreignbishop

Question mentions nothing about DRS. Therefore, we are only dealing with an HA licensed cluster (theoretically). Affinity and Anti-Afinity rules are only applicable to DRS enabled clusters for VM’s. (Not including affinity with regards to storage groups). B cannot be a correct answer.

HE

HE

correct answer but it shoud be host and not hot 🙂