CCNA v1.1 Blueprint Deep Dive: New Exam Topics for Network Automation & AI
The Cisco Certified Network Associate certification has long served as the foundational credential for networking professionals worldwide, and the release of the CCNA v1.1 blueprint represents the most significant curriculum update in recent years. This revision reflects the profound transformation happening across enterprise networks, where automation tools, programmable infrastructure, and artificial intelligence are reshaping what network engineers actually do on a daily basis. Cisco recognized that teaching only traditional CLI-based network management was producing graduates who were unprepared for the modern network environment, and the v1.1 update directly addresses that gap by expanding coverage of network automation, programmability, and AI-driven operations in ways that were either absent or superficially covered in earlier versions of the exam.
For candidates currently preparing for the CCNA or planning to sit the exam in the coming months, the v1.1 blueprint changes are not cosmetic — they represent a meaningful shift in what the exam expects candidates to know and demonstrate. Understanding which topics have been added, which have been expanded, and how the new automation and AI content connects to the foundational networking knowledge that the CCNA has always required is essential for building a preparation strategy that leads to genuine readiness rather than a narrow focus on legacy content that no longer reflects the full scope of the exam. This article walks through the new blueprint additions in depth, explaining what each topic covers, why it matters in real network environments, and how candidates should approach learning it.
Why Cisco Revised the CCNA Blueprint at This Moment
Cisco does not update major certification blueprints without substantive reasons, and the v1.1 revision reflects a confluence of forces that have been building in the networking industry for several years. The proliferation of software-defined networking, the widespread adoption of cloud infrastructure, and the emergence of intent-based networking platforms like Cisco DNA Center have collectively shifted the day-to-day responsibilities of network engineers away from manual device-by-device configuration toward orchestrated, automated, policy-driven management. Organizations deploying networks at scale simply cannot operate efficiently if every configuration change requires a human logging into each device individually and typing commands — the speed, consistency, and auditability demands of modern infrastructure require automation.
Artificial intelligence and machine learning have entered network operations through tools that analyze telemetry data to detect anomalies, predict failures, optimize traffic distribution, and surface actionable insights that would be invisible to human operators reviewing static dashboards. These capabilities are no longer experimental — they are shipping in production network management platforms and changing the skills that employers need from network engineers. Cisco’s blueprint revision acknowledges this reality by making automation and AI operational knowledge part of the baseline that every CCNA-certified professional is expected to possess, not advanced specialization reserved for senior engineers or those pursuing higher-level certifications.
The Expanded Network Automation Domain and What It Now Covers
The network automation domain in the CCNA v1.1 blueprint has grown substantially in both breadth and depth compared to earlier versions. Candidates are now expected to demonstrate understanding of automation concepts that go beyond simply knowing what automation is — they need to understand the tools, protocols, and architectures that make network automation practical in real environments. This includes familiarity with controller-based networking architectures where a centralized platform manages device configurations and policies across the entire network, as opposed to traditional distributed management where each device is configured independently. The distinction between southbound interfaces that connect controllers to network devices and northbound interfaces that connect controllers to orchestration systems and applications is a conceptual foundation that the updated blueprint tests explicitly.
Specific automation tools and frameworks now appear in the blueprint in ways that require working-level familiarity rather than just definitional awareness. Ansible, the agentless automation platform that uses YAML-based playbooks to define and execute configuration tasks, receives significant coverage because of its widespread adoption in network automation workflows. The CCNA does not expect candidates to write complex Ansible playbooks from scratch, but it does expect them to read a basic playbook and understand what it does, identify the components of an Ansible inventory file, and explain how Ansible’s agentless architecture uses SSH and network device APIs to execute tasks without requiring software installation on managed devices. This working-level familiarity with Ansible reflects its status as effectively the standard automation tool for network engineers entering the profession today.
Python Scripting Fundamentals Now Expected of Network Engineers
One of the most significant changes in the v1.1 blueprint is the explicit inclusion of Python scripting fundamentals as content that CCNA candidates are expected to know. This marks a clear departure from the traditional view of the CCNA as a purely networking credential and signals Cisco’s intention to define modern network engineering as a discipline that incorporates programming skills alongside protocol knowledge. The level of Python knowledge required is foundational rather than advanced — candidates are not expected to build complex software applications — but they are expected to read Python scripts that interact with network devices or APIs and explain what those scripts do, identify basic Python constructs including variables, data types, conditional statements, loops, and functions, and understand how Python libraries relevant to network automation are imported and used.
The practical rationale for this Python requirement is compelling. Network automation scripts written in Python are increasingly common across network operations teams, and engineers who cannot read them are effectively shut out from contributing to or maintaining the automation infrastructure their organizations depend on. Even engineers who will not write Python scripts themselves need to be able to review scripts written by colleagues or vendors, understand what changes a proposed script will make to network devices before approving its execution, and troubleshoot automation failures by reading error output and tracing it back to the relevant portion of a script. The CCNA’s Python requirement is calibrated to produce engineers who are literate in automation code rather than professional developers, which is precisely the right level for an entry-level networking credential.
REST APIs and How Network Devices Expose Programmable Interfaces
The v1.1 blueprint places substantial emphasis on REST APIs as the dominant mechanism through which modern network devices and management platforms expose programmable interfaces to automation tools and applications. Candidates need to understand what a REST API is, how HTTP methods including GET, POST, PUT, PATCH, and DELETE map to read and write operations on network resources, and what HTTP status codes communicate about the success or failure of API requests. The request and response cycle of REST API interactions — sending a request with appropriate authentication headers and a JSON or XML body, receiving a response with a status code and a response body — is content that the exam tests through scenario-based questions requiring candidates to interpret API interactions.
JSON is the data format that dominates modern network API responses, and the blueprint explicitly includes JSON as content candidates must be able to work with. Reading a JSON response from a network device API and identifying the values of specific fields, understanding the hierarchical structure of nested JSON objects and arrays, and recognizing how JSON maps to Python data structures like dictionaries and lists are all within scope. YANG data models, which provide a formal language for describing the structure of data that network devices expose through APIs, appear in the blueprint as foundational knowledge for understanding how model-driven programmability works. NETCONF and RESTCONF, the protocols that use YANG data models to provide standardized programmatic access to network device configuration and operational state, are both explicitly covered and represent the intersection of protocol knowledge and programmability that characterizes the v1.1 update’s broader theme.
Cisco DNA Center as a Network Automation and Management Platform
Cisco DNA Center receives dedicated coverage in the v1.1 blueprint as the flagship example of a controller-based network management platform and the primary context in which the blueprint’s controller and automation concepts are applied. DNA Center is Cisco’s intent-based networking platform that allows network administrators to define network behavior through policies and intents rather than device-by-device configurations. Candidates need to understand what DNA Center does at a functional level — how it discovers and inventories network devices, how it provisions device configurations, how it monitors network health through assurance capabilities, and how it exposes northbound REST APIs that allow external systems to interact with the network through DNA Center rather than directly with individual devices.
The DNA Center API coverage in the blueprint is particularly relevant for automation-focused content. Candidates should understand how to authenticate to the DNA Center API, how to use the API to retrieve device inventory information, how to interpret the JSON responses that DNA Center API calls return, and how automation scripts and orchestration platforms interact with DNA Center to manage network configurations programmatically. This is not purely theoretical content — Cisco’s DevNet sandbox environments provide free access to DNA Center instances where candidates can practice making API calls using tools like Postman or Python scripts, which is a learning approach that the exam community has widely endorsed as effective preparation for the API-related questions in the v1.1 blueprint.
Artificial Intelligence in Network Operations and What It Actually Does
The explicit inclusion of artificial intelligence in the CCNA v1.1 blueprint is one of its most distinctive features and one that requires careful attention to understand what the exam actually expects candidates to know. The AI content in the CCNA is not about machine learning theory, mathematical foundations, or model training — it is about how AI and machine learning capabilities are applied in network operations platforms to improve visibility, reduce troubleshooting time, and enhance network reliability. Candidates need to understand what AI-driven network operations tools do in practical terms: they analyze large volumes of network telemetry data, identify patterns that indicate normal and abnormal behavior, surface anomalies that might indicate problems or security threats, and provide recommendations or automated responses based on learned models of network behavior.
Cisco’s AI Network Analytics, integrated into DNA Center, is the primary example through which the blueprint grounds its AI network operations content. This platform continuously collects telemetry from network devices including wireless access points, switches, and routers, builds models of normal behavior for each network environment, and uses those models to identify deviations that may indicate problems. When a specific location in a campus network shows degraded client connectivity performance, AI Analytics can compare current conditions against historical baselines, identify whether the degradation pattern is consistent with a specific category of known problem, and recommend remediation steps. Candidates should understand this general operational model — telemetry collection, baseline modeling, anomaly detection, and insight surfacing — and be able to explain how it differs from traditional threshold-based monitoring that only alerts when a metric crosses a predefined limit.
Software-Defined Networking Concepts and Architecture Principles
Software-defined networking concepts receive expanded coverage in the v1.1 blueprint, with particular emphasis on the architectural separation between the control plane and the data plane that defines the SDN approach. In traditional networking, both the control plane — which makes decisions about how traffic should be forwarded — and the data plane — which actually forwards packets — run on each individual network device. SDN separates these functions, moving control plane intelligence to a centralized controller that has a network-wide view and programmatically controls the forwarding behavior of data plane devices through southbound interfaces like OpenFlow or vendor-specific protocols. This separation enables network-wide policy enforcement, rapid reconfiguration, and programmable traffic engineering that are difficult or impossible to achieve when control intelligence is distributed across individual devices.
The blueprint’s SDN content extends to specific deployment models that candidates should be able to distinguish. Pure SDN implementations where a centralized controller makes all forwarding decisions represent one end of the spectrum. Hybrid SDN models where controller-based management coexists with traditional distributed routing and switching represent the more common practical reality of most enterprise networks, which typically cannot be fully replaced with SDN infrastructure overnight. Overlay networks that create virtual network topologies on top of physical infrastructure using tunneling protocols — VXLAN being the primary example in the blueprint — are covered as the technology that enables the network virtualization that modern data center and cloud environments depend on. Understanding why overlays exist and how they decouple logical network topology from physical infrastructure is conceptual knowledge that the exam tests in scenario-based questions about data center networking.
Network Telemetry and Streaming Data Collection Methods
Network telemetry is the practice of collecting real-time operational data from network devices and streaming it to analysis and monitoring platforms, and it receives dedicated coverage in the v1.1 blueprint as a foundational enabler of both AI-driven operations and modern network observability. Traditional network monitoring relied primarily on SNMP polling, where a management system periodically requests specific data from network devices at intervals measured in minutes. Streaming telemetry inverts this model — devices continuously push operational data to collection platforms at much higher frequencies, typically measured in seconds, providing near-real-time visibility into network conditions that polling-based approaches cannot match. This distinction between polling-based and streaming telemetry is explicitly tested content in the v1.1 blueprint.
Model-driven telemetry, which uses YANG data models to define the structure of the telemetry data that devices stream, is the modern standard that the blueprint covers in the context of how network automation and AI analytics platforms receive structured operational data from devices. Candidates should understand how model-driven telemetry subscriptions work conceptually — how a management platform subscribes to specific data streams from a device, specifying which YANG paths it wants data from and at what frequency — and how this structured, model-defined data stream enables automation platforms to process and analyze telemetry without custom parsing for each device type. The contrast between the rich, structured, high-frequency data available through model-driven telemetry and the limited, structured, low-frequency data available through SNMP polling explains why modern AI network analytics platforms require streaming telemetry rather than traditional monitoring approaches.
Configuration Management and Infrastructure as Code Concepts
Infrastructure as code is a practice borrowed from software development that treats network device configurations as code artifacts that are version-controlled, tested, and deployed through automated pipelines rather than applied manually by engineers. The v1.1 blueprint includes infrastructure as code concepts because they underpin how modern network automation workflows are organized and managed. When network configurations are defined in code — whether as Ansible playbooks, Python scripts, or declarative configuration templates — they can be stored in version control systems like Git, reviewed through code review processes before deployment, tested in lab environments before production application, and rolled back to previous versions if a change produces unexpected results.
Version control concepts including repositories, commits, branches, and merge operations appear in the blueprint as knowledge that network engineers now need because participating in infrastructure as code workflows requires understanding how Git-based version control works at a basic operational level. Candidates are not expected to be Git experts, but they should understand why version control is valuable for network configurations, what a commit represents in the context of configuration changes, and how branching enables parallel development of configuration changes without interfering with the main production configuration baseline. The broader concept of treating network configurations with the same discipline applied to software code — review, testing, versioning, and controlled deployment — represents a professional maturity that the v1.1 blueprint formally acknowledges as within the CCNA’s scope.
Network Verification and Validation Through Automated Testing
Automated network verification and validation is an emerging practice that the v1.1 blueprint introduces as a complement to traditional manual verification procedures. After making configuration changes to a network, engineers have traditionally verified the results by manually running show commands on affected devices and visually inspecting the output to confirm that routes are present, interfaces are in the expected state, and connectivity tests produce the expected results. Automated verification replaces this manual inspection with scripts and tools that systematically check a predefined set of conditions and report pass or fail results, producing consistent and repeatable verification that does not depend on an engineer remembering to check every relevant condition.
Tools and frameworks for network verification that the blueprint covers include pyATS, Cisco’s Python-based network testing framework, which provides a structured way to connect to network devices, collect operational state data, and compare it against expected values defined in test cases. The concept of a network snapshot — capturing the operational state of a network before and after a change and comparing the two snapshots to identify what changed — is a verification technique that the exam covers as a practical method for confirming that changes had their intended effect without unintended side effects. Candidates should understand why automated verification is valuable — it is faster, more consistent, and more comprehensive than manual verification — and be familiar with the general approach of defining expected network state and programmatically confirming that actual network state matches expectations.
Preparing Effectively for the New Automation and AI Exam Topics
Preparing for the automation and AI content in the v1.1 blueprint requires a different approach than preparing for traditional networking topics because the material is inherently more practical and hands-on than protocol theory. Reading about REST APIs is far less effective preparation than actually making API calls against a network device or management platform and observing the requests and responses. Cisco’s DevNet platform provides free learning resources, sandbox environments, and hands-on labs specifically designed to build the practical automation skills that the CCNA now tests, and candidates who are serious about the automation domains of the exam should spend significant time working through DevNet learning paths alongside their primary CCNA study materials.
For the Python content, working through introductory Python exercises focused on the constructs most relevant to network automation — reading and writing JSON, making HTTP requests using the requests library, iterating over data structures, and handling basic error conditions — is more valuable than a comprehensive general Python course. The Cisco CCNA study guides from publishers including Wendell Odom have been updated to reflect the v1.1 blueprint content, and candidates should confirm that any study materials they use explicitly cover the new automation and AI topics rather than relying on older editions that predate the blueprint revision. Practice exam providers including Boson and MeasureUp have also updated their question banks for v1.1, and working through practice questions specifically tagged to the automation and programmability domains helps calibrate preparation and identify remaining knowledge gaps before the exam date.
Conclusion
The CCNA v1.1 blueprint revision represents a clear and deliberate statement from Cisco about what network engineering means in the current decade. The addition of network automation, Python scripting, REST APIs, AI-driven operations, and infrastructure as code concepts to a foundational certification is not a peripheral update — it is a signal that these capabilities are now considered baseline professional competencies rather than advanced specializations. The network engineers entering the field in the coming years will be expected to operate comfortably in environments where automation handles routine configuration tasks, where AI surfaces operational insights that would be invisible to traditional monitoring, and where network infrastructure is managed through APIs and code rather than exclusively through CLI sessions.
For candidates approaching the CCNA v1.1 for the first time, this expanded scope creates a more demanding preparation challenge but also a more valuable credential. Earning the updated CCNA demonstrates not just that a professional understands how routing protocols and switching work but that they can participate in modern network operations workflows involving automation tools, programmable interfaces, and AI-enhanced management platforms. That combination of foundational networking knowledge and modern operational skills is precisely what employers building and operating contemporary enterprise networks need from entry-level network engineers, and the v1.1 blueprint is calibrated to validate both.
The transition the CCNA v1.1 represents mirrors a broader transition happening across the entire networking profession. The engineers who will thrive in this environment are not those who resist automation as a threat to their relevance but those who embrace it as a multiplier of their effectiveness — who use automation to handle routine tasks more reliably, who use AI-driven analytics to diagnose problems faster, and who apply infrastructure as code practices to manage network configurations with the rigor and discipline that complex, business-critical infrastructure deserves. Building these habits and skills during exam preparation, rather than treating the automation content as a box to check before returning to what feels like real networking, sets the foundation for a career that remains relevant and valuable as the tools and technologies of network engineering continue to evolve.