An engineer is implementing the Cisco ACI fabric and must create two different vPCs from leaf switches A and B. The vPCs are deployed as follows: vPC…

In Cisco ACI, a Virtual Port-Channel (vPC) allows links that are physically connected to two different leaf switches to appear as a single Port-Channel to a third device. Each logical vPC requires a set of policies that define its behavior (e.g., LACP, CDP). These policies are bundled into a vPC Interface Policy Group. Since the scenario requires creating two distinct vPCs connecting to two different servers, two separate vPC Interface Policy Groups must be created. This allows for independent policy management for each server's connection, which is a fundamental ACI design principle for scalability and modularity.

B. An access port interface policy group is used for individual, non-Port-Channel interfaces, which is incorrect for a vPC configuration.
C. A "PortChannel interface policy group" is used for a Port-Channel on a single leaf, not a vPC that spans two leaf switches.
D. Using one vPC interface policy group for two different vPCs is not best practice and limits policy flexibility, as both vPCs would be forced to share the exact same policies.

1. Cisco, Cisco APIC Layer 2 Networking Configuration Guide, Release 4.2(x), "vPC Interfaces", Section: "About vPC Interface Policy Groups". It states, "The vPC interface policy group is a container for all the policies that are related to a vPC interface."

2. Cisco, ACI Design Guide, "Access Policies", Section: "Interface Policies". The guide details the ACI object model where distinct logical constructs like separate vPCs are configured with their own policy groups for granular control.