In the dynamic vNIC creation wizard, why are choices for Protection important?

In the dynamic vNIC creation wizard, why are choices for Protection important?
A . They allow reserve vNICs to be allocated out of the spares pool.
B . They enable hardware-based failover.
C . They select the primary fabric association for dynamic vNICs.
D . They allow dynamic vNICs to be reserved for fabric failover.

View Answer

Answer: C

Explanation: Number of Dynamic vNICs C This is the number of vNICs that will be available for dynamic assignment to VMs. Remember that the VIC has a limit to the number of vNICs that it can support and this is based on the number of uplinks between the IOM and the FI. At least this is the case with the 2104 IOM and the M81KR VIC, which supports ((# IOM Links * 15) C 2)). Also remember that your ESXi server will already have a number of vNICs used for other traffic such as Mgmt, vMotion, storage, etc, and that these count against the limit.

Adapter Policy C This determines the vNIC adapter config (HW queue config, TCP offload, etc) and you must select VMWarePassThru to support VM-FEX in High Performance mode.

Protection C This determines the initial placement of the vNICs, either all of them are placed on fabric A or Fabric B or they are alternated between the two fabrics if you just select the “Protected” option. Failover is always enabled on these vNICs and there is no way to disable the protection.

Reference: http://infrastructureadventures.com/2011/10/09/deploying-cisco-ucs-vm-fex-for-vsphere-%E2%80%93-part-2-ucsm-config-and-vmware-integration/