Automation at CCNA level is about understanding models and interfaces, not becoming a software engineer. Explain which system holds intent, how it communicates with devices, and how structured data represents the requested state.
What to know and how to practise it
Automation impact and controller-based architecture
Compare manual per-device configuration with controller-led consistency, scale, and feedback. Distinguish overlay, underlay, and fabric roles, and separate control-plane decisions from data-plane forwarding. Know the purpose of northbound and southbound interfaces.
AI and machine learning in network operations
Recognize practical uses such as anomaly detection, classification, forecasting, and operational assistance while retaining human validation. Models can prioritize evidence or suggest action, but their output is not proof that the network state is correct.
REST APIs and JSON
Understand CRUD-style operations, common HTTP verbs, resource URIs, authentication, headers, status codes, and the difference between a request and response. Read JSON objects, arrays, names, and values accurately, including nesting and data types.
Configuration management and infrastructure as code
Recognize the roles of Ansible and Terraform, declarative intent, idempotence, inventory, templates, state, and repeatable change. Focus on why structured automation reduces drift and how verification remains necessary after execution.
Example API interpretation
A controller receives a request to read one interface resource and returns a successful response containing a nested JSON object. Identify the GET operation, the resource URI, the 2xx status, and the field holding operational state before drawing a conclusion.
GET /api/v1/interfaces/1
HTTP 200 OK
{ "interface": { "name": "GigabitEthernet1", "status": "up" } }Readiness checklist
- Compare traditional and controller-based network management.
- Separate overlay, underlay, control plane, and data plane.
- Interpret a simple REST request, response, and status code.
- Read nested JSON objects and arrays without guessing data types.
- Explain idempotence and repeatable configuration management.
Common mistakes to remove
- Treating northbound and southbound as physical compass directions.
- Assuming every successful HTTP response means the intended network state exists.
- Confusing a JSON string containing digits with a numeric value.