Cisco SD-WAN Controller for Provisioning and Configuration
Which controller is used for provisioning and configuration in a Cisco SD-WAN solution?
Community Votes
75% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It distinguishes between the three controller types (vBond, vSmart, vManage) by mapping 'provisioning and configuration' to vManage, while noting that vSmart handles control plane routing.
This question tests the specific role of the Cisco Catalyst SD-WAN controllers, identifying vManage as the component responsible for centralized provisioning and configuration.
Learners often select vSmart because it is the primary 'controller' for traffic flow and policy enforcement, confusing control plane orchestration with management plane configuration.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The question asks which controller is used for provisioning and configuration. In the Cisco SD-WAN architecture, vManage (now known as the SD-WAN Manager) is the centralized network management system. It provides a single pane of glass for deploying configurations, managing templates, monitoring the network, and handling software upgrades. Therefore, Option A is the correct answer.Why the Other Options Are Wrong
- vBond (Option B): This is the orchestrator controller. Its primary role is to authenticate devices, discover other controllers, and facilitate NAT traversal. It does not handle provisioning or configuration tasks.
- WAN Edge router (Option C): These are the edge devices (CPEs) that forward traffic. They receive configurations but do not perform the centralized provisioning function asked in the question.
- vSmart (Option D): This is the control plane controller. It distributes routing policies and maintains control plane connectivity between WAN Edge routers. While it enforces policies, it does not provide the GUI or API interface for provisioning and configuration.
Community Comment Notes
Community consensus strongly favors vManage (A). As Networkchamp87 noted, vManage includes "Centralized provisioning, troubleshooting, and monitoring" and "Deployed policies and templates." Another user, jstaruch, correctly identified that vBond handles authentication/NAT and vSmart distributes routes, reinforcing why they are incorrect for this specific question. A minority comment suggested vSmart, likely due to its name containing 'Smart' and its central role in control, but this confuses policy distribution with device configuration.Exam Strategy
Memorize the distinct roles of the three controllers: vBond (Orchestrator/Auth), vSmart (Control Plane/Routing), and vManage (Management/Provisioning). When you see 'configuration', 'templates', or 'single pane of glass', think vManage immediately.
Frequently Asked Questions
What is the difference between vManage and vSmart?
vManage is the management plane for provisioning and configuration via a GUI/API. vSmart is the control plane that distributes routing policies and maintains control sessions between WAN Edge routers.
Does vBond handle any configuration tasks?
No, vBond is strictly an orchestrator. It authenticates devices, discovers controllers, and facilitates NAT traversal, but it does not push configurations or manage the network state.
Related Analysis
Practice All 300-415 Questions
Access 120 questions with complete answers and detailed explanations.
View Full 300-415 Practice Test →