A customer needs a new compute environment based on HPE Synergy with VMware vSphere 6.5. This needs to interact with the customer's exiting network consisting of 300 independent global sites. Each…

Question

Options

• ANVGRE increasing the amount of separated Layer 2 segments
• BVxLAN as it allows flexibility and suitable for multitenant environment
• CRDMA as it increases host efficiency and virtualization performance
• DVLANs as it supports up to 4094 VLAN ids

• A
  19% (9)
• B
  67% (32)
• C
  4% (2)
• D
  10% (5)

Explanation

VxLAN is correct because the customer requires 300 sites × 15 VLANs = 4,500 unique network segments, which exceeds the 4,094 limit of standard 802.1Q VLANs. VxLAN uses a 24-bit Virtual Network Identifier (VNI) supporting over 16 million isolated segments, and encapsulates Layer 2 traffic over Layer 3, making it ideal for spanning 300 globally distributed sites. It is also natively supported by VMware vSphere 6.5 (NSX/vDS), making it the right fit for this stack.

Why the distractors are wrong:

• A (NVGRE): Also supports large-scale Layer 2 segmentation, but it is a Microsoft-centric technology less integrated with VMware vSphere, and VxLAN is the dominant standard in this context.
• C (RDMA): Remote Direct Memory Access improves memory transfer performance between hosts-it has nothing to do with network segmentation or VLAN scaling.
• D (VLANs): Standard VLANs cap at 4,094 IDs. With 4,500 required segments, VLANs alone cannot satisfy the requirement-this is the exact problem VxLAN was designed to solve.

Memory tip: Think "VxLAN = eXtensible"-when the number of required segments extends beyond the 4,094 VLAN ceiling, especially across a routed WAN, VxLAN is your answer. If you see "global sites + many VLANs" in a question, do the math first.

No community discussion yet for this question.