A logistics company is rolling out 60 SD-WAN branches with zero-touch provisioning, centralized configuration, loop-free route distribution, and encrypted site-to-site transport. The design must assign each task to the right plane. Which SD-WAN function mapping correctly places orchestration, management, control and data duties?
Select an answer to reveal the explanation.
Short Explanation
You're handing each crew its own clipboard so bootstrap, config, routes, and packets stay tidy. This plane-to-box match is the backbone of scalable SD-WAN design.
Full Explanation
The correct mapping reflects SD-WAN plane separation needed for scale: the Validator authenticates chassis and coordinates zero-touch provisioning for orchestration, the Manager provides centralized templates, configuration and monitoring for management, the Controller distributes OMP routes and policy with loop avoidance for control, and WAN Edge routers build IPsec tunnels and forward traffic for data. The mapping that places orchestration on the Controller fails by concept because the Controller maintains persistent OMP sessions and distributes reachability after authorization, while initial discovery, certificate authentication and NAT-traversal coordination belong to orchestration and cannot scale securely for 60 branches otherwise. The mapping that places management on the Controller fails by concept because centralized configuration, software lifecycle and visibility are management duties, whereas the Controller is optimized for route calculation and policy enforcement and lacks the template model required for consistent operation. The mapping that trusts MPLS provider privacy for transport fails by concept because SD-WAN requires authenticated encrypted site-to-site connectivity on any underlay, and treating private MPLS as inherently secure leaves traffic unprotected and violates the encrypted transport requirement despite that assumption being common in legacy WAN practice. As an exam caveat, distinguish logical roles from similar device names and remember lab co-location does not merge plane responsibilities. As a practical check, verify onboarding authentication, template attachment, OMP peering with received routes, and IPsec associations with counters on each WAN Edge before declaring branches ready.