A service provider wants to offer a common service from its data center via VMware SD-WAN Partner Gateway to many customers with overlapping IP addresses. Which configuration must be implemented?

Question

Options

• ADefine multiple segments tor each customer
• BEnable NAT hand off under hand off static routes configuration
• CEnable tag type QinQ under hand off interface configuration
• DConfigure source policy-based NAT under business- policies configuration

• A
  73% (29)
• B
  18% (7)
• C
  5% (2)
• D
  5% (2)

Explanation

Defining multiple segments (A) is correct because segments in VMware SD-WAN function like VRFs - each customer is placed in its own isolated routing domain with its own independent routing table, so overlapping IP addresses across customers never collide within the shared Partner Gateway infrastructure.

Option B (NAT handoff under static routes) addresses address translation at the WAN handoff point, not multi-tenant IP isolation - it doesn't create separate routing contexts per customer. Option C (QinQ tagging) is a Layer 2 VLAN-stacking mechanism used for carrier Ethernet handoffs, not a solution for Layer 3 IP overlap between tenants. Option D (source policy-based NAT in business policies) applies NAT for traffic steering decisions, but business policies operate within a single routing domain and can't solve cross-customer IP conflicts at scale.

Memory tip: Think "Segments = Separation" - just as VRFs isolate routing tables in traditional networking, SD-WAN segments provide the per-customer isolation that makes overlapping IPs a non-issue for the service provider.

No community discussion yet for this question.