An administrator determines that a virtual machine configured for the Development port group lost network
connectivity when it was migrated with vMotion from one ESXi 5.x host to another. The administrator notices
that machines configured for the Production port group are not experiencing the issue. The hosts have port
groups with the following network configuration:
Host A:
Production (VLAN 100)
Development
Host B:
Production (VLAN 100)
Development (VLAN 200)
Which two conditions would explain the loss of network connectivity for the virtual machine? (Choose two.)
A.
The configured VLAN for Production on Host A is incorrect.
B.
The configured VLAN for Development on Host B is incorrect.
C.
An improper native VLAN is configured on the uplinks to Host A.
D.
An improper native VLAN is configured on the uplinks to Host B.
Can anybody explain that question please?
0
0
Ok, explanation.
in order to successfully migrate a vm using vmotion you must have identical network setup on both hosts.
here we have only one vlan WHICH IS THE SAME ON BOTH HOSTS ehich is the Production (VLAN 100).
Now the develpoment VLAN is the problem as on one host it is confihured and on the other one it is not!
since you can’t guess what is the correct setup for the development (with VLAN 200 or WITHOUT) THE ANSWER must be B and C is because untagged VLANs are usually taken as native VLANS and it means that the native on the A switch is not set properly
0
0
I think B and D are correct
VM was working fine in Host A and lost connectivity after vMotion to Host B. So physical switch connected to Host B uplink may be have not configured to allow native vlan.
0
0
I don’t think the scenario ever stated which host it was migrated from. So we don’t know which configuration was working. So I think best answer is B,C.
0
0
The wording in answer C is weird. VALNs aren’t configured on uplinks, they may be configured on the physical switch that connect to the physical NICs that are assigned to the uplinks. Another weird wording from VMWare!
0
0