CCNA 200-301 v1.1 reference — Automation and Programmability
Automation and controllers
How automation changes network management and how controller-based networking differs from device-by-device management.
Objective 6.1Objective 6.2v1.1 exam target
Loading
Automation replaces per-device, manual, CLI-by-CLI work with programmatic changes: configuration rendered from templates, state verified continuously, rollouts repeatable. The impact on network management is consistency (no snowflake devices), speed, and the ability to treat infrastructure as code — versioned, reviewed, testable.
Traditional versus controller-based networking
| Property | Traditional | Controller-based |
|---|---|---|
| Configuration | Per device, distributed | Central intent pushed to devices |
| Policy | Emergent from individual configs | Declared once, enforced everywhere |
| Source of truth | The running-configs themselves | The controller's model/database |
| Change process | Box-by-box maintenance windows | Orchestrated, validated rollouts |
| Troubleshooting view | Device at a time | Fabric-wide telemetry and assurance |
What automation actually changes
| Area | Before | After |
|---|---|---|
| Config drift | Slow accumulation, invisible | Detected vs the declared model |
| Rollout | Manual, error-prone per device | Template-driven, consistent |
| Rollback | Rebuild from memory/backups | Restore a versioned state |
| Compliance | Periodic audits | Continuous verification |
Related resources
Sources
- Cisco CCNA 200-301 v1.1 Exam Topics (official PDF) — reviewed 2026-11-02
Targets CCNA 200-301 v1.1 objectives. Supplemental blocks are labeled beyond exam scope.