Use this cheat sheet for Cisco Certified DevNet Associate after you understand the basics and need faster API-plus-infrastructure decisions. DevNet questions reward reading the contract: endpoint, method, authentication, payload, response, idempotency, and operational safety.
Read every DevNet question in this order
- Identify the task: API call, automation script, data parsing, platform integration, deployment, or troubleshooting.
- Check the API contract: method, URL, headers, auth, payload, schema, status code, and rate limit.
- Check the data shape: JSON, YAML, XML, dictionary/list, required fields, and types.
- Decide whether the operation is safe to rerun or changes state.
- Add secrets handling, logging, error handling, tests, and rollback where needed.
DevNet answer sequence
Use this when the stem mixes API contract, auth, payload shape, idempotency, or safety.
flowchart TD
S["Scenario"] --> C["Check the API contract"]
C --> D["Check the data shape"]
D --> S2["Decide if it changes state"]
S2 --> H["Add secrets, logging, tests, and rollback"]
API and HTTP map
| Need |
Fast rule |
| retrieve resource |
GET |
| create resource |
POST |
| replace resource |
PUT |
| partially update |
PATCH |
| delete resource |
DELETE |
| success with response |
200-style status |
| created resource |
201-style status |
| client problem |
400-style status |
| authentication/authorization issue |
401/403-style status |
| server problem |
500-style status |
Authentication and secrets
| Scenario |
Better instinct |
| API call fails unauthorized |
check token, scope, expiry, header, and endpoint |
| script stores password |
move to secret manager, environment variable, or approved credential store |
| token has broad access |
reduce scope and rotate according to policy |
| logs contain bearer token |
sanitize logs and rotate exposed token |
| automation runs in CI/CD |
use pipeline secrets and least privilege |
| multiple Cisco platforms |
do not assume identical auth or object model |
Data and Python basics
| Task |
What to check |
| parse JSON |
object versus array, key names, nested structure |
| edit YAML |
indentation and data type correctness |
| loop through devices |
handle empty list, failures, and retries |
| compare intended state |
diff desired versus observed state before changing |
| handle exception |
catch meaningful error and report context |
| write reusable code |
functions, parameters, clear names, and tests |
Automation safety
| Requirement |
Strong answer pattern |
| avoid duplicate changes |
idempotent design and state check before change |
| prevent outage |
test in lab, stage rollout, validate, and rollback |
| manage configuration |
version control, review, template, and source of truth |
| reduce manual CLI |
API/controller/config management path |
| prove result |
check response, device state, logs, and monitoring |
| scale across devices |
inventory, loops, error handling, and rate limits |
| Area |
Exam instinct |
| network controller |
policy, inventory, assurance, automation API |
| collaboration platform |
users, rooms, messages, webhooks, and bot-style integration |
| security platform |
events, policies, findings, and API-driven response |
| compute or data center |
inventory, configuration, lifecycle, and automation interface |
| model-driven programmability |
structured models, telemetry, and config/state separation |
| webhooks |
event-driven callback that needs endpoint security and validation |
CI/CD, containers, and deployment
| Need |
Start with |
| track code |
Git branch, commit, PR, review |
| validate change |
tests, linting, static checks, and pipeline status |
| package app |
container image or deployment artifact |
| deploy safely |
environment, variables, secrets, health check, rollback |
| debug container |
logs, port mapping, environment, image version |
| prevent config drift |
versioned templates and automation run history |
Common traps
| Trap |
Better instinct |
| code change before reading response |
inspect status code, body, headers, and API docs |
| wrong JSON shape |
validate keys, nesting, arrays, and required fields |
| hard-coded secret |
use approved secret handling and rotate if exposed |
| non-idempotent script |
check current state before changing state |
| platform assumptions |
Cisco APIs vary by product and auth model |
| no rollback |
automation must have verification and recovery path |
Final 15-minute review
| If the stem says… |
Start here |
| API failure |
method, URL, auth, status code, payload, schema |
| data parsing |
JSON/YAML shape, fields, type, nesting |
| automation risk |
idempotency, scope, validation, rollback |
| credential issue |
token, scope, expiry, secret storage, logs |
| CI/CD |
Git, tests, artifact, deployment, environment |
| Cisco platform |
controller/API model, object type, auth, event flow |
Practice fit
Use IT Mastery for the exact product route, practice status, spaced review when available, and close-answer explanation practice as coverage expands.
One-line decision rule
DevNet answers should honor the API contract, protect credentials, make automation repeatable, and verify infrastructure state after every change.