What is a Key Characteristic of Cisco vManage?

What is a characteristic of vManage?

  1. It leverages the overlay management protocol to interface with WAN Edge devices.
  2. It supports protocols such as OSPF to integrate with legacy network devices.
  3. It requires a public IP address to allow WAN Edge devices to discover fabric components.
  4. It uses NETCONF to configure vSmart devices to build the overlay network data plane. Source Reference Answer

Community Votes

D
54%
A
46%

54% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The question evaluates whether you recognize vManage's reliance on NETCONF for device configuration, despite the option's slightly imprecise reference to the 'data plane'.

This question tests vManage's communication protocols within the SD-WAN fabric. While technically nuanced, the exam expects NETCONF as the primary configuration method used by vManage to manage controllers and edge devices.

Candidates often select Option A because OMP is heavily emphasized in SD-WAN studies, mistakenly attributing it to vManage's direct communication with edge devices instead of recognizing it belongs to the vSmart control plane.

Community Discussion (11 comments)

Mistwalker 👍 13 Selected: D
vManage => NETCONF => vSmart => OMP => VEdge While it's true that the vSmart controllers don't construct the data plane, answers A and B are clearly referencing vSmart.
matass_md 👍 1 Selected: A
The answer is A , the reason it's not D is because vSmart build the CONTROL plane not data PLANE , data plane is made out of IPsec tunnels.
chmacnp 👍 1
D - every article I read and note I have suggests the answer is D, but for some reason I have a note that vManage leverages OMP to interface with vEdge and CertyIQ answer is also A. I am sure it is D
chmacnp 👍 1 Selected: D
D - every article I read and note I have suggests the answer is D, but for some reason I have a note that vManage leverages OMP to interface with vEdge and CertyIQ answer is also A. I am sure it is D
dkonly 👍 1 Selected: A
For me is definitivly answer A
cjoyce1980 👍 4 Selected: A
A. It leverages the overlay management protocol to interface with WAN Edge devices. Explanation: vManage is part of the Cisco SD-WAN solution, serving as the central management platform for configuring, monitoring, and managing SD-WAN edge devices. It uses the Overlay Management Protocol (OMP) to communicate with WAN Edge devices, ensuring that policies and configurations are distributed across the network. Why other options are incorrect: B: vManage does not support legacy routing protocols like OSPF directly. Instead, it focuses on SD-WAN protocols and policies. C: vManage does not require a public IP address for WAN Edge devices to discover fabric components. Discovery typically occurs through a centralized orchestration system (vBond) using secure control plane protocols. D: vManage does use NETCONF, but it primarily configures WAN Edge devices, not directly vSmart devices, which handle control plane policies. vSmart also communicates with WAN Edge devices using OMP.
[Removed] 👍 1 Selected: D
all answers are wrong, however the closeset one is D
Shri_Fcb10 👍 1 Selected: C
For me its C bcoz vManage requires a public IP address to enable WAN Edge devices to discover and communicate with the components of the SD-WAN fabric. This is necessary for the establishment and management of the overlay network. Option D:- This characteristic is not accurate. vManage primarily uses NETCONF for communication with WAN Edge devices, not vSmart devices, to configure and manage the overlay network. A:- This characteristic is also not accurate. vManage primarily uses NETCONF, RESTCONF, and other protocols to communicate with WAN Edge devices, rather than overlay management protocols.
masrur 👍 4 Selected: A
Not D: Cisco vSmart it is belongs to control plane and it is the brain of the solution. It is responsible for enforcing the policies centrally. These policies are created on the vManage.
Mistwalker 👍 1
OMP is really for vSmart a.k.a. SD-WAN Controllers to communicate with each other and the edge devices. vManage (now SD-WAN Manager) uses NETCONF for its communications to the controllers, per the below link. Some quotes: "The NETCONF protocol defines a mechanism through which network devices are managed and configured. The SD-WAN Manager uses NETCONF for communication with SD-WAN devices, primarily over DTLS/TLS, but there are a few situations where NETCONF is used natively before DTLS/TLS connections are formed." "The Overlay Management Protocol (OMP), a TCP-based protocol similar to BGP, provides the routing for the overlay network. The protocol runs between SD-WAN Controllers and WAN Edge routers where control plane information is exchanged over secure DTLS or TLS connections." https://www.cisco.com/c/en/us/td/docs/solutions/CVD/SDWAN/cisco-sdwan-design-guide.html
outnumber_gargle024 👍 3 Selected: A
It leverages the overlay management protocol to interface with WAN Edge devices1. Cisco vManage is a highly customizable dashboard that simplifies and automates the deployment, configuration, management, and operation for Cisco SD-WAN2. It uses the overlay management protocol (OMP) to communicate with vSmart controllers and WAN Edge devices, and to exchange routing, policy, and management information3. 1: Cisco SD-WAN Design Guide 2: Cisco Catalyst SD-WAN Manager (formerly vManage) - Cisco 3: SD-WAN API, Release 20.6 - Cisco DevNet

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Understanding vManage’s Role in SD-WAN

Cisco vManage serves as the centralized management plane for the SD-WAN fabric. Its primary function is to provide a single pane of glass for configuring, monitoring, and troubleshooting network elements. To accomplish this, vManage relies on standardized configuration protocols rather than dynamic routing protocols.

Protocol Breakdown: NETCONF vs. OMP

The defining characteristic tested here is NETCONF (Network Configuration Protocol). vManage uses NETCONF (alongside RESTCONF/gRPC in newer versions) to push YANG-based configurations to both vSmart controllers and WAN Edge devices. While Option D incorrectly implies vManage builds the "data plane," the inclusion of NETCONF makes it the only viable choice. In contrast, OMP (Overlay Management Protocol) is exclusively used by the vSmart control plane to exchange routing, policy, and topology information with edge devices. vManage does not natively speak OMP.

Why Other Options Fail

  • Option A misattributes OMP to vManage. OMP operates strictly between vSmart and WAN Edge routers.
  • Option B confuses management with legacy routing. OSPF runs on edge devices for internal routing, not on vManage.
  • Option C incorrectly mandates a public IP. SD-WAN fabrics support private addressing with NAT traversal for cloud discovery.
Community feedback highlights a common trap: candidates gravitate toward OMP because it dominates SD-WAN study guides, overlooking that vManage’s configuration engine is fundamentally NETCONF-driven. Exam logic prioritizes the correct protocol association over perfect architectural phrasing.

Official Reference

Exam Strategy

When answering vManage protocol questions, prioritize NETCONF or gRPC for configuration tasks and reserve OMP exclusively for vSmart control-plane exchanges. If an option contains a minor architectural inaccuracy but correctly identifies the core management protocol, it is usually the intended answer over options with completely wrong protocols.

Related Analysis

Practice All 350-401 Questions

Access 218 questions with complete answers and detailed explanations.

View Full 350-401 Practice Test →

← Back to 350-401 Study Guide