You have a server named Server1 that runs Windows Server 2016. Server1 is a Hyper-V host that hosts a virtual machine named VM1.
Server1 has three network adapter cards that are connected to virtual switches named vSwitch1, vSwitch2 and vSwitch3.
You configure NIC Teaming on VM1 as shown in the exhibit. (Click the Exhibit button.)
You need to ensure that VM1 will retain access to the network if a physical network adapter card fails on Server1.
What should you do?
A. From the properties of the NIC team on VM1, change the load balancing of the NIC team.
B. From Hyper-V Manager on Server1, modify the settings of VM1.
C. From Windows PowerShell on Server1, run the Set-VmNetworkAdapterFailoverConfiguration cmdlet.
D. From Hyper-V Manager on Server1, modify the properties of vSwitch1.
Answer is correct
VM Setting, Network Adapter, Advanced Feature, NIC Teaming , then Enable the checkbox
Note that,
When this option is cleared, a team created in OS will lose connectivity if one of the physical network adapters stops working
A — In this scenario, you have improperly configured NIC Teaming on VM1. So even if you did perform (B) Modify the settings of VM1 to Enable NIC Teaming, it would fail due to the requirement for Load Balancing to be set to Address Hash. According to Microsoft, “If you are configuring a NIC Team in a VM, you must select a Teaming mode of Switch Independent and a Load balancing mode of Address Hash.”
https://docs.microsoft.com/en-us/windows-server/networking/technologies/nic-teaming/create-a-new-nic-team-on-a-host-computer-or-vm