A global logistics firm with 800 sites needs the control plane to survive a controller failure and to scale OMP load, considering three SD-WAN Controllers with affinity for regional edges. Connections must reconverge without full outage. Which control-plane scale and redundancy design using multiple controllers and controller groups meets the need?
Select an answer to reveal the explanation.
Short Explanation
You never want one brain for 800 sites — affinity spreads load while keeping backup paths warm. Edges stay tied to multiple controllers, so one loss barely ripples.
Full Explanation
OMP control-plane scale and redundancy come from deploying multiple SD-WAN Controllers (formerly vSmart) where each WAN Edge forms persistent control connections to more than one controller, and controller groups with affinity steer regional edges to preferred controllers while preserving failover; if one controller is lost, routes and policies remain available through survivors and reconvergence is rapid. A single controller fails by concept because it creates a single failure domain and OMP scaling bottleneck regardless of timer tuning. Using Validators fails by concept because SD-WAN Validators (formerly vBond) handle orchestration, serial validation, and NAT traversal, not OMP route computation and policy distribution. Using Managers fails by concept because SD-WAN Manager (formerly vManage) provides management and monitoring, not OMP control-plane peering to edges. Exam caveat: know which component owns OMP versus orchestration versus management when diagrams mix icons. Practical check: verify control connections and affinity with show control connections and controller-group status.