3Cisco Platforms and Development

• 3.1Cisco SDKs and network management APIs

  Covers how an SDK (a language-specific library) abstracts raw REST calls, and the scope of the main network-management platforms—Meraki (Dashboard API), Catalyst Center (Intent API), ACI (APIC), Catalyst SD-WAN, and Cisco NSO—framed as the judgment of "which platform's API to choose for this requirement."

• 3.2Compute, collaboration, and security APIs

  Covers compute (UCS Manager's on-prem XML API and Intersight's cloud REST), collaboration (the Webex API and CUCM's AXL/UDS), and security (XDR, Firepower (FMC), ISE (ERS), Secure Malware Analytics), framed as the judgment of "which domain's API solves this operational requirement."

• 3.3Device APIs and model-driven programmability

  Covers the on-box APIs of IOS XE/NX-OS and the three pillars of model-driven programmability—YANG (data-model definition), NETCONF (XML/SSH with datastores), and RESTCONF (HTTP+JSON/XML, CRUD<->HTTP methods)—as response interpretation and method selection. It also pins down DevNet learning/testing resources (Sandbox, Code Exchange, Learning Labs, API docs).

• 3.4Building code to meet a requirement

  Covers typical tasks—fetching a device list (Catalyst Center Intent API/Meraki), posting a message to Webex, and fetching a client list (Meraki)—as the construction judgment of "requirement -> which platform's endpoint and HTTP method to assemble," along with diagnosing faulty scripts (missing auth, wrong endpoint, method mismatch).