Memory hook: Model desired state; authenticate the API; verify the result.
Must remember
Traditional device-by-device administration differs from controller-based management. Controllers expose APIs and coordinate policy; the data plane still forwards traffic. Northbound interfaces connect applications/automation to controllers; southbound interfaces connect control systems to devices. Centralization improves consistency while making controller availability and access critical.
REST-style APIs use resources and HTTP methods: GET reads, POST commonly creates/requests actions, PUT replaces a resource representation, PATCH partially updates and DELETE removes. Read the API's actual semantics. Status families include 2xx success, 4xx client/request issues and 5xx server issues. Authentication, authorization, rate limits and pagination remain part of automation design.
JSON uses objects with string keys, arrays, strings, numbers, booleans and null. Double quotes matter; trailing commas and comments are not valid standard JSON. Data serialization is not executable configuration by itself.
Ansible commonly uses agentless playbooks/modules for configuration tasks. Terraform describes desired resources and keeps state linking them to remote objects. Plans, provider versions, state protection and review matter. Idempotence means repeating an operation with the same desired input should not create unintended additional changes; tool names do not guarantee every task is idempotent.
Predictive AI/ML can detect patterns or forecast demand; generative AI produces new text/configuration based on learned patterns and context. Treat generated commands as proposals: verify syntax, platform version, topology, policy and rollback before execution. Sensitive configurations should not be sent to an unapproved model service.
Automate small, testable changes with input validation, least-privilege credentials, useful logs and post-change verification. A syntactically valid API call can still target the wrong device or tenant.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Consistent intended infrastructure | Versioned Terraform configuration with reviewed plans and protected state. |
| Repeated device configuration tasks | Appropriate configuration-management playbooks and verification. |
| AI suggests a router change | Review against real topology and policy before execution. |
Traps
- Valid JSON does not imply a valid API request.
- An automation success status does not prove the network meets the business requirement.
Active recall
1. What does northbound usually describe?
An interface from a controller toward applications or higher-level orchestration.
2. GET versus PATCH?
GET retrieves; PATCH applies a partial update under the API’s rules.
3. Are comments valid in standard JSON?
No.
4. What does Terraform state connect?
Configured resource addresses with real remote object identities.
5. Why verify AI-generated configuration?
It may be plausible but wrong for the platform, topology, policy or intended behavior.