A VM-Host affinity rule states that VM group “X” must run on hosts in group “Y”.
If all ESXi hosts in group “Y” fail, which is the resulting behavior with vSphere HA enabled?
A.
The virtual machines in group “X” will failover to hosts that do not belong to group “Y”, but will vMotion back
to hosts in group “Y” when they become available.
B.
The virtual machines in group “X” will not failover to hosts that do not belong to group “Y”.
C.
This scenario is not possible because vSphere HA and DRS cannot work together.
D.
The virtual machines in group “X” will only fail over to hosts that do not belong to group “Y” if they are
marked as “High” VM Restart Priority within vSphere HA.
B
Correct: B
If you are using VM-Host affinity rules that are required, be aware that these rules cannot be violated. vSphere HA does not perform a failover if doing so would violate such a rule.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-1D8B1384-59A4-41E2-AF05-697FC06D9EF9.html
Restart Priority can override the default cluster settings.
Reference > https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.avail.doc/GUID-FA8B166D-A5F5-47D3-840E-68996507A95B.html
After you create a vSphere HA cluster, you can override the default cluster settings for Restart Priority and Isolation Response for specific virtual machines. Such overrides are useful for virtual machines that are used for special tasks. For example, virtual machines that provide infrastructure services like DNS or DHCP might need to be powered on before other virtual machines in the cluster.
I would agree with kan on B. I don’t think Restart Priority can override VM-Host affinity rules — infojami.