You work as a senior administrator at Contoso.com. The Contoso.com network consists of a single
domain named Contoso.com. All servers on the Contoso.com network have Windows Server 2012
installed.

You are running a training exercise for junior administrators. You are currently discussing NIC
Teaming.
Which of the following is TRUE with regards to NIC Teaming? (Choose all that apply.)

A.
It allows for traffic failover to prevent connectivity loss if a network component fails.

B.
It prevents bandwidth aggregation.

C.
The Windows Server 2012 implementation of NIC Teaming supports a maximum of 5 NICs in a
team.

D.
The Windows Server 2012 implementation of NIC Teaming supports a maximum of 32 NICs in a
team.

Explanation:
NIC teaming, also known as Load Balancing/Failover (LBFO), allows multiple network adapters to be
placed into a team for the purposes of bandwidth aggregation, and/or traffic failover to maintain
connectivity in the event of a network component failure. This feature has long been available from
NIC vendors but until now NIC teaming has not been included with Windows Server.
Do I have to select a standby member to get fault tolerance (failover)? No. IN any team with two or
more network adapters if a network adapter fails in an Active/Active configuration, the traffic on
that network adapter will gracefully failover to the other network adapters in the team even if none
of the other adapters are in standby mode.
Number of NICs in a team in a native host
NIC teaming requires the presence of at least one Ethernet NIC. A team of one NIC may be used for
separation of traffic using VLANs. Obviously a team with only one team member has no failure
protection. Fault protection (failover) requires a minimum of two Ethernet NICs in the team. The
Windows Server 2012 implementation supports up to 32 NICs in a team.
Number of team interfaces for a team Windows Server 2012 supports up to 32 team interfaces.