Cisco DevNet glossary of APIs, automation, and CI/CD terms, traps, and decision cues.
Use this glossary when Cisco Certified DevNet Associate (DevNet) terms start to blur together. The goal is practical recognition, not encyclopedia coverage.
| Term | Exam meaning |
|---|---|
| REST API | HTTP-based API style using resources, verbs, and status codes. |
| JSON | Structured data format commonly used by APIs. |
| Idempotency | Safe repeat execution without unintended extra changes. |
| Webhook | HTTP callback triggered by an event. |
| Controller | Platform that manages infrastructure and exposes automation APIs. |
| Token | Credential string used to authenticate API calls. |
| Pair | How to separate them |
|---|---|
| Software development basics vs Cisco platforms and APIs | Ask which layer the scenario is testing, then match the answer to that layer only. |
| Control vs evidence | A control changes behavior; evidence proves behavior or supports investigation. |
| Managed service vs custom build | Managed services win for lower operational effort unless the requirement needs unsupported customization. |
| Prevention vs detection | Prevention blocks or reduces a bad event; detection finds or reports that it happened. |
Do not memorize terms in isolation. For each term, write one scenario where it is the best answer, one scenario where it is a distractor, and one signal that proves it worked.