Question 1,744 of 1,389
CCNA AI and Network Operations Practice Question
In a controller-based design, which statement best describes a northbound API?
⚠ Common exam trap
A frequent exam trap is mistaking the northbound API for a physical cable or a routing protocol. Some candidates incorrectly associate 'northbound' with physical connections between controllers or with link-state protocols, which is incorrect. Northbound APIs are purely logical interfaces used by applications to communicate with the controller, not hardware or routing mechanisms. Another trap is assuming northbound APIs bypass security controls; in reality, these APIs require proper authentication and authorization. Misunderstanding these points can lead to selecting incorrect answers that describe physical or protocol-related concepts rather than software interfaces.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
An application-facing API used by external software to communicate with the controller
A northbound API is the interface exposed by the controller to external applications, orchestration systems, dashboards, or automation tools. In plain language, it is the way software above the controller communicates with the controller so that it can request data, apply policy, or trigger changes. This is different from the southbound side, where the controller interacts with the underlying infrastructure devices. This concept appears often in automation topics because it helps define where the controller sits in the larger architecture. A northbound API is not a physical cable, and it does not replace security controls. It is an application-facing software interface, which is exactly what the correct answer should capture.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
An application-facing API used by external software to communicate with the controller
Why this is correct
In a controller-based architecture, the northbound API (often RESTful) faces applications and orchestration systems, allowing them to request network services or retrieve telemetry without manual device-level configuration. It abstracts the underlying network complexity, so external software can communicate intent to the controller, which then translates that intent into device-specific actions. This direction is 'north' because it sits above the controller in the logical hierarchy.
- ✗
A cable type used between controller clusters
Why it's wrong here
Northbound and southbound are logical labels delineating the controller's interfaces, not physical media types. A cable cannot be 'northbound' because direction is defined by data flow between layers, such as applications above and network devices below the controller. Controller clusters communicate over conventional Ethernet or IP networks, but those links are not called northbound, and they have nothing to do with application-facing APIs.
When this WOULD be correct
If the question were about the physical infrastructure of a network and asked about the types of cables used for interconnecting network devices, then option B could be correct in that context, specifically referring to a type of cable like fiber optic or Ethernet used between controller clusters.
- ✗
The link-state protocol the controller uses to reach switches
Why it's wrong here
The northbound API is not a routing protocol like OSPF or IS-IS; it is an application interface used by external systems. Controller-to-switch communication (the southbound interface) may indeed use protocols like OpenFlow or NETCONF, but the question specifically asks about the controller-based design's application-facing interface. A link-state protocol handles routing updates between routers, not API calls from software, so this option confuses data-plane routing with control-plane programmability.
When this WOULD be correct
If the question were to ask about the protocols used by a controller to communicate with switches, specifically focusing on network topology and routing, then option C could be correct as it would refer to the protocols that maintain network state information.
- ✗
A mechanism that removes the need for authentication
Why it's wrong here
This choice mistakes an API for a security control. Northbound APIs commonly require authentication, typically via HTTPS with credentials, API tokens, or certificates, and they enforce authorization so each application only gets permitted operations. Removing authentication would create a severe vulnerability, so no standard northbound API does that; instead, APIs are interfaces, not trust-elimination mechanisms.
When this WOULD be correct
In a question asking about security features of a network controller, if it specifically states that the controller's design includes a feature that eliminates the need for authentication for certain operations, then option D could be correct.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
✓An application-facing API used by external software to communicate with the controllerCorrect answer▾
Why this is correct
In a controller-based architecture, the northbound API (often RESTful) faces applications and orchestration systems, allowing them to request network services or retrieve telemetry without manual device-level configuration. It abstracts the underlying network complexity, so external software can communicate intent to the controller, which then translates that intent into device-specific actions. This direction is 'north' because it sits above the controller in the logical hierarchy.
✗A cable type used between controller clustersWrong answer — click to see why▾
Why this is wrong here
Option B is incorrect because a northbound API refers to an interface for external applications to interact with the controller, not a physical cable type used for communication between controller clusters.
★ When this WOULD be the correct answer
If the question were about the physical infrastructure of a network and asked about the types of cables used for interconnecting network devices, then option B could be correct in that context, specifically referring to a type of cable like fiber optic or Ethernet used between controller clusters.
Why candidates choose this
Candidates may be tempted by option B due to familiarity with networking concepts, where cables are often discussed in the context of connectivity, leading to confusion about the terminology used in API discussions.
✗The link-state protocol the controller uses to reach switchesWrong answer — click to see why▾
Why this is wrong here
Option C is incorrect because a northbound API refers to communication between the controller and external applications, not a link-state protocol used for switch connectivity. Link-state protocols, such as OSPF, are not classified as APIs.
★ When this WOULD be the correct answer
If the question were to ask about the protocols used by a controller to communicate with switches, specifically focusing on network topology and routing, then option C could be correct as it would refer to the protocols that maintain network state information.
Why candidates choose this
Candidates may find option C tempting due to the association of 'northbound' with network communication, leading them to mistakenly connect it with the protocols that facilitate controller-switch interactions, rather than understanding the API's role.
✗A mechanism that removes the need for authenticationWrong answer — click to see why▾
Why this is wrong here
Option D is incorrect because a northbound API is designed for communication between the controller and external applications, and it does not inherently relate to authentication mechanisms.
★ When this WOULD be the correct answer
In a question asking about security features of a network controller, if it specifically states that the controller's design includes a feature that eliminates the need for authentication for certain operations, then option D could be correct.
Why candidates choose this
Candidates may find this option tempting because they might associate APIs with security features and assume that a simplified authentication process could be a benefit of a northbound API.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
Routing Protocol Comparison
| Protocol | Metric | Max Hops | Algorithm | Type |
|---|---|---|---|---|
| RIP v2 | Hop count | 15 | Bellman-Ford | Distance vector |
| OSPF | Cost (bandwidth) | Unlimited | Dijkstra (SPF) | Link state |
| EIGRP | Composite metric | Unlimited | DUAL | Hybrid |
| IS-IS | Cost | Unlimited | Dijkstra | Link state |
| BGP | Policy / attributes | Unlimited | Path vector | Path vector |
RIP's 15-hop limit makes it unsuitable for large networks. OSPF and EIGRP dominate modern enterprise deployments.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: May 17, 2026
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.