A study plan for Cisco’s CCNA exam must identify which version is actually being tested. As of October 13, 2026, Cisco is administering 200-301 CCNA v1.1. The 200-301 code will remain, but the substantially revised v2.0 examination starts February 3, 2027, after the last v1.1 testing day on February 2. Candidates studying in late 2026 should not confuse an already published future blueprint with the live exam. This distinction matters because v2.0 reorganizes domains and expects more hands-on diagnostics.
Use Cisco’s official current v1.1 exam topics as the source of truth, then convert its objectives into observable network tasks. A course playlist or practice-question count is not a substitute for doing the configurations or interpreting device output.
Separate the live CCNA v1.1 blueprint from the 2027 version
The six domains of the current 200-301 v1.1 exam are Network Fundamentals (20%), Network Access (20%), IP Connectivity (25%), IP Services (10%), Security Fundamentals (15%), and Automation and Programmability (10%). The percentages describe the relative exam weighting, not a requirement to study exactly the same number of hours per domain. IP Connectivity is the largest, but a learner weak at subnetting may first need foundational repair before routing labs make sense.
Cisco has already published the v2.0 exam topics. Those topics are useful for long-range planning; they are not yet the October 2026 exam. The replacement emphasizes troubleshooting and practical verification, but it would be misleading to import its new agentic-AI and diagnostic objectives wholesale into a v1.1 checklist. If your test appointment crosses the February 2027 cutover, rebuild your objective map against the version you will actually sit.
The live v1.1 Cisco PDF contains 53 top-level numbered objectives (1.1 through 6.7) plus lettered sub-objectives. Check the lettered items too. A headline like “configure and verify VLANs” hides the different requirements of access/voice ports, inter-VLAN reachability and native VLAN behavior. The distinction between “describe,” “interpret,” “configure,” and “verify” should govern the depth of the corresponding practice.
Build foundational skills before trusting routing answers
The first domain expects candidates to explain routers, switches, access points, controllers, endpoints, next-generation firewalls, power over Ethernet and familiar network topologies. It also expects practical IPv4 subnetting and IPv6 addressing. Do not begin by memorizing OSPF configuration lines if you cannot determine a host’s network address, mask and next hop. Subnetting without guesswork is a valuable early checkpoint.
A productive paper drill is to take 192.0.2.138/27 and calculate the network (192.0.2.128), last host (192.0.2.158) and broadcast (192.0.2.159). Then decide whether another address is on-link or must go through a default gateway. Follow with one IPv6 /64 configuration, a link-local next-hop question and an explanation of why a router advertisement differs from DHCPv4.
For the physical layer, recognize the difference between single-mode and multimode fiber, copper media, negotiated speed and duplex. A green link LED does not prove there are no receive errors. Knowing how a switch learns a source MAC address is often more useful than memorizing a list of product models. Validate knowledge with packet paths: where does an unknown unicast flood, and when does a routed packet receive a new Ethernet header?
Practice Network Access as configurations and failure cases
On switches, the correct configuration depends on where the setting applies. An endpoint-facing access port uses an access VLAN; an interswitch trunk carries tagged VLANs and may have a native VLAN, while the routed gateway belongs on an SVI or suitable router interface. A two-switch test of VLANs, trunks and native VLAN behavior should confirm that access and trunk membership yield the intended reachability without confusing Layer 2 transport with the Layer 3 gateway.
Build a two-switch lab with at least two VLANs and one 802.1Q trunk. Verify that the selected VLANs traverse the trunk and that a deliberate native-VLAN mismatch produces the symptoms you expect. Then configure a Layer 2 EtherChannel using LACP and check why changing one member’s trunk attributes can prevent bundling. Use show interfaces trunk, show etherchannel summary and show vlan brief as observation points, not incantations.
Rapid PVST+, PortFast and BPDU Guard deserve separate study. Practice recognizing the root bridge and blocking/discarding roles before editing priorities or guard options. For wireless, understand access-point modes, controllers, SSIDs, RF interference and a WPA2-PSK WLAN, but do not assume every controller firmware uses the same GUI labels.
Interpret IP Connectivity without confusing preference mechanisms
The routing-table question often contains several plausible routes. Longest prefix match determines which installed route matches a packet destination most specifically. Administrative distance determines preference among routes to a given prefix learned from different sources; the metric compares routes within a particular routing protocol. Reversing that order leads to incorrect forwarding decisions.
For example, a router with 10.40.0.0/16 learned by OSPF and a static 10.40.8.0/24 forwards traffic for 10.40.8.30 using the installed /24 route, regardless of the broader OSPF route’s metric. Practice distinguishing a default route, host route, network route and floating backup. A floating static route becomes active when its preferred alternative disappears; understanding static routes and administrative distance helps predict that failover without confusing prefix length with route preference.
For single-area OSPFv2, confirm the router ID, hello/dead compatibility, interface network type, subnet and area, and DR/BDR role on broadcast segments. A neighbor stuck short of FULL may indicate adjacency issues rather than a broken static route. A working OSPF adjacency does not guarantee that the desired route has been installed or that the remote host allows the traffic.
Treat IP Services as operational dependencies
The 10% services domain includes NAT, NTP, DHCP, DNS, SNMP, syslog, QoS, SSH and file-transfer roles. These are not interchangeable services. DHCP relay forwards client discovery toward a remote server; DNS converts names to records; NTP makes event timestamps useful; syslog exports event messages; SNMP reads device state; QoS changes treatment of congested traffic. A single scenario may include several dependencies, but diagnose each layer separately.
A workable troubleshooting drill is “a client has an IP address but cannot load an application by name.” First inspect the assigned address, gateway and resolver. Compare a ping to the gateway, an IP-based reachability test and a DNS query. If the host has no address, check DHCP scope, VLAN path and relay instead of beginning with DNS. If the application uses TCP, an open ping path does not prove the destination port is reachable.
Configure a basic inside-source NAT scenario using static translation or a small dynamic pool and verify with an inside-to-outside flow and translation state. Do not infer that NAT is a replacement for an access-control policy: an address rewrite and an authorization decision solve different problems.
Give security controls their correct scope
The security domain mixes fundamental definitions, access control, password policy, IPsec VPN concepts, ACLs, Layer 2 safeguards, AAA and Wi-Fi security. Candidates must not assume a technology is secure merely because its name contains “authentication.” Authentication proves identity; authorization decides permitted actions; accounting records use. WPA2-Personal with a preshared key is not the same credential architecture as WPA2-Enterprise with 802.1X and a RADIUS service.
In a small switch lab, configure one access port with PortFast and BPDU Guard, understand how a DHCP snooping trust boundary works, and explain why Dynamic ARP Inspection depends on validated bindings or approved exceptions. For router filtering, compare standard and extended IPv4 ACLs and the importance of first-match order, implicit deny and interface direction. Keep the existing ACL comparison handy during packet-path practice.
On device management, learn to distinguish SSH remote-access protection from TACACS+/RADIUS policy. Remote access to a production network device should never depend on exposing an unauthenticated management service. Avoid pretending that every Cisco IOS platform accepts an identical command set; read the platform’s current command-reference help for syntax and feature support.
Understand automation without importing the future agentic-AI domain
CCNA v1.1 includes controller-based architectures, overlay versus underlay, northbound and southbound APIs, REST requests and JSON structures, and recognition of Ansible and Terraform. It also includes generative versus predictive AI and machine learning in network operations. The current exam does not require building an autonomous agent or writing production automation code.
For REST, know the difference between GET (read), POST (create/submit), PATCH (partial change), PUT (replace) and DELETE, but remember that an actual API contract controls the supported method for a specific endpoint. Be able to locate a JSON key in a nested object and distinguish a string from a number, object, array or Boolean. The REST and JSON explanation gives examples to practice reading rather than memorizing.
Treat AI suggestions as hypotheses that need device output and verification. A generated configuration that looks plausible may be wrong for the software image, topology or production security posture. Predictive analytics can surface anomalous trends but also requires a baseline and sound input data.
Use a repeatable twelve-week skills schedule
Weeks 1–2: address planning, physical infrastructure, switch forwarding and host IP verification. Weeks 3–4: VLANs, trunks, EtherChannel, Rapid PVST+ and wireless architecture. Weeks 5–6: static routing, longest-prefix decisions, single-area OSPFv2 and first-hop redundancy concepts. Weeks 7–8: IP services, DHCP relay, NAT, time synchronization and quality of service. Weeks 9–10: security, ACLs, secure administration and Wi-Fi access. Weeks 11–12: automation and the v1.1 AI objective, mixed troubleshooting, remediation of weak tasks and timed practice.
This sequence is a scaffold, not a promise of exam readiness after twelve weeks. Allocate extra time where you cannot demonstrate a skill. At the end of each session, write one observable acceptance test: “I can configure and verify a single-area OSPF neighbor,” “I can predict how a VLAN-mismatched trunk fails,” or “I can identify an incorrect /27 host address.” Review your error log by Cisco objective number and fix recurring decision mistakes, rather than simply repeating more questions.
Re-check the Cisco CCNA certification requirements before booking. The crucial release distinction remains: v1.1 is the live October 2026 exam; v2.0 is already documented but not testable until February 2027. A sound study strategy matches the version you will sit, focuses on observables and builds from packet behavior toward secure automated operations.