Q: 2
What are two benefits of model-driven programmability?
Options
Discussion
A/E, not C. Trap is thinking human-friendly means model-driven, but that's more about structure than abstraction or decoupling.
C or D could fit too. Model-driven programmability definitely makes APIs a bit easier and more human-friendly, which both C and D hint at. Not totally sold those are the main "architectural" benefits Cisco's after, but they're both plausible in real-world situations. Maybe missing the abstraction piece but still makes sense from a dev's view.
A and E. Main benefits are abstraction via models and flexibility because the model isn't tied to one protocol or encoding. Pretty sure that's what official study material highlights, but open if anyone sees it differently from labs or exam practice.
Yeah, has to be A and E for core model-driven programmability benefits.
Its A and E, saw a similar question on a practice test. Matches the main model-driven programmability benefits.
C or D here. Model-driven stuff always felt more about being human-friendly and making APIs easier to handle, so those feel like legit benefits to me. Not totally sure if that's what Cisco's after, open to other takes.
Every Cisco exam just loves these model-driven terms. Pretty sure it's A and E for the core benefits.
Option A and E. Model-driven APIs abstract things, and models being decoupled from transport is key here.
C and D. Question is really clear, easy to follow.
Be respectful. No spam.
Question 2 of 35