A university automates Catalyst Center to push campus QoS policy and to feed a NOC dashboard with client health trends. The code must separate intent changes from operational insight calls. Which distinction contrasts Intent API versus Network Assurance API roles?
Select an answer to reveal the explanation.
Short Explanation
You keep building apart from watching so each call lands where it should. Your split is like design team versus watch team with clear jobs.
Full Explanation
In Catalyst Center (formerly DNA Center), the Intent API expresses business intent by creating sites, policies, templates and provisioning devices, while the Network Assurance API exposes operational insight such as device, client and application health, issues and trends for NOC dashboards, so policy push and health reads belong to different domains. Reversing the roles sends provisioning to the insight layer and health to the intent layer, which fails both goals. Syslog-only plus shelved CLI mischaracterizes both APIs and misses intent translation and assurance analytics. Login-only plus image deploy narrows each API to unrelated admin tasks. Exam caveat: intent equals configure and provision, assurance equals monitor and diagnose. Practical check: check the API reference path groups and test one intent POST plus one assurance GET in lab.