Which set of actions ensures that the Cisco UCS network configuration contains the required VLAN...

The reusable Cisco UCS design is to define VLAN membership on vNIC templates and reference those vNIC templates from the service profile templates. Cisco states that a vNIC can be bound to a vNIC template and that UCS Manager then configures the vNIC with the values defined by that template. If a bound vNIC does not match the template, UCS Manager reconfigures it; changes must subsequently be made through the associated template. This creates a single policy location for VLAN selection, fabric choice, MTU, QoS policy references, and related vNIC properties. Binding the vNIC template to the service profile template ensures that every derived service profile receives the same intended LAN configuration. With updating templates, eligible changes can propagate to already-associated profiles in a controlled manner. Defining settings separately in each service profile template duplicates configuration and weakens consistency. Manually attaching uplinks is an infrastructure operation and does not provide reusable server-side VLAN policy. A LAN connectivity policy can group vNIC definitions, but merely declaring VLANs globally does not assign them to the vNICs consumed by the servers. Editing individual server adapters from the Hardware tab defeats policy-based stateless computing and creates configuration drift; a server adapter policy controls adapter behavior rather than VLAN membership. Option C is therefore the only approach that centralizes VLAN intent at the correct UCS abstraction and applies it consistently to all profiles derived from the templates. Cisco UCS Manager vNIC template behavior

================