Which Entity Maintains VXLAN Layer 2 Isolation?
Which entity is responsible for maintaining Layer 2 isolation between segments in a VXLAN environment?
Community Insight
The question tests the distinction between the identifier that defines isolation (VNID) and the device that carries traffic (VTEP), and the trap is choosing the more familiar 'entity' VTEP over the actual isolation mechanism.
This 350-401 question asks which VXLAN component keeps Layer 2 segments isolated from one another. The answer is the VNID, the 24-bit segment identifier that functions like a VLAN ID and defines each separate broadcast domain in the VXLAN overlay.
Option C (VTEP) is the most tempting wrong pick because it is a real device-like entity that encapsulates traffic; however, VTEP only applies and forwards based on the VNID — it does not itself define or maintain the boundary between segments.
Community Discussion (28 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The 24-bit VNID (VXLAN Network Identifier) is precisely what identifies each Layer 2 segment and maintains isolation between those segments, exactly as a VLAN ID does in a traditional switched network. Cisco Press describes the VNID as the value used "to identify Layer 2 segments and to maintain Layer 2 isolation between the segments," and it scales VXLAN to roughly 16 million distinct broadcast domains. Every frame entering the overlay is stamped with a VNID, and no traffic crosses segment boundaries unless it is routed, so the isolation property resides in the VNID itself. This matches the question's wording almost verbatim, making A the intended and technically defensible answer.Why the Other Options Are Wrong
Option C, the VTEP, is the encapsulating/decapsulating endpoint (usually an NVE on a leaf or host) that reads and applies the VNID — it is the courier that reads the label, not the label that defines the segment. Option B, the switch fabric, refers to the underlay spine/leaf transport that carries encapsulated packets and provides no L2 segment separation on its own. Option D, the host switch, is a generic term for an access device and has no defined role in VXLAN segmentation. Choosing any of these confuses the forwarding mechanism with the isolation identifier that the question asks about.Community Comment Notes
Most commenters landed on A, with Rockford simply noting "VNID - VXLAN Network IDentifier" and chakspear insisting "It's VNID guys." ShadyAbdekmalek backed A with a Cisco Press citation that mirrors the question wording, and achille5 offered a shipping analogy in which "VNID = tracking number" while the VTEP is only "the courier hub." nightstalker pushed back that a VNID is not an entity and that "the entity that enforces isolation based on the VNID is the VTEP," and 074a077 similarly argued for C — but their own explanations confirm the VTEP merely applies the VNID. tumajay documented how an AI assistant flip-flopped between VNI and VTEP, which shows why the distinction is a classic trap on this exam.Official Reference
Exam Strategy
When a question uses the phrase "maintaining Layer 2 isolation between segments," look for the identifier value (VNID/VNI) rather than the forwarding device — similar to how a VLAN ID, not the switch port, defines the broadcast domain boundary.
Frequently Asked Questions
Why isn't the VTEP the answer for VXLAN Layer 2 isolation?
The VTEP only encapsulates and decapsulates frames and forwards them using the VNID. It applies the segmentation value, but the VNID itself defines and maintains the segment boundary.
Is a VNID an entity or just an identifier?
VNID is the 24-bit VXLAN Network Identifier — a segment ID rather than a device. In this question's wording, however, it is the component responsible for keeping Layer 2 segments isolated.
Related Analysis
Practice All 350-401 Questions
Access 218 questions with complete answers and detailed explanations.
View Full 350-401 Practice Test →