vPC+ Feature Selection for VXLAN Multipod Design
Refer to the exhibit. An engineer must design a solution to support a customer's rapidly growing online business. After consulting with the customer, the engineer determined: • VXLAN multipod will provide the most optimal Layer 3 transport between web server clusters. • Devices should be multihomed in an active/active configuration using LACP. • No FEX or virtual switching is needed. • vPC will be implemented to maximize throughput and provide redundancy for web server clusters. Which feature must the engineer select to support this design? - 
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests the distinction between standard vPC and vPC+, specifically highlighting that vPC+ is designed for interconnecting with ACI or VXLAN fabrics where the switch acts as a vPC peer.
This question evaluates the correct vPC variant for connecting traditional server clusters to a VXLAN EVPN fabric, establishing that vPC+ is the required feature.
Candidates often choose 'enhanced vPC' or 'double-sided vPC' due to terminology confusion, failing to recognize that vPC+ is the specific term for Fabric Extender-like connectivity in Nexus 9000 VXLAN deployments.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is A (vPC+) because the design involves a VXLAN multipod architecture. In Cisco Nexus 9000 Series switches running NX-OS, vPC+ is the feature that allows a traditional vPC domain to connect to an ACI fabric or a VXLAN EVPN fabric where the upstream device acts as a virtual peer. It simplifies the configuration by eliminating the need for manual peer-link and peer-switch configurations typically found in standard vPC, making it ideal for the described optimal Layer 3 transport scenario.Why the Other Options Are Wrong
Option B (single-sided vPC) is not a standard Cisco term for this high-redundancy active/active requirement. Option C (enhanced vPC) usually refers to feature enhancements like LACP load balancing but does not inherently support the VXLAN fabric integration described. Option D (double-sided vPC) is also not a standard feature name; while the topology might be double-sided physically, the logical feature enabling this specific VXLAN integration is vPC+.Community Comment Notes
Community feedback strongly supports vPC+. One user noted that 'VPC+ is appropriate to connect the traditional vPC to Fabric vPC,' which aligns with the official documentation regarding VXLAN multipod designs. Another user debated between vPC+ and other options but ultimately acknowledged the specific use case for vPC+ in fabric integrations.Exam Strategy
When designing for VXLAN multipod or ACI integration, always look for 'vPC+' as the solution for connecting traditional data center servers. Remember that vPC+ abstracts the peer-link complexity, allowing the fabric to manage the redundancy automatically.
Frequently Asked Questions
What is the main difference between vPC and vPC+?
vPC requires manual peer-link and peer-switch configuration, while vPC+ automates these aspects when connecting to an ACI or VXLAN fabric.
Can I use standard vPC for VXLAN multipod?
No, standard vPC is not optimized for direct integration with VXLAN fabrics without significant complexity; vPC+ is the intended feature.