You have a Hyper-V host named Server1 that runs Windows Server 2012 R2.Server1 has the virtual
switches listed in the following table.
You create a virtual machine named VM1.VM1 has two network adapters. One network adapter
connects to vSwitch1. The other network adapter connects to vSwitch2.You configure NIC teaming
on VM1.
You need to ensure that if a physical NIC fails on Server1, VM1 remains connected to the network.
What should you do on Server1?
A.
Run the Set-VmNetworkAdaptercmdlet.
B.
Add a new network adapter to VM1.
C.
Create a new virtual switch on Server 1.
D.
Modify the properties of vSwitch1 and vSwitch2.
When nic teaming is set on the Guest (VM1)
you still need to enable the Nic Teaming on the Host that is server1
(under Network Adapter Advanced Features)
please note if it is not set a team created in the guest operating system will
lose connectivity if one of the Physical networks adapters stops working
or the PowerShell command
Set-VmNetworkAdapter
Set-VmNetworkAdapter deals with the VM networking and not the host networking.
@Jan you appear to be correct.
http://www.serverwatch.com/server-tutorials/configuring-nic-teaming-for-virtual-machines-with-hyper-v-3.0.html
answer is A
Example 5
This example configures NIC Teaming for all virtual network adapters of the virtual machine named Redmond.
Windows PowerShell
PS C:\> Get-VM Redmond | Set-VMNetworkAdapter –AllowTeaming On
https://technet.microsoft.com/en-us/library/hh848457.aspx
and
https://mountainss.wordpress.com/2012/08/04/technical-overview-windows-server-2012-nic-teaming-ws2012-hyperv/