What Characterizes Cisco DNA Center and vManage Northbound APIs?
What is one characteristic of Cisco DNA Center and vManage northbound APIs?
Community Votes
81% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests your ability to distinguish between application-layer protocol standards and data payload formats, warning against confusing northbound intent APIs with southbound configuration mechanisms.
This question evaluates understanding of Cisco SD-Architecture interfaces, specifically differentiating northbound intent APIs from southbound device protocols. The community consensus confirms that both platforms implement the RESTCONF protocol for their northbound programmatic interfaces.
Candidates frequently select XML-formatted content, mistaking a common REST payload type for the defining protocol characteristic. Others incorrectly choose NETCONF, erroneously applying southbound device-management protocols to the northbound management plane.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Northbound vs. Southbound Interface Roles
In Cisco’s “DNA” and SD-Access architectures, the system is logically divided into northbound and southbound interfaces. Northbound APIs expose business intent and platform capabilities to external applications, orchestrators, and developers. Southbound protocols handle the actual translation of those intents into device-specific commands.Why RESTCONF is the Correct Answer
Both Cisco DNA Center and vManage expose their Intent APIs via RESTCONF (RFC 8040) over HTTPS. RESTCONF was specifically designed as a modern, standards-based replacement for legacy SOAP and proprietary XML interfaces, providing a clean, resource-oriented programming model. As noted by top-voted community members, these platforms leverage RESTCONF to allow external systems to query state and submit configuration intents programmatically.Debunking the Distractors
- Option A describes a southbound action. Northbound APIs do not push configurations directly to network devices; they receive high-level intent and translate it internally before using southbound protocols.
- Option B focuses on data formatting. While RESTCONF can technically transmit XML, JSON is overwhelmingly preferred in Cisco’s ecosystem, and payload format is never the defining architectural characteristic tested here.
- Option D cites NETCONF, which is primarily a southbound protocol used to configure underlying network elements (routers, switches, firewalls), not a northbound feature for external orchestration.
Official Reference
- https://www.cisco.com/c/en/us/td/docs/cloud-systems-management/network-automation-and-management/dna-center-platform/2-3-7/user-guide/b-dnac-platform-ug-2-3-7/b-dnac-platform-ug-2-3-7-chapter-01.html#:~:text=Intent%20APIs%3A%20The%20Intent%20APIs,mechanisms%20that%20implement%20that%20outcome.
- https://www.rfc-editor.org/rfc/rfc8040
- https://developer.cisco.com/docs/xdn/
Exam Strategy
When tackling automation questions, immediately map the interface direction (northbound vs. southbound) to its primary function before evaluating protocol options. Memorize that northbound intent layers rely on RESTCONF/REST over HTTPS, while southbound device control utilizes NETCONF, RESTCONF, SNMP, and gRPC. This mental filter will instantly eliminate format-based distractors and misapplied southbound protocols.
Related Analysis
Practice All 350-401 Questions
Access 218 questions with complete answers and detailed explanations.
View Full 350-401 Practice Test →