Due to very strict security policies an enterprise customer is looking for an on-premises deployment of the VMware SD-WAN Orchestrator and Controllers. Customer data is not expected to flow through…

Question

Options

• AUnder gateway configuration -> Configure the Gateway roles as Control Plane, disable Data Plane
• BUnder gateway configuration -> Configure the Gateway roles as Control Plane, disable Data Plane
• CUnder gateway configuration -> Configure the Gateway roles as Control-Plane, enable Data Plane
• DUnder gateway configuration -> Configure the Gateway roles as Control-Plane, enable Data Plant-

• A
  11% (5)
• B
  2% (1)
• C
  82% (37)
• D
  4% (2)

Explanation

Option C is correct because the scenario requires the on-premises Controller to support overlay tunnels for management plane traffic from Edges to the Orchestrator - and enabling both the Control-Plane role AND the Data Plane role is what allows the Controller to participate in the overlay network and forward that tunneled traffic. Customer data not transiting the Controller is enforced through routing policy, not by disabling the Data Plane role at the gateway level.

Why the distractors fail:

• A and B are identical (a common exam trick) and both wrong for the same reason: disabling the Data Plane prevents the Controller from participating in overlay tunnels altogether, which would break the requirement that management traffic from Edges can use those tunnels.
• D contains a deliberate typo ("Data Plant" vs. "Data Plane") - it describes the same configuration as C but is an invalid/nonsensical option intended to catch inattentive readers.

Memory tip: Think of it this way - the Data Plane role is the tunnel engine; you need the engine running even if you're only carrying management passengers in it. Disabling it parks the vehicle entirely. Customer data exclusion is a policy decision, not a role decision.

No community discussion yet for this question.