What is true about the VSX switches in EVPN VXLAN?

Question

Options

• AYou should make the two switches in the VSX pair operate as a single logical VTEP
• BVSX stacking and EVPN VXLAN are mutually exclusive
• CEach member of the VSX acts as standalone from the EVPN VXLAN perspective

• A
  86% (36)
• B
  5% (2)
• C
  10% (4)

Explanation

In EVPN VXLAN deployments, VSX (Virtual Switching Extension) pairs are designed to share a single anycast VTEP IP address - typically a common loopback - so the rest of the fabric sees them as one logical VTEP rather than two separate tunnel endpoints. This enables active-active redundancy and seamless failover without the fabric needing to recalculate paths when one switch goes down.

Option B is wrong because VSX and EVPN VXLAN are fully compatible and commonly deployed together; they complement each other rather than conflict.

Option C is wrong because the whole point of VSX is to eliminate standalone behavior - both switches coordinate through the ISL (Inter-Switch Link) and present a unified control and data plane to the EVPN fabric.

Memory tip: VSX = "Virtual Single VTEP" - two physical boxes, one logical tunnel endpoint. If you remember that VSX's job is to make two switches look like one, the correct answer follows naturally.

No community discussion yet for this question.