You have a file server named Server1 that runs Windows Server 2012.
Server1 has following hardware configurations:
16 GB of RAM
A single quad-core CPU
Three network teams that have two network adapters each
You add additional CPUs and RAM to Server1.
You repurpose Server1 as a virtualization host.
You install the Hyper-V server role on Server1.
You need to create four external virtual switches in Hyper-V.
Which cmdlet should you run first?

A.
Add-VMNetworkAdapter

B.
Add-NetLbfoTeamNic

C.
Set-NetAdapter

D.
Remove-NetLbfoTeam

Explanation:
Here we’re talking about hardware network adapters which belong to NIC teams
Each externalvirtual switch must be connected to a NIC or a NIC team, so we need 4 NICs or NIC teams
but currently only have 3 teams available.
=> we need to break a team first and then connect the two last external virtual switches to each of the 2
“liberated” NIC
(an other solution could be to add one physical NICand connect the last external virtual switch to it.
or add several (two or more) NICs, create a NIC team containing them and connect the external virtual switch
to the NIC team)
==============
http://technet.microsoft.com/en-us/library/jj130848.aspx
NIC Teaming (NetLBFO) Cmdlets in Windows PowerShell
Remove-NetLbfoTeam : Removes the specified NIC teamfrom the host.
=================
http://technet.microsoft.com/en-us/library/hh831648.aspx
NIC Teaming Overview
NIC Teaming, also known as load balancing and failover (LBFO), allows multiple network adapters on a
computer to be placed into a teamfor the following purposes:
Bandwidth aggregation
Traffic failover to prevent connectivity loss in the event of a network component failure
This feature has been a requirement for independenthardware vendors (IHVs) to enter the server network
adapter market, but until now NIC Teaming has not been included in Windows Server operating systems.
Requirements
NIC Teaming requires the presence of a single Ethernet network adapter, which can be used for separating
traffic that is using VLANs. All modes that providefault protection through failover require at leasttwo Ethernet
network adapters. Windows Server 2012 supports up to 32 network adapters in a team.
==============