A port authority wants one operational surface for SD-WAN templates, policies, and monitoring. Which component is that single pane of glass?
Select an answer to reveal the explanation.
Short Explanation
vManage is the port’s glass cockpit—templates, policies, and health views in one place, plus APIs for automation. vBond greets devices; it is not the day-2 ops dashboard. OMP is a protocol, not a GUI, and managing dozens of Edges only from each box’s local UI does not scale.
Full Explanation
vManage is the SD-WAN management plane: operators build feature/device templates, define centralized and localized policies, monitor overlay health, and use northbound APIs. vBond orchestrates onboarding and does not replace vManage dashboards or forward user traffic. Per-Edge local UIs cannot efficiently operate a multi-site port authority overlay. OMP is the overlay routing protocol, not an operations console.