Which two actions take place when an active NSX Edge instance fails? (Choose two.)
A.
Once the original NSX Edge instance is recovered, it preempts the other NSX Edge instance
and takes over the active role.
B.
The standby NSX Edge instance becomes the active instance and requests routing updates
from the routing neighbors.
C.
Once the original NSX Edge instance is recovered, the NSX Manager attempts to place it on a
different host from the other NSX Edge instance.
D.
The standby NSX Edge instance becomes the active instance and retains any routing neighbor
adjacencies.
C is not true, NSX Manager is not responsible for the location of the ESGs VMs,if your cluster has DRS enabled anti-affinity rules are created automatically to separate these VMs, but the NSX doesn’t move VMs to anywhere.
A is not true neither, the role is NOT preemptive
B is incorrect because the stand-by node already has the routing information, is the “same” peer/neighbour that the failed active node.
If this question became on the exam I’ll comment it and answer what here said
From: https://pubs.vmware.com/NSX-6/topic/com.vmware.nsx.admin.doc/GUID-6C4F0C33-C6DD-432B-AA91-10AD6B449125.html
NSX Edge ensures that the two HA NSX Edge virtual machines are not on the same ESX host even after you use DRS and vMotion.
Maybe we’re splitting hairs here, but if NSX puts in the anti-affinity rule, then NSX is ensuring that the VMs are not on the same host.
In this case, it appears C and D would be correct.
That should be right, splitting hairs, maybe 🙂
Technically per the Admin Doc, its the Edge that ensures that they are not on the same host, not the manager but either way they are saying that NSX is responsible for that not necessarily anti-affinity rules especially when you may be running on a Hypervisor that doesn’t support those rules.
https://pubs.vmware.com/NSX-6/topic/com.vmware.nsx.admin.doc/GUID-6C4F0C33-C6DD-432B-AA91-10AD6B449125.html
“NSX Edge ensures that the two HA NSX Edge virtual machines are not on the same ESX host even after you use DRS and vMotion (unless you manually vMotion them to the same host).”