Which statements are true regarding a VXLAN Implementation on HPE Aruba Networking switches? (Select two.)

Question

Options

• AThey are only available for datacenter switches (CX 8k, 9k, 10k).
• BVNIs encapsulate and decapsulate VXLAN traffic.
• CMTU size must be increased beyond the default.
• DAll AOS-CX switches support VXLAN.
• EVTEPs encapsulate and decapsulate VXLAN traffic.

• A
  5% (2)
• B
  9% (4)
• C
  84% (36)
• D
  2% (1)

Explanation

VTEPs (VXLAN Tunnel Endpoints) are the network devices that actually perform encapsulation and decapsulation of VXLAN traffic - wrapping Layer 2 frames inside UDP/IP packets and unwrapping them at the destination, making E correct. Because VXLAN adds roughly 50 bytes of header overhead (outer Ethernet + IP + UDP + VXLAN headers) to every frame, the default 1500-byte MTU is insufficient and must be increased (typically to 1600+ or jumbo frames at 9000), making C correct.

Why the distractors are wrong:

• A is false - VXLAN is not exclusive to CX 8k/9k/10k datacenter switches; it is available on a broader range of AOS-CX platforms.
• B confuses VNIs with VTEPs - VNIs (VXLAN Network Identifiers) are simply 24-bit logical segment labels (analogous to VLAN IDs), not the components doing encapsulation/decapsulation.
• D overstates support - not all AOS-CX switches support VXLAN; support depends on the specific model and its feature set.

Memory tip: Think of VTEP as "VXLAN Tunnel = Encapsulates Packets" - the endpoint of the tunnel does the work. For MTU, remember "VXLAN = eXtra bytes = eXpand your MTU."

No community discussion yet for this question.