Cisco CCNA 200-301 v1.1: The Six Tested Skill Domains
Read CCNA v1.1 as six practical skill domains
A useful Cisco CCNA syllabus is more than a list of headings. It distinguishes the network behavior a candidate should explain from the tasks they must configure, verify or interpret. Cisco’s 200-301 exam has carried several versions since the 2020 associate-level redesign. Version 1.1 began testing on August 20, 2024 and remains active as of October 2026 through February 2, 2027. The upcoming v2.0 begins February 3, 2027 under the same code with a reorganized objective list.
The active Cisco CCNA v1.1 topics divide the exam into Network Fundamentals (20%), Network Access (20%), IP Connectivity (25%), IP Services (10%), Security Fundamentals (15%) and Automation and Programmability (10%). IP Connectivity is the largest weighted domain. A 2025-marketed syllabus remains relevant only if it reflects these exact objectives instead of guessing weight changes from the publication year of a course.
Read the verbs and sub-objectives before deciding that a topic is complete. Identifying a cable type is not the same task as verifying an OSPF neighbor. The percentages describe relative emphasis; they are not a promise that every delivery has a fixed question count or identical simulation sequence. Use the syllabus to organize real learning evidence rather than to predict confidential exam items.
Network Fundamentals: interpret the path from media to addresses
Network Fundamentals begins with the purpose of routers, Layer 2 and Layer 3 switches, wireless devices, next-generation firewalls, endpoints and controllers. Candidates need enough understanding to know which part of a traffic path each component controls. Physical-layer topics include copper and fiber interfaces, media characteristics and common error conditions. A learner should recognize that duplex or cable failure can cause symptoms before any IP route is involved.
IPv4 addressing remains essential: classify a prefix, identify a usable range and recognize when a host or gateway has the wrong mask. Subnetting decisions become operational when they affect broadcast boundaries, DHCP scopes and summarizable route plans. IPv6 adds link-local and global addressing and Neighbor Discovery behavior that is not simply an expanded version of ARP.
Wireless concepts include frequency bands, channels, SSIDs and basic access point roles. The exam does not require candidates to become radio engineers, but they should know why coverage, security settings and the wired network all contribute to the client experience. A practical lab can show a correctly associated station with a failed DHCP lease, demonstrating why a network symptom must be traced across layers.
Network Access: verify switching and wireless state
Network Access includes VLANs, trunks, native VLAN behavior, inter-VLAN routing, spanning-tree operation and EtherChannel. These topics interact: a trunk mismatch can break a VLAN path even when the physical link is active, and a blocked spanning-tree port can be expected behavior rather than a hardware fault. Candidates should verify what the switch is actually forwarding instead of assuming a successful configuration command proves the topology works.
Set up two access VLANs, a trunk and a Layer 3 gateway. Test end-to-end connectivity, then remove one VLAN from the allowed list and inspect the effect on specific endpoints. Check root bridge and port roles when redundant links exist. Such lab evidence develops a VLAN and trunking model that transfers beyond one memorized topology.
Controller-based wireless administration also belongs in the domain. Learn the role of lightweight APs, the wireless LAN controller and the basic configuration checks appropriate to the objective. Distinguish RF or authentication failure from an absent client VLAN path. Avoid assuming that one Cisco controller GUI example works identically on every product or software release.
IP Connectivity: the largest tested domain
IP Connectivity has a 25-percent published weight. It covers reading routing tables, distinguishing route sources and interpreting forwarding paths. A candidate should understand longest-prefix match, administrative distance, next-hop reachability and how directly connected, static and dynamically learned routes relate. The underlying task is to explain why traffic uses a route or why the expected route is missing.
Cisco v1.1 explicitly names single-area OSPFv2 for configuration and verification. Candidates should know the effect of area and interface settings, the process of neighbor formation and the meaning of observed OSPF routes. A small two-router lab can intentionally break an adjacency and compare the neighbor and routing table outputs before and after correction. The current v1.1 objective is not a mandate to configure OSPFv3 for IPv6; that distinct task appears in the future v2.0 outline.
Static routes can be practised on both IPv4 and IPv6 networks. Verify that a next hop can be resolved and that a more specific route wins when appropriate. First-hop redundancy also belongs in the conceptual coverage, but the expected depth should follow the actual version’s verbs instead of importing advanced professional-level routing configuration into a foundational CCNA course.
IP Services: diagnose connectivity beyond a ping
IP Services is weighted at 10 percent and covers mechanisms that make routed connectivity useful to applications. NAT, NTP, DHCP, DNS, monitoring, QoS, SSH and file-transfer concepts may appear within the domain’s sub-objectives. A candidate should not confuse reachability at one layer with service availability at another. A client may reach a default gateway yet fail to obtain a lease, or use its IP address successfully while a DNS name fails.
Practise a DHCP relay between two subnets and verify that a client receives the correct gateway and DNS settings. Remove the relay and inspect the failure. Then restore it and deliberately break name resolution to compare the symptoms. Such cases connect routing, addressing and service behavior without turning the subject into an unrelated server-administration tutorial.
NTP synchronizes clocks so logs can be correlated; syslog and SNMP provide different monitoring evidence; QoS distinguishes classification, marking, queuing, policing and shaping concepts. The learner should explain what each mechanism measures or changes and what could be observed when a dependency fails, rather than memorizing a port-number list without context.
Security Fundamentals: apply controls to real traffic
Security Fundamentals carries 15 percent of v1.1. Cisco includes common threats, security program principles, device access, Layer 2 controls, access lists, wireless security and VPN concepts. Practical security questions depend on connecting a control to the traffic or threat it is supposed to influence. A rule is not useful merely because its syntax is accepted.
For an ACL, distinguish source, destination, protocol, match order, placement and implicit deny behavior. Configure a limited policy in a lab, send authorized and unauthorized traffic and inspect counters. For an access switch, practise port security or DHCP snooping in a supported environment and record which ports are trusted. Failure investigation reveals how a protective control can also block legitimate communication when configured incorrectly.
Wireless authentication and encrypted communication are different from IP routing and VLAN segmentation. An associated client can still fail authentication or reachability. Candidates should separate the stages and describe how the chosen security feature fits the network’s policy boundary. That skill is a better measure of understanding than remembering an unsourced list of supposedly common exam scenarios.
Automation and Programmability: read before changing
Automation and Programmability has a 10-percent weight in the v1.1 syllabus. The official tasks include comparing controller-based and traditional network management, understanding REST-based APIs and JSON data, recognizing Ansible and Terraform capabilities, and explaining AI and machine-learning applications in network operations. These are entry-level operational concepts, not a demand to program a large management platform.
A practical task could inspect JSON returned by a controller, find an interface’s administrative state and explain how an HTTP GET differs from a request that changes configuration. REST APIs and network automation make more sense when tied to a familiar device question. The candidate should also discuss credentials, least privilege, failure handling and verification of the resulting state.
Python, YAML, Puppet and Chef can be useful in professional practice, but they are not each named mandatory current v1.1 exam objectives. Do not replace Cisco’s requirements with a favorite automation course. The appropriate CCNA depth is to recognize why a tool or architecture helps and how its behavior affects network operations.
Use a version-specific crosswalk before the 2027 transition
The announced Cisco v2.0 syllabus changes the organization to five domains and adds certain troubleshooting and OSPFv3 tasks. A learner already near readiness for v1.1 may be better served by completing the active test before its last scheduled date. Someone booking after February 3, 2027 should build the plan around v2.0, not copy a v1.1 topic chart into a different version.
Create an objective-to-resource matrix: Cisco code, subject, action verb, where it is covered, and the lab or explanation proving the skill. A video or practice question is only one form of evidence. A configure-and-verify objective should be demonstrated in a supported device environment or clear task simulation. Historical topics can be marked as additional background rather than forced into the active test scope.
Cisco 200-301 preparation questions can support diagnosis of missed concepts as a third-party resource, but they are not Cisco’s official examination or proof that a candidate will pass. Review unfamiliar problems against the active syllabus and validate the mechanisms through labs. A reliable 200-301 syllabus makes those relationships clear while keeping 2020 portfolio history, 2024 v1.1 changes and 2027 v2.0 distinct.
