A bank is troubleshooting why a new branch prefix is missing at remote sites while data-plane tunnels are up, and the design review must confirm control-plane responsibilities. Controllers show OMP peering established and policies unchanged. Which description correctly states the SD-WAN Controller role for control plane, route and policy distribution over OMP?
Select an answer to reveal the explanation.
Short Explanation
Tunnels are up but routes are missing, so you're looking above the packets. The Controller is your air-traffic control tower for OMP routes and policies. Forwarding and onboarding belong to other boxes.
Full Explanation
The SD-WAN Controller, formerly vSmart, is the dedicated control-plane brain that forms OMP sessions to WAN Edge routers, reflects service and transport routes, and programs centralized control and data policies so all sites share consistent reachability without full-mesh configuration. Forwarding user packets over IPsec describes the WAN Edge data-plane role, not the Controller, so it confuses control with forwarding even though tunnels depend on Controller-distributed routes. Validating identity and issuing certificates during onboarding is the Validator's authentication role (with certificates coming from the PKI), not route reflection. Hosting dashboards and configuration workflows describes SD-WAN Manager, formerly vManage, which provides management-plane visibility while the Controller handles OMP distribution. For the exam, map former vSmart directly to SD-WAN Controller and OMP; in practice check OMP peers and received routes on the Controller when prefixes are missing.