Capability of Model-Driven Programmability
Short answer
C Model-driven programmability exposes generic APIs built on standardized YANG models, so the same automation works across multiple platforms.
Question
Key Takeaways
Tests what model-driven programmability actually delivers — decoupled, standardized APIs — against the misconception that one global data model spans the whole network.
Model-driven programmability exposes generic, model-based APIs such as NETCONF and RESTCONF running on standardized YANG models, so the same automation can drive multiple platforms.
Common mistake: Learners choose "a single data model across the network", but models are defined per device (native, OpenConfig, IETF); standardization means vendor-neutral APIs, not one universal model.
Expert Analysis
Why the Answer Is Correct
Model-driven programmability describes device data with structured models — most commonly YANG — and serves that data through generic, protocol-based APIs such as NETCONF and RESTCONF. Because the model (what the data means) is decoupled from the transport, protocol and encoding, the same API and tooling can drive devices from different platforms and vendors. That vendor-neutral, reusable API surface is the capability the question asks about, and it is what lets automation scale beyond a single hardware family.
Why the Other Options Are Wrong
Compatibility with "any" networking device is an overstatement: a device must implement the relevant model and management protocol, and legacy or closed platforms often do not. Automatic version control is a workflow benefit of automation tooling such as Git, not a property that model-driven programmability itself provides. A single data model across the whole network is a common misconception — each device exposes its own native model alongside shared standards such as IETF and OpenConfig, so there is no one universal model for everything.
Community Comment Notes
Most commenters back this option and tie it to YANG. One explains that standardized models like YANG yield "generic APIs that facilitate interoperability across various platforms", and a third learner reaches the same conclusion. The dissenting note simply asserts the single-model option without argument, which matches the misconception the distractors are built on.
Official Reference
- https://developer.cisco.com/docs/modeling-labs/
- https://www.rfc-editor.org/rfc/rfc7950
- https://www.rfc-editor.org/rfc/rfc6241
These links open the official vendor documentation in a new tab.
Exam Strategy
Remember the decoupling: model-driven APIs separate the data model from transport, protocol and encoding. That is why one API toolset can target many platforms — the wording the exam rewards.
Frequently Asked Questions
Why is "a single data model" wrong?
Which protocols do these generic APIs use?
Community Votes
60% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
daniii89 👍 1 Answered CC. Generic APIs that are compatible with multiple platforms By leveraging standardized data models like YANG, model-driven programmability provides generic APIs that facilitate interoperability across various platforms.
-
ciscowiz 👍 2 Answered Dits D for sure
-
christyronny7 👍 2 Answered CIt's C, right?
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All 200-901 Questions
Access 105 questions with complete answers and detailed explanations.
View Full 200-901 Practice Test →