A customer has a hybrid VMware SD-WAN deployment and wants to use the SD-WAN Service Reachable feature on the private WAN. What is the main dependency that must be met for the feature to work?

Question

Options

• AInternet reachability via the private WAN
• BGateway IPs must be routed in the overlay
• CDefault route learned via dynamic routing
• DStatic mute for gateway IPs on the edge

• A
  6% (3)
• B
  14% (7)
• C
  76% (38)
• D
  4% (2)

Explanation

Option C is correct because the SD-WAN Service Reachable feature on a private WAN requires the Edge to dynamically learn a default route over that private WAN link (via BGP or OSPF) - this default route is what the Edge uses to forward traffic toward the SD-WAN Gateways through the underlay, enabling overlay tunnel establishment without internet access.

Why the distractors are wrong:

• A is self-contradicting - private WAN links don't provide internet reachability by design; the feature exists precisely to support gateway connectivity without internet on that link.
• B confuses cause and effect - overlay routing is the result of the tunnel coming up, not a prerequisite for establishing it; underlay routing is what matters here.
• D is close but wrong - the feature depends on a dynamically learned default route, not static routes to gateway IPs; static configuration is a different (and unsupported) approach for this feature.

Memory tip: Think of "Service Reachable" - the Edge must dynamically reach the gateway. Dynamic routing (BGP/OSPF) provides the path advertisement; without it, the Edge has no learned route to follow across the private WAN.

No community discussion yet for this question.