Automation & Programmability — Question Bank
Thirty-six questions covering CCNA Domain 6.0 (Automation and Programmability, 10% of the exam): the impact of automation, traditional versus controller-based networking, SDN planes and APIs, REST and CRUD, configuration management tools, JSON data, and Cisco DNA Center / Catalyst Center. Explanations follow every answer.
- Each part is a separate self-scoring quiz; work them in order.
- Learn the vocabulary precisely — northbound vs southbound is a classic trap.
- Read each explanation and note the near-miss terms.
- Your answers are saved locally on this device.
Part 1 — Automation impact & planes
-
Which is a major benefit of network automation over manual configuration?
- It removes the need for network engineers.
- It reduces human error and applies consistent configuration at scale.
- It eliminates the need for authentication.
- It guarantees zero downtime.
Automation improves consistency, speed, and repeatability and reduces typo-driven outages. It changes the engineer's role rather than removing it, and does not remove security requirements.
-
Which plane is responsible for forwarding packets based on the information in the device's tables?
- Management plane
- Control plane
- Data plane
- Service plane
The data plane (forwarding plane) moves the actual user traffic. The control plane builds the routing/forwarding information, and the management plane is for administration (SSH, SNMP, HTTPS).
-
Which plane runs protocols such as OSPF and STP that decide the path?
- Control plane
- Data plane
- Management plane
- User plane
The control plane exchanges routing and topology information and programs the data plane tables. Separating the planes is fundamental to SDN.
-
Which plane would SSH, SNMP, and syslog belong to?
- Data plane
- Control plane
- Forwarding plane
- Management plane
Management-plane protocols are used to administer and monitor the device: SSH and HTTPS for access, SNMP for polling/traps, and syslog for logging.
-
Which statement best contrasts a traditional device-centric model with a controller-based model?
- Both require every device to be configured individually.
- Traditional management configures each device separately; a controller centralises policy and pushes it to devices.
- Controller-based networking removes the data plane from devices.
- Traditional networking has no control plane.
In the controller-based model, the controller holds the network-wide policy and communicates with devices via southbound APIs, reducing per-device configuration drift.
-
Which is a risk or challenge of network automation?
- Configurations can never be versioned.
- It always reduces security.
- A flawed change can be rolled out to many devices rapidly, so testing and review matter.
- It works only with a single vendor.
Automation amplifies both good and bad changes: an error applied to hundreds of devices at once is costly. Testing, staged rollout, and version control mitigate the risk.
-
What does "infrastructure as code" mean?
- Describing desired network state in machine-readable files that tools apply and version.
- Writing physical cabling diagrams.
- Compiling the router operating system.
- Replacing all devices with servers.
Infrastructure as code treats configuration and topology as version-controlled text (YAML, JSON, playbooks), so changes are reviewable, testable, and reproducible.
Part 2 — SDN & controller-based networking
-
In SDN, what is a northbound API?
- The interface between the controller and the network devices.
- The interface between the controller and the applications/automation tools.
- A physical cable direction.
- The routing protocol between devices.
Northbound APIs expose the controller's capabilities to applications and scripts above it (for example, REST). Southbound APIs talk down to the devices.
-
Which protocol is a well-known southbound API used to program SDN devices?
- REST
- JSON
- OpenFlow
- HTML
OpenFlow is a classic southbound protocol that lets a controller install flow entries directly into device forwarding tables. REST is generally a northbound (or device) API style.
-
What distinguishes a controller-based (SDN) architecture's control plane?
- It may be centralised in the controller, with devices focused on forwarding.
- It is removed entirely from the network.
- It runs only on management workstations.
- It is always physical.
SDN centralises the control plane logic in a controller, which programs the data plane of distributed devices. Some designs are hybrid, keeping local control logic as a fallback.
-
Which is a benefit of a centralised controller in an SDN design?
- It removes the need for any configuration.
- It eliminates the data plane.
- It guarantees unlimited bandwidth.
- It gives a network-wide view for consistent policy and easier automation.
A single controller (or cluster) has visibility of the whole network, so policy can be expressed once and applied consistently. It also becomes a potential single point of failure, hence clustering.
-
What is an overlay network in SDN?
- The physical cabling under the floor.
- A logical topology built in software tunnels over an existing physical underlay.
- A wireless-only design.
- A routing protocol.
Overlay networks (VXLAN, GRE) create logical connectivity by tunneling across an underlay that just provides IP reachability, decoupling policy from physical layout.
-
Which capability is enabled by separating intent from implementation in a controller?
- Devices can run without power.
- ACLs become unnecessary.
- The same policy intent can be translated to many device types and vendors.
- Routing tables are encrypted automatically.
Because the controller holds the intent and translates it southbound, the operator can express a goal once and have it realised across a heterogeneous fleet.
Part 3 — REST APIs & CRUD
-
Which HTTP method is used to retrieve data in a REST API?
- POST
- GET
- DELETE
- PUT
GET reads a resource. POST creates, PUT/PATCH updates, and DELETE removes. Together these are the CRUD operations (Create, Read, Update, Delete).
-
Which HTTP method should create a new resource?
- GET
- DELETE
- HEAD
- POST
POST creates; PUT typically replaces/updates. GET only reads. CRUD maps to Create=POST, Read=GET, Update=PUT/PATCH, Delete=DELETE.
-
What does an HTTP 200 status code indicate?
- A client error
- A server error
- Success
- A redirect
2xx codes mean success (200 OK, 201 Created). 4xx are client errors (400, 401, 404) and 5xx are server errors (500).
-
Which status code means the requested resource was not found?
- 404
- 200
- 500
- 301
404 Not Found is a client error meaning the URI does not exist. 401 is unauthorised (authentication needed) and 500 is an internal server error.
-
Which statement about REST is correct?
- REST is a transport protocol on port 22.
- REST is an architectural style using HTTP methods and usually JSON, and is stateless.
- REST requires SOAP envelopes.
- REST cannot use TLS.
RESTful APIs are stateless and use standard HTTP methods and URIs, commonly exchanging JSON. SOAP is a different, heavier style that uses XML envelopes.
-
In a REST URL such as https://dnac.example.com/dna/intent/api/v1/network-device, what does the path identify?
- The encryption key
- The administrator's password
- The TCP window size
- The resource being requested (the network devices collection)
REST URIs identify resources. Here the path points to the v1 network-device collection endpoint on the controller.
-
Which pair correctly matches Update and Delete to HTTP methods?
- PUT (update), DELETE (delete)
- GET (update), POST (delete)
- PATCH (delete), DELETE (update)
- POST (update), GET (delete)
PUT (or PATCH for partial updates) updates a resource; DELETE removes it. GET reads and POST creates.
Part 4 — Configuration management tools
-
Which configuration management tool is agentless and typically uses SSH?
- Puppet
- Chef
- Ansible
- OpenFlow
Ansible is agentless: it connects over SSH (or an API) and pushes changes from a control node. Puppet and Chef rely on agents installed on managed nodes.
-
Which tools are agent-based, requiring software on each managed device?
- Ansible and Terraform
- Puppet and Chef
- REST and JSON
- SNMP and syslog
Puppet and Chef install an agent that pulls configuration and reports back. Ansible, by contrast, needs no agent on the managed device.
-
In Ansible, what is a playbook?
- A YAML file describing a set of tasks to run against hosts.
- A compiled C program.
- A physical rack diagram.
- A JSON web token.
Ansible playbooks are YAML documents listing ordered tasks (playbooks contain plays, plays contain tasks). They express desired state declaratively.
-
Which best describes a declarative configuration tool?
- It requires you to list every command in order.
- It cannot check current state.
- You describe the desired end state and the tool works out how to reach it.
- It only works on routers.
Declarative tools (Puppet, Chef, Ansible) compare current and desired state and converge. Imperative tools require an explicit ordered procedure.
-
What is idempotence in the context of configuration management?
- Running the same job twice produces two changes.
- Running the same job repeatedly gives the same result without unintended extra changes.
- The tool must reload the device.
- Changes cannot be rolled back.
Idempotent operations are safe to repeat: if the state already matches the goal, nothing changes. This is what makes repeated automation runs safe.
-
Which is a benefit of using a version-control system with configuration files?
- It encrypts all traffic automatically.
- It replaces the need for testing.
- It removes the need for credentials.
- It records who changed what and when, and supports review and rollback.
Version control (Git) provides history, diffs, peer review, and the ability to roll back a bad change — central to safe infrastructure-as-code workflows.
Part 5 — JSON, XML & YAML
-
Which characters delimit a JSON object and a JSON array, respectively?
- Parentheses and square brackets
- Angle brackets and parentheses
- Curly braces and square brackets
- Square brackets and curly braces
A JSON object is a set of key/value pairs wrapped in { } (unordered), and an array is an ordered list wrapped in [ ].
-
In JSON, which is a correct key/value pair?
- "hostname": "R1"
- hostname = R1
- hostname: R1
- <hostname>R1</hostname>
JSON pairs use a quoted string key, a colon, and a value (“hostname”: “R1”). XML uses tags, and YAML uses key: value without quotes or braces.
-
Which data format uses indentation and key: value pairs and is common for Ansible playbooks?
- JSON
- YAML
- XML
- CSV
YAML is human-friendly: indentation defines structure and simple key: value pairs are the norm. It is a superset of JSON in practice for many structures.
-
Which format uses opening and closing tags such as <name>R1</name>?
- JSON
- YAML
- CSV
- XML
XML marks up data with tags. A SOAP API typically exchanges XML, while RESTful APIs tend to use JSON.
-
What is a JSON array of two hostnames?
- ["R1", "R2"]
- {"R1", "R2"}
- (R1, R2)
- R1; R2
An array is an ordered list in square brackets: ["R1", "R2"]. Curly braces would make an object, which needs key/value pairs.
-
Which pair of characters begins and ends every JSON array element list consistently?
- { and }
- < and >
- [ and ]
- / and \
Square brackets [ ] delimit arrays; curly braces { } delimit objects. Mixing them changes the meaning of the data.
Part 6 — DNA Center / Catalyst Center
-
What is Cisco DNA Center (now Cisco Catalyst Center) primarily?
- A routing protocol
- A controller and management platform for intent-based networking
- A type of Ethernet cable
- A wireless encryption standard
Catalyst Center (formerly DNA Center) is Cisco's controller for campus and enterprise networks: it provisions, monitors, and assures intent across devices.
-
Which interface does DNA Center expose for automation via scripts and third-party tools?
- A console cable only
- A proprietary serial bus
- A northbound REST API
- A syslog server
DNA Center's northbound REST API (often called Intent API) lets automation tools and applications read state and push intent programmatically.
-
What is intent-based networking?
- Expressing business intent as policy, then having the system translate and enforce it across the network.
- Configuring one device at a time.
- Using only physical controls.
- Disabling all automation.
Intent-based networking captures the desired outcome (for example, "guest users get Internet only"), translates it to device configuration, and verifies it continuously.
-
Which SDN controller category does DNA Center represent?
- A pure data-plane device
- A routing protocol daemon
- A physical patch panel
- A controller providing network-wide (often called fabric) automation and assurance
DNA Center is a controller-based platform that provisions and assures the network, separating intent (northbound) from device configuration (southbound).
-
How do APIs and controllers typically improve change management?
- They remove the need for authentication.
- They make changes programmatic, repeatable, and auditable rather than ad hoc.
- They prevent all configuration changes.
- They guarantee no outages regardless of errors.
Programmatic changes are version-control friendly and repeatable, so they can be reviewed and rolled back. They still require testing and sound design.
Missed-question review map
| Part | Topic | Where it is covered |
|---|---|---|
| Part 1 | Automation impact, planes, infrastructure as code | Week 12 · Automation & Programmability |
| Part 2 | SDN, northbound/southbound, OpenFlow, overlay | Week 12 · Automation & Programmability |
| Part 3 | REST, CRUD, HTTP verbs and status codes | Week 12 · Automation & Programmability |
| Part 4 | Ansible, Puppet, Chef, idempotence, version control | Week 12 · Automation & Programmability |
| Part 5 | JSON, XML, YAML syntax | Week 12 · Automation & Programmability |
| Part 6 | DNA Center / Catalyst Center, intent-based networking | Week 12 · Automation & Programmability |
Sources & references
- Cisco. CCNA (200-301) Exam Topics, Domain 6.0 Automation and Programmability. cisco.com.
- Fielding, R. Architectural Styles and the Design of Network-based Software Architectures (REST dissertation, 2000). ics.uci.edu.
- McKeown, N. et al. OpenFlow: Enabling Innovation in Campus Networks (2008). opennetworking.org.
- IETF. RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format (2017). rfc-editor.org/rfc/rfc8259.
- Ansible. Ansible Documentation. docs.ansible.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.