CCNA v1.1 Changes and the Move to v2.0

Cisco CCNA 200-301 v1.1 remains the active exam in October 2026, but it now sits inside a defined transition window. Cisco will keep the current version available through February 2, 2027 and launch CCNA v2.0 on February 3. That makes v1.1 more than a historical update: candidates need to understand what changed from v1.0, what still matters now, and when it makes sense to shift preparation toward the next blueprint.

The useful news is that v1.1 was never a ground-up rewrite. Cisco described it as a minor update and said the changed material accounted for about 10 percent of the exam. The core CCNA skills remained stable: network fundamentals, switching and access, routing, IP services, security, and automation. The changes mostly modernized examples and introduced topics that better reflect cloud-managed networks, AI-assisted operations, and current automation tools.

What Cisco actually changed in CCNA v1.1

The v1.1 release notes identify a small set of targeted blueprint changes. Rapid PVST+ coverage was expanded to include root guard, loop guard, BPDU filter, and BPDU guard. Device-management access was broadened beyond AP and WLC management to include network devices generally and cloud-managed access. The automation section replaced the old comparison with Cisco DNA Center device management with a requirement to explain generative AI, predictive AI, and machine learning in network operations.

REST API coverage was also refined to include authentication types, while configuration-management examples shifted from Puppet, Chef, and Ansible to Ansible and Terraform. Those edits tell you something important about Cisco’s intent: CCNA remains a networking exam, but the environment surrounding network operations has changed. The current 200-301 CCNA exam therefore rewards candidates who can connect traditional infrastructure knowledge with more modern management and automation concepts without losing depth in fundamentals.

Spanning Tree protection became more explicit

Basic Rapid PVST+ knowledge was already part of CCNA, but v1.1 made several protection mechanisms explicit. Root guard helps prevent an unexpected switch from becoming root on a protected port. BPDU guard is commonly associated with edge ports that should not receive BPDUs; receiving one can trigger protective action. Loop guard helps protect against certain failures that could otherwise allow a blocked port to move into forwarding incorrectly. BPDU filter changes whether BPDUs are sent or processed and therefore has to be understood carefully because misuse can undermine loop prevention.

You do not need to turn CCNA into a specialist Spanning Tree course. You do need to understand the problem each mechanism addresses and how that protection fits into Layer 2 switching design. A candidate who understands only the command names but cannot explain the failure condition is not ready for an interpretation-style objective.

Cloud-managed access replaced narrower management wording

Another v1.1 change broadened management access. Instead of focusing narrowly on AP and WLC access methods, the blueprint asks candidates to describe network device management access across Telnet, SSH, HTTP, HTTPS, console, TACACS+/RADIUS, and cloud-managed approaches.

The practical lesson is to distinguish management transport from authentication and from the management platform itself. SSH and HTTPS protect remote management better than clear-text alternatives. AAA systems such as TACACS+ and RADIUS centralize identity and authorization decisions. Cloud-managed platforms move some operational workflows away from direct device sessions, but they do not eliminate the need to understand the device, the network path, or access control.

This shift also prepares candidates for the broader direction of Cisco networking, where controllers, APIs, telemetry, and cloud-delivered management increasingly coexist with direct CLI work.

AI and machine learning entered the blueprint at explanation depth

The most visible v1.1 update is AI. Cisco removed the older objective comparing traditional campus management with Cisco DNA Center and added a requirement to explain generative AI, predictive AI, and machine learning in network operations.

The wording matters. Cisco’s own guidance emphasizes that “explain” does not require the same depth as “configure and verify.” Candidates should understand what these technologies do, the kinds of data they use, and how they can support network operations. Predictive methods can help identify patterns or anticipate conditions; generative systems can assist with summarization, troubleshooting workflows, configuration drafts, and operator interaction. Machine learning provides a broader family of methods that can support classification, anomaly detection, and prediction.

Do not let AI study crowd out routing and switching. Cisco explicitly described the update as limited. The right response is to add a clear conceptual layer, not replace core networking practice with an AI course.

Automation examples now reflect Ansible and Terraform

Version 1.1 also changed the named configuration-management examples. Puppet and Chef were removed from the objective, while Terraform joined Ansible. That aligns the blueprint more closely with tools candidates are likely to encounter in infrastructure automation and declarative provisioning conversations.

The exam does not require you to become an expert automation engineer. You should be able to recognize how configuration-management and infrastructure-as-code mechanisms reduce repetitive manual work, improve consistency, and make change easier to review. Understanding APIs, JSON, controllers, and templates provides the conceptual bridge between traditional CLI administration and network automation.

This is also a useful point of separation between the regular CCNA and Cisco’s newer dedicated Automation track. CCNA asks every network professional to understand automation fundamentals; specialized automation certifications go much further.

What did not change is more important than many candidates think

The most damaging reaction to an exam update is often overcorrection. Candidates see new terms and assume the entire exam has become new. Cisco repeatedly stated that v1.1 preserved the main skills and competencies. You still need IPv4 and IPv6 addressing, VLANs, trunks, EtherChannel, Spanning Tree, routing tables, static routing, OSPF, ACLs, NAT, DHCP, wireless fundamentals, secure management, and basic programmability.

That means solid v1.0 books and labs can still be useful when the subject itself has not changed. The correct approach is to map older material against the current blueprint and supplement the exact gaps. For example, an older chapter on subnetting remains useful; an older automation chapter centered on Puppet and Chef needs updating. A current CCNA preparation should therefore prioritize durable fundamentals first and use the v1.1 release notes as a gap checklist.

How the upcoming v2.0 changes the decision

Cisco has already announced the next major CCNA blueprint. The new version becomes testable on February 3, 2027, immediately after v1.1 closes. Cisco describes v2.0 as the first major CCNA blueprint change since 2019 and says the new design is built around modern network infrastructure, troubleshooting and problem-solving, a security-first mindset, and the role of AI in network management and operations.

The company is also increasing practical validation. Candidates preparing for v2.0 should expect more emphasis on doing and diagnosing, not simply recalling. That direction is consistent with Cisco’s broader certification strategy, which is putting more attention on hands-on skills and AI-ready infrastructure.

If you have already invested heavily in v1.1 and can realistically test before February 3, there is little value in restarting merely to earn a differently versioned CCNA. If you are only beginning and your study horizon extends beyond the transition, v2.0 should become your official map.

Older resources are most useful when you separate timeless networking content from version-specific exam mapping. IPv4 subnetting, Ethernet switching, VLANs, routing tables, OSPF fundamentals, ACL logic, NAT, DHCP, and DNS have not become wrong because the blueprint changed. Keep strong explanations and labs for those topics.

Then tag the areas where older material can mislead. A course that teaches Puppet and Chef as the named configuration-management examples needs a current supplement. A section focused on comparing traditional campus management with DNA Center no longer maps to the v1.1 objective that replaced it. Spanning Tree material that stops at PortFast should be extended with the guard and BPDU-protection concepts. API material should include authentication types rather than only CRUD verbs and data encoding.

This audit is more efficient than discarding everything written before August 2024. It also teaches an important professional habit: engineers routinely work with documentation produced at different times and must distinguish durable protocol knowledge from product- or version-specific detail.

If you plan for v1.1 but later discover that your exam date will fall after February 2, 2027, do not panic and do not restart. Freeze the knowledge you have already mastered, download the v2.0 blueprint, and create a delta list. Mark each objective as already covered, partially covered, or new. Then build labs and review only around the differences.

The same logic works in the opposite direction. If you originally expected to wait for v2.0 but become ready early enough to test on v1.1, make sure you know the active v1.1-specific objectives and do not assume a future blueprint is automatically a valid study map for the current exam.

Version discipline matters because certification questions are tied to a defined scope. Professional networking skill is broader, but exam preparation should always know which blueprint it is serving.

There is also a practical difference between “knowing a topic exists” and studying to the verb Cisco uses. When the blueprint says configure and verify, build a lab and prove the result. When it says interpret, practice reading outputs and explaining state. When it says explain or describe, be able to articulate the concept, its purpose, and a realistic use case. That discipline prevents candidates from spending expert-level time on awareness topics while under-practicing hands-on objectives.

Use the current blueprint as a coverage contract. A video course, book, or lab platform is only a delivery vehicle. If a resource does not show how its lessons map to the active objectives, do that mapping yourself. That single habit is one of the best defenses against studying obsolete content during a transition year.

A transition-proof way to prepare

The safest study plan separates durable knowledge from version-specific deltas. Put most of your effort into packet flow, addressing, subnetting, switching, routing, security, and troubleshooting. Those capabilities survive blueprint changes because they describe how networks work.

Then maintain a smaller “version layer” in your notes. For v1.1, that layer contains the added Spanning Tree protections, cloud-managed access, AI/ML concepts, API authentication awareness, and Ansible/Terraform. If you switch to v2.0, replace that layer with the new blueprint’s explicit changes rather than rebuilding your entire knowledge base.

This approach also keeps the certification in perspective. CCNA is a foundation for broader Cisco paths, including CCNP Enterprise, security, wireless, and automation. Passing the exam matters, but the more durable payoff is becoming comfortable enough with networks that later specialization has something solid to build on.