Overview
Automation and Programmability is 10% of the CCNA and the newest content, revised most in v1.1. It has seven objectives, all at a describe-and-recognize level. It covers how automation impacts network management; comparing traditional networks with controller-based networking; controller-based and software-defined architectures including overlay, underlay, fabric, the separation of control and data planes, and northbound and southbound APIs; generative and predictive AI and machine learning in network operations, newly added in v1.1; the characteristics of REST APIs including authentication types, CRUD, HTTP verbs and data encoding; configuration management with tools such as Ansible and Terraform; and recognizing components of JSON-encoded data.
Nothing here asks you to write code. The exam rewards understanding the concepts: what automation and controllers provide, how software-defined architectures separate planes and use APIs, how REST and JSON work, and where AI fits. Careful reading, not lab hours, answers most of these questions.
How it's tested
CCNA questions in this domain are describe-and-recognize, testing concepts of automation, controllers, APIs and JSON rather than coding. No commands are typed here, so read each description for the concept it names, such as a southbound API or a declarative tool, and match it to the definition.
-
Automation and controllers
A management approach is described, and you compare traditional with controller-based or identify the automation benefit.
-
SDN architecture
An architecture concept is described, and you identify the plane or API direction.
-
APIs and data
An integration or data need is described, and you identify the REST API characteristic or JSON component.
In a software-defined network, a controller must push configuration down to the network devices it manages. The direction matters: communication from applications down to the controller uses northbound APIs, while communication from the controller down to the devices uses southbound APIs. Pushing configuration to the devices therefore uses the southbound API, which is the direction the exam expects for controller-to-device communication.
Domains 7
Official domains from the Cisco outline, in outline order.
6.1 Explain how automation impacts network managementBenefits of automating network tasks.
- What it means
- This covers how automation impacts network management: reducing manual, repetitive configuration, increasing consistency and speed, reducing human error, and enabling scale, compared with traditional manual device-by-device management.
- What to understand
- Automation applies configuration programmatically and consistently across many devices, cutting errors and effort and enabling scale and rapid change. Understanding why organizations automate and what it changes about network management is the conceptual knowledge expected.
- How it shows up
- A management situation is described, and you must identify the automation benefit or impact.
- Common confusion
- Treating automation as only speed, overlooking consistency and reduced error.
6.2 Compare traditional networks with controller-based networkingDevice-by-device versus centralized control.
- What it means
- This covers comparing traditional networks, configured device by device, with controller-based networking, where a central controller manages devices programmatically, and the benefits of centralization.
- What to understand
- In traditional networking each device is configured individually, while controller-based networking centralizes control, so policy and configuration are defined once and pushed out, improving consistency and manageability. Understanding this shift is central to the domain.
- How it shows up
- A management model is described, and you must identify traditional versus controller-based networking.
- Common confusion
- Confusing controller-based networking with simply using management software, rather than centralized programmatic control.
6.3 Describe controller-based, software-defined architecturesOverlay, underlay, fabric, planes, and northbound and southbound APIs.
- What it means
- This covers software-defined architecture concepts: overlay and underlay networks and fabric, the separation of the control plane from the data plane, and northbound APIs (to applications) versus southbound APIs (to devices).
- What to understand
- Software-defined networking separates the control plane (decision-making) from the data plane (forwarding), centralizing control. The underlay is the physical network, the overlay is a virtual network on top, and the fabric is the combined system. Northbound APIs face applications, southbound APIs face devices. These distinctions are frequently tested.
- How it shows up
- An architecture concept is described, and you must identify the plane, overlay/underlay or API direction.
- Common confusion
- Confusing northbound with southbound APIs, or the control plane with the data plane.
6.4 Explain AI and machine learning in network operationsGenerative and predictive AI and machine learning (new in v1.1).
- What it means
- This covers the role of generative and predictive AI and machine learning in network operations, such as predictive analytics, anomaly detection and assistance with operations, added in the v1.1 revision.
- What to understand
- AI and machine learning increasingly support network operations through predictive analytics that anticipate problems, anomaly detection that flags unusual behavior, and generative assistance. Understanding at a conceptual level where AI and machine learning fit in operations is the new v1.1 knowledge expected.
- How it shows up
- An operations scenario is described, and you must identify the AI or machine learning role.
- Common confusion
- Confusing predictive analytics with generative AI, or overlooking this newly added topic.
6.5 Describe characteristics of REST-based APIsAuthentication, CRUD, HTTP verbs and data encoding.
- What it means
- This covers REST API characteristics: authentication types, the CRUD operations (create, read, update, delete) mapped to HTTP verbs (POST, GET, PUT, DELETE), status codes, and data encoding formats such as JSON.
- What to understand
- REST APIs let applications interact with network controllers and devices over HTTP, using verbs for CRUD operations, authentication to secure access, and encoded data (often JSON) in requests and responses. Understanding these characteristics, including which verb maps to which operation, is the expected knowledge.
- How it shows up
- An API interaction is described, and you must identify the REST characteristic, verb or operation.
- Common confusion
- Confusing the HTTP verbs with their CRUD operations, such as which verb reads versus creates.
6.6 Recognize configuration management mechanisms (Ansible and Terraform)Ansible and Terraform.
- What it means
- This covers recognizing configuration management and automation tools, specifically Ansible and Terraform (which replaced Puppet and Chef in v1.1), and their general roles in automating infrastructure and configuration.
- What to understand
- Ansible is an agentless automation tool using YAML to push configuration, and Terraform is a declarative infrastructure-as-code tool. The exam expects recognition of these tools and their general purpose, not deep usage. Knowing that v1.1 features Ansible and Terraform is the current requirement.
- How it shows up
- An automation-tool need is described, and you must recognize Ansible or Terraform.
- Common confusion
- Confusing the roles of the tools, or expecting the retired Puppet and Chef still to be featured.
6.7 Recognize components of JSON-encoded dataJSON structure: objects, arrays, keys and values.
- What it means
- This covers recognizing the components of JSON-encoded data: objects enclosed in braces, arrays in brackets, key-value pairs, and the data types, as used in API requests and responses.
- What to understand
- JSON represents structured data with objects (key-value pairs in braces), arrays (ordered lists in brackets), strings, numbers, booleans and null. The exam asks you to read JSON and recognize its components and structure, not to write it. Being able to parse a JSON snippet correctly is the tested skill.
- How it shows up
- A JSON snippet is shown, and you must recognize its components or interpret its structure.
- Common confusion
- Confusing a JSON object (braces, key-value) with an array (brackets, ordered list).
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Automation benefits
Consistency, speed and reduced error.
- Remember
- More than just speed.
- Tested as
- Automation questions.
- Trap
- Seeing only speed.
-
Controller-based networking
Central programmatic control of devices.
- Remember
- Define once, push out.
- Tested as
- Architecture questions.
- Trap
- Confusing with management software.
-
Control vs. data plane
Decision-making versus forwarding.
- Remember
- SDN separates them.
- Tested as
- SDN questions.
- Trap
- Confusing the planes.
-
Overlay vs. underlay
Virtual network versus physical network.
- Remember
- Fabric is the combined system.
- Tested as
- SDN questions.
- Trap
- Confusing the two.
-
Northbound vs. southbound APIs
To applications versus to devices.
- Remember
- Direction matters.
- Tested as
- API questions.
- Trap
- Confusing the directions.
-
AI and ML in operations
Predictive analytics and anomaly detection.
- Remember
- New in v1.1.
- Tested as
- AI questions.
- Trap
- Overlooking the new topic.
-
REST APIs
HTTP-based interaction, CRUD via verbs.
- Remember
- GET reads, POST creates.
- Tested as
- API questions.
- Trap
- Confusing verbs and operations.
-
CRUD and HTTP verbs
Create, read, update, delete.
- Remember
- Mapped to POST, GET, PUT, DELETE.
- Tested as
- API questions.
- Trap
- Mismatching verb and operation.
-
Ansible and Terraform
Agentless automation and declarative IaC.
- Remember
- Replaced Puppet and Chef in v1.1.
- Tested as
- Automation questions.
- Trap
- Expecting the retired tools.
-
JSON components
Objects, arrays, keys, values.
- Remember
- Braces for objects, brackets for arrays.
- Tested as
- Data questions.
- Trap
- Confusing objects and arrays.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Traditional vs. controller-based networking
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Traditional | Device-by-device configuration | Manual, per-device | Confusing with controller-based |
| Controller-based | Central programmatic control | Define once, push out | Confusing with management software |
Northbound vs. southbound APIs
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Northbound API | Controller to applications | Faces applications | Confusing with southbound |
| Southbound API | Controller to devices | Faces devices | Confusing with northbound |
JSON object vs. array
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Object | Braces, key-value pairs | Unordered named data | Confusing with an array |
| Array | Brackets, ordered list | Ordered values | Confusing with an object |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Southbound to applications
- What candidates pick
- Say applications talk to the controller over the southbound API.
- Why it looks right
- Both are controller APIs.
- Why it's wrong
- Northbound APIs face applications; southbound APIs face the network devices.
Clue to watch for The communication is between applications and the controller versus the controller and devices.
-
GET creates a resource
- What candidates pick
- Use the GET verb to create a new resource via a REST API.
- Why it looks right
- GET is a common verb.
- Why it's wrong
- GET reads data; POST creates a resource. The verbs map to specific CRUD operations.
Clue to watch for The operation is creating versus reading data.
-
Puppet is current
- What candidates pick
- Expect Puppet and Chef to be the featured configuration tools.
- Why it looks right
- They were in older blueprints.
- Why it's wrong
- v1.1 replaced Puppet and Chef with Ansible and Terraform as the featured tools.
Clue to watch for The question reflects the current v1.1 tools.
-
Object is an array
- What candidates pick
- Identify a braces-enclosed key-value structure as a JSON array.
- Why it looks right
- Both hold data.
- Why it's wrong
- A JSON object uses braces with key-value pairs; an array uses brackets with an ordered list.
Clue to watch for The structure uses braces and keys versus brackets and a list.
-
Controller is just software
- What candidates pick
- Equate controller-based networking with running a management application.
- Why it looks right
- Both manage devices.
- Why it's wrong
- Controller-based networking centralizes programmatic control, defining policy once and pushing it to devices, beyond traditional management software.
Clue to watch for The model centralizes control rather than configuring each device.
Answer framework
For any Domain 6 scenario, use these steps to find the answer CCNA expects.
- Recognize that this domain is conceptual, so reading carefully matters more than lab time.
- For automation and controllers, identify the benefits (consistency, speed, fewer errors) and distinguish traditional from controller-based networking.
- For architecture, separate the control plane from the data plane, the overlay from the underlay, and northbound (applications) from southbound (devices) APIs.
- For APIs and data, map CRUD to the HTTP verbs, recognize REST characteristics, and parse JSON objects and arrays.
- Know the newly added topics: AI and machine learning in operations, and Ansible and Terraform as the featured configuration tools. Where two answers seem to fit, check the API direction: northbound between controller and applications, southbound between controller and devices.
Practice question
Want more like this? The CCNA practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Approach this final domain as conceptual recognition, since nothing here requires writing code and careful reading answers most questions. Start with the automation and architecture concepts: why automation helps (consistency and fewer errors, not just speed), traditional versus controller-based networking, and the software-defined architecture distinctions, especially control versus data plane and northbound versus southbound APIs, which are frequent traps.
Then learn REST API basics, mapping CRUD to HTTP verbs, and practice reading JSON to recognize objects, arrays, keys and values. Make sure to study the v1.1 additions: AI and machine learning in network operations, and Ansible and Terraform as the featured configuration tools (not the retired Puppet and Chef).
Because this is only 10% and conceptual, spaced repetition of the terms is efficient. This is the final domain, so finish with full practice tests across all six, and practice the 120-minute pacing, remembering the heaviest marks are in Domains 1 to 3.
FAQ
How much of the CCNA is Domain 6?
Automation and Programmability is 10% of the exam, the newest content, and the area the v1.1 revision changed most.
What changed in Domain 6 for v1.1?
The old DNA Center management objective was replaced with generative and predictive AI and machine learning in network operations, Terraform replaced Puppet and Chef, and REST API authentication types were added.
What is the difference between northbound and southbound APIs?
Northbound APIs face applications communicating with the SDN controller. Southbound APIs face the network devices, letting the controller push configuration down to them.
What is the difference between the control plane and the data plane?
The control plane makes forwarding decisions, and the data plane forwards the traffic. Software-defined networking separates them, centralizing the control plane in a controller.
How do CRUD operations map to HTTP verbs?
Create maps to POST, read to GET, update to PUT (or PATCH), and delete to DELETE. REST APIs use these verbs to operate on resources.
What are the components of JSON data?
JSON uses objects (key-value pairs enclosed in braces), arrays (ordered lists in brackets), and values that are strings, numbers, booleans or null. The exam asks you to recognize these components, not write JSON.
How does Domain 6 connect to the rest of the exam?
Automation and programmability modernize how the networks built and secured in the other domains are managed, applying controllers, APIs and tools to the infrastructure covered across the exam.
Other Networking certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 6 knowledge
You have covered automation, controller-based and software-defined architectures, APIs and JSON. Test whether you can recognize the right concept under exam conditions.