When Cisco changes the CCNA exam, a new objective document does not mean every networking principle has been replaced. A useful update guide identifies the actual changed statements, their effective dates and what remains transferable. Without that distinction, a candidate can waste weeks repeating subnetting and switching lessons while missing one new automation topic—or accidentally study a future blueprint as if it already governed today’s examination.
The history of Cisco CCNA 200-301 involves three separate events: the major Cisco certification program consolidation in February 2020, the targeted v1.1 objective revision on August 20, 2024, and the announced v2.0 examination beginning February 3, 2027. As of October 26, 2026, **v1.1 is still the current test**, with its final testing day scheduled for February 2, 2027. This article explains the differences without inventing a retirement that has not yet occurred.
2020: CCNA 200-301 becomes the consolidated associate exam
Before the 2020 certification overhaul, Cisco offered multiple associate-level pathways and exam combinations, including older CCNA Routing and Switching options. Cisco’s retired-exams register lists 100-105 ICND1, 200-105 ICND2 and 200-125 CCNA as retired on February 23, 2020, with 200-301 identified as the replacement route for the associated networking certification path.
The new 200-301 structure broadened the general associate foundation around networking, security and automation. A person reading older training that requires an ICND1/ICND2 pair must recognize that as historical context, not an alternate current registration procedure. A certification or study route that was valid under the 2019 program should not be presented as a choice for a new 2026 test booking.
Some older engineering concepts remain useful, including IPv4 addressing, VLANs and route selection. That does not make their exam codes current. Historical Cisco credential pages and course editions are useful for understanding how the program evolved; the official currently scheduled exam decides what a new candidate needs to prepare.
2024: v1.1 changes selected statements, not the entire exam
Cisco introduced the 200-301 CCNA v1.1 update on August 20, 2024. Its official release notes characterize it as a minor update, intended to align the exam with evolving technologies while minimizing disruption to preparation. Cisco explained that the targeted changes represented approximately ten percent of the updated examination content.
The v1.1 weighting still puts IP Connectivity at one quarter of the blueprint, with Network Fundamentals and Network Access each taking one fifth. Security Fundamentals remains fifteen percent; IP Services and Automation and Programmability each represent ten percent. These domain proportions do not imply that individual examination questions remained identical across the revision. A candidate using older material should compare the exact affected objective statements, not rely on a broad percentage as a shortcut.
The phrase “ten percent” describes the limited scope of the refresh according to Cisco, not a promise about how a particular sitting allocates questions. A learner should still maintain full domain coverage and verify whether the training resource maps to v1.1’s actual wording.
Rapid PVST+ safeguards become explicit v1.1 objectives
One documented difference is in Network Access objective 2.5, which concerns interpreting basic Rapid PVST+ Spanning Tree behavior. The v1.0 list covered root roles, port roles and states, and PortFast; the v1.1 release notes added root guard, loop guard, BPDU filter and BPDU guard as explicitly named interpretation topics.
These features are not interchangeable protections. BPDU guard can protect an edge port by reacting to unexpected BPDUs. Root guard helps prevent certain downstream devices from becoming the spanning-tree root. Loop guard addresses loss of expected BPDU information under supported conditions, while BPDU filter can affect BPDU transmission or processing and should not be treated as a universal safety setting.
The exam verb is important. Cisco says candidates should *interpret* basic Rapid PVST+ operations for the listed features, not infer that every complex spanning-tree implementation is now within associate exam scope. In an authorized lab, examine a root bridge and a port-state change under a controlled condition. Use the observation to explain why an edge safeguard applies—or why applying the wrong one would be dangerous.
This is a good example of focused study: review the relevant protocol purpose and behavior, rather than rebuilding an entire enterprise switching course because one objective acquired additional subpoints.
Device management now includes cloud-managed access
The 2024 change to objective 2.8 broadened language previously focused on access-point and wireless LAN controller management. The v1.1 wording describes network device management access and includes cloud-managed approaches alongside console, Telnet, SSH, HTTP/HTTPS and TACACS+/RADIUS-related concepts.
The broader wording matters because management may be performed locally, through remote protocols or under cloud/controller administration. Each approach has different connectivity and credential assumptions. A management session is not the same as ordinary application forwarding; the network should restrict who can make infrastructure changes and how those actions are authenticated.
Do not treat the addition of “cloud managed” as a requirement to design an entire multi-vendor management platform. Explain the management paths and constraints at the level requested by the exam. The learner should know why insecure remote administration is an inappropriate default even when a device technically supports it.
Automation updates include AI, REST authentication and Terraform
Cisco replaced the old objective comparing traditional campus management with Cisco DNA Center-enabled management with a new task: explain generative and predictive AI and machine learning in network operations. The update reflects how AI can help analyze telemetry, recognize patterns and suggest remediation, without making a generated suggestion an authoritative network configuration.
This remains a conceptual associate-level objective. Cisco’s own explanation emphasizes the verb *explain*: candidates should understand the functions and limits of AI/ML in networking, not assume they must train a production machine-learning model or automatically accept unverified route changes.
The REST API objective retained concepts such as CRUD operations, HTTP verbs and data encoding, and explicitly added authentication types. That asks candidates to understand how an API client presents authority and how a response is interpreted, not merely memorize that GET is used for reading. A successful API request does not prove that the resulting network state matches the design.
The configuration-management objective changed examples from Puppet, Chef and Ansible toward Ansible and Terraform. The point is to recognize their capabilities and how they relate to repeatable management. A comparison of Ansible and Terraform is valuable when tied to actual intended and effective configuration, not as a list of competing product names.
Important core skills did not suddenly become new
Subnetting, physical media, switching, VLANs, trunks, routing tables, static routes, single-area OSPFv2, DHCP/DNS, NAT, ACLs, device access and wireless foundations were already central to CCNA preparation. A training provider can refresh examples while retaining sound explanations of those mechanisms. Calling every familiar topic a revolutionary addition misrepresents the release.
For example, the host’s route decision still depends on destination addressing and its configured local prefix. IPv4 subnetting remains necessary when a host must decide whether to resolve a local neighbor or forward toward a gateway. No AI update changes the need for correct prefix calculations and next-hop logic.
The same goes for evidence. A trunk can omit a required VLAN, a route can point to an unusable next hop, and DNS can produce a wrong address. An automation platform or AI tool may help identify the discrepancy, but the network still forwards according to actual interface, route and security state.
When updating a course, retain modules that accurately teach these properties, repair obsolete commands or product assumptions and add targeted coverage for the changed 2024 objectives. A v1.0 chapter that explains a correct route-selection rule can remain useful; a chapter that claims current testing excludes Terraform or cloud management needs revision.
2026 announcement: v2.0 is published but not yet active
In May 2026 Cisco announced another CCNA refresh and published its new exam topics. The v2.0 test launches February 3, 2027; the current v1.1 examination remains available through February 2. The code 200-301 continues, but the version and skill outline are material. A candidate should not infer that a new PDF automatically changed the objectives being assessed today.
The announced v2.0 outline groups skills into five domains instead of v1.1’s six and increases focus on practical troubleshooting, management and AI-driven network operations. That future structure is relevant for someone planning a 2027 sitting; it does not make v1.1’s existing 20/20/25/10/15/10 domain allocation incorrect for an October 2026 exam.
Likewise, a training product branded “CCNA 2.1” may describe the provider’s course or learning-path revision rather than the numbered certification exam version. Separate training edition, exam code and official exam version in your notes so a product’s version label is not mistaken for a change in testing eligibility.
Cisco states that fundamental networking skills carry forward. Someone well into v1.1 preparation does not need to discard all work automatically. What changes for a future sitting is which official topic descriptions and practical depths must be assessed before booking.
Translate the history into a current study decision
Write the planned test date first. For a sitting on or before February 2, 2027, prepare against the current v1.1 six-domain list and its targeted 2024 updates. For a sitting on or after February 3, use the announced v2.0 topic document and confirm current testing details with Cisco. The date determines which objectives apply; an old article’s publication date does not.
Do a source-level comparison. Keep a module if it accurately teaches a shared core skill. Update it if the protocol remains relevant but the objective or supported management method has changed. Replace it if a retired exam code, obsolete procedure or false eligibility claim would mislead a new candidate. Test revised instruction in an authorized lab before treating it as production-ready.
The separate current v1.1 blueprint defines what Cisco measures now, while this historical article explains why earlier materials contain different claims and how to reconcile them. They serve different search intents and should not be merged by merely appending a generic “updated for 2026” label.
A sound understanding of CCNA changes starts with exact dates, actual objective differences and the underlying network properties that remain valid. The goal is neither to dismiss an old source automatically nor to keep using it unchanged. It is to study the exam Cisco actually offers while preserving the durable networking knowledge that survives a version change.