What are the two main characteristics of Cisco vManage APIs?

What are two characteristics of vManage APIs? (Choose two.)

Northbound API is based on RESTCONF and JSON.
Southbound API is based on NETCONF and XML. Source Reference Answer
Southbound API is based on RESTCONF and JSON.
Southbound API is based on OMP and DTLS.
Northbound API is RESTful using JSON. Source Reference Answer

Community Votes

84%

16%

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

Community Insight

It evaluates your knowledge of SD-WAN management plane interfaces, with the common trap being the confusion between control plane protocols (OMP/DTLS) and actual management API transports.

This question tests the distinction between northbound and southbound API protocols in Cisco SD-WAN vManage. The community consensus confirms that the northbound API is RESTful/JSON while the southbound API utilizes NETCONF/XML.

Many candidates incorrectly select options A and E, focusing solely on the northbound API and missing the required southbound component, or they erroneously choose D by mistaking OMP and DTLS for management API protocols rather than control and security layer functions.

Community Discussion (6 comments)

chiacche 👍 2 Selected: BE

vManage APIs: Southbound API (NETCONF/XML)N Northbound API (RESTful/JSON)

[Removed] 👍 2 Selected: BE

B & E are correct The Network Configuration Protocol (NetConf) uses an Extensible Markup Language (XML) to communicate with the switches and routers to install and make configuration changes. NETCONF is an XML-based protocol used for configuration and monitoring devices in the network. https://www.sdxcentral.com/networking/sdn/definitions/what-the-definition-of-software-defined-networking-sdn/southbound-interface-api/#:~:text=The%20Network%20Configuration%20Protocol%20(NetConf)%20uses%20an%20Extensible%20Markup%20Language%20(XML)%20to%20communicate%20with%20the%20switches%20and%20routers%20to%20install%20and%20make%20configuration%20changes https://docs.opendaylight.org/projects/netconf/en/latest/user-guide.html#:~:text=NETCONF%20is%20an%20XML%2Dbased%20protocol%20used%20for%20configuration%20and%20monitoring%20devices%20in%20the%20network.

Adalberto 👍 2 Selected: AE

The correct options are: A. Northbound API is based on RESTCONF and JSON. E. Northbound API is RESTful using JSON. Both of these options correctly describe the characteristics of the vManage's Northbound API. Thank you for your understanding, Nuno!

gorillaenhanced 👍 4 Selected: BE

"vManage is the management plane for the overall SDWAN solution. It uses netconf/YANG to talk to vEdge devices"

outnumber_gargle024 👍 1 Selected: DE

DE OMP and DTLS are the protocols used by vManage API to communicate with the Cisco devices

Mistwalker 👍 2 Selected: BE

Answer is correct, Northbound = RESTful, Southbound = NETCONF https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2020/pdf/DEVNET-1380.pdf

Comments & Corrections

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

Expert Analysis

Understanding vManage API Architecture

Cisco vManage serves as the centralized network management system for SD-WAN deployments, utilizing distinct protocols for northbound and southbound communications. The northbound API provides an external-facing interface for third-party orchestration tools, automation platforms, and integration frameworks. As noted in community discussions, this interface is explicitly designed as RESTful using JSON, making option E correct. While some sources mention RESTCONF, vManage's primary northbound implementation leverages standard REST principles with JSON payloads for maximum interoperability.

Southbound Communication Protocols

The southbound API handles internal communication between vManage and the managed edge devices (vEdges/cEdges). For configuration and state retrieval, vManage relies on NETCONF with YANG models, which inherently uses XML for data encoding. This makes option B the second correct choice. NETCONF is specifically chosen for its robust transactional capabilities, rollback features, and standardized schema-driven configuration model, which are critical for enterprise SD-WAN rollouts.

Eliminating Incorrect Options

Option A is partially descriptive but less accurate than E for vManage's official northbound specification, and selecting both A and E leaves no room for the mandatory southbound answer. Option C incorrectly assigns RESTCONF/JSON to the southbound interface, reversing the actual architecture. Option D references OMP (Overlay Management Protocol) and DTLS (Datagram Transport Layer Security), which are fundamental to the SD-WAN control and secure transport planes, respectively, but play no role in vManage’s API communication layers. Confusing these plane-specific protocols with management APIs is a frequent pitfall highlighted by candidates.

Official Reference

Exam Strategy

Always map API directionality first: northbound equals external integration (REST/JSON), southbound equals device management (NETCONF/XML). When faced with multiple plausible-sounding options, eliminate control/data plane protocols like OMP, IPsec, or DTLS immediately, as they belong to different architectural layers and will never appear as API transport mechanisms.

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