How does a dynamic vNIC get allocated?
A.
Dynamic vNICs are assigned to VMs in VMware vCenter.
B.
Dynamic vNICs can only be bound to the service profile through an updating template.
C.
Dynamic vNICs are bound directly to a service profile.
D.
Dynamic vNICs are assigned by binding a port profile to the service profile.
You can configure the LAN and SAN connectivity for a service profile through either of the following methods:
•LAN and SAN connectivity policies that are referenced in the service profile
•Local vNICs and vHBAs that are created in the service profile
•Local vNICs and a SAN connectivity policy
•Local vHBAs and a LAN connectivity policy
Cisco UCS maintains mutual exclusivity between connectivity policies and local vNIC and vHBA configuration in the service profile. You cannot have a combination of connectivity policies and locally created vNICs or vHBAs. When you include a LAN connectivity policy in a service profile, all existing vNIC configuration is erased, and when you include a SAN connectivity policy, all existing vHBA configuration in that service profile is erased
When defining an LAN connection policy it requires one or more of the following resources to exist on the system
• Named VLAN
• MAC pool
• QoS policy
• LAN pin group
• Statistics threshold policy
From the above answer B is incorrect as you can directly associate a local vNIC with a service profile as well as use a template
answer d is incorrect because a port profile is not related to configuring an vNIC
Port profiles contain the properties and settings used to configure virtual interfaces in Cisco UCS for VN-Link in hardware. The port profiles are created and administered in Cisco UCS Manager. There is no clear visibility into the properties of a port profile from VMware vCenter.
In VMware vCenter, a port profile is represented as a port group. Cisco UCS Manager pushes the port profile names to vCenter, which displays the names as port groups. None of the specific networking properties or settings in the port profile are visible in VMware vCenter.
After a port profile is created, assigned to, and actively used by one or more DVSes, any changes made to the networking properties of the port profile in Cisco UCS Manager are immediately applied to those DVSes.
You must configure at least one port profile client for a port profile, if you want Cisco UCS Manager to push the port profile to VMware vCenter
When creating a port profile the setting configured include
QoS Policy
Network Control policy
Max Ports – The mac number of ports that can be associated with the created port profile
Pin Group
You can also select the VLAN you require for this port profile and which VLAN will be considered the native Vlan
Take a look at both of these
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/1-3-1/b_UCSM_GUI_Configuration_Guide_1_3_1/UCSM_GUI_Configuration_Guide_1_3_1_chapter32.html#concept_8F2249C39F3443338C29BA384C06091C
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/gui/config/guide/1-3-1/b_UCSM_GUI_Configuration_Guide_1_3_1/UCSM_GUI_Configuration_Guide_1_3_1_chapter32.html#concept_8F2249C39F3443338C29BA384C06091C
There is also this
The dynamic vNIC connection policy determines how the connectivity between VMs and dynamic vNICs is configured. This policy is required for Cisco UCS domains that include servers with VIC adapters on which you have installed VMs and configured dynamic vNICs.
Each dynamic vNIC connection policy includes an Ethernet adapter policy and designates the number of vNICs that can be configured for any server associated with a service profile that includes the policy.
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/sw/vm_fex/kvm/gui/config_guide/2-1/b_GUI_KVM_VM-FEX_UCSM_Configuration_Guide_2_1.pdf