You have a file server named Server1 that runs Windows Server 2012 R2. 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-NetLbfoTeamNic

B.
Set-NetAdapter

C.
Remove- NetLbfoTeam

D.
Add-VMNetworkAdapter

Explanation:
Here we’re talking about hardware network adapters which belong to NIC teams Each external virtual
switchmust be connected to a NIC or a NIC team, so we need 4 NICs or NIC teamsbut currently only have 3
teamsavailable.
=>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 NIC and connect the last external virtual
switchto it or add several (two or more) NICs, create a NIC team containing them and connect the external
virtualswitch 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 team from the host. http://technet.microsoft.com/en-us/
library/hh831648.aspx NIC Teaming Overview
NIC Teaming, also known as load balancing and failover (LBFO), allowsmultiple network adapters on
acomputer to be placed into a team for 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 independent hardware vendors (IHVs) to enter the server
networkadapter 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 networkadapter, which can be used
forseparating traffic that is using VLANs. All modes that provide fault protection through failover require at
leasttwo Ethernet network adapters. Windows Server?2012 supports up to 32 network adapters in a team.