Inside the Current CCNA 200-301 Blueprint

The CCNA blueprint is more useful when read as a specification of skills than as a list of network product names. Cisco deliberately uses different verbs: describe a technology, interpret an operational state, configure a feature or verify its behavior. Those expectations are not interchangeable. An administrator may be asked to explain why a network-management API exists without building an enterprise controller, while another objective expects the candidate to configure and verify a working static route.

In October 2026, the current exam is Cisco CCNA 200-301 v1.1. Cisco says this version remains available through February 2, 2027; v2.0 begins February 3, 2027. The latter’s revised domain structure should not be presented as the current blueprint. This article interprets the six published v1.1 domains and their weightings using Cisco’s actual objective language. It is distinct from a worked networking lifecycle, a personalized study plan or a prediction about specific examination questions.

The current v1.1 domains and published emphasis

Cisco CCNA 200-301 v1.1 area Weight Representative competency
Network Fundamentals 20% Understand links, devices, addressing, Ethernet and basic wireless or virtualization behavior
Network Access 20% Configure and verify VLANs and interswitch connectivity, interpret switching and wireless operation
IP Connectivity 25% Read routing tables and configure or verify basic static routing and single-area OSPFv2
IP Services 10% Implement or explain services including NAT, NTP, DHCP, DNS, QoS and logging
Security Fundamentals 15% Apply and distinguish device access, ACLs, Layer 2 security and wireless protection
Automation and Programmability 10% Understand controller-based management, APIs, JSON, configuration tooling and introductory AI/ML

These percentages total 100% and describe relative blueprint emphasis, not an exact forecast of the number of questions or a guarantee of a particular exam score. A domain’s weighting does not make it safe to ignore. A failure to understand basic DNS or DHCP may cause confusion in IP Connectivity and Network Access scenarios even though IP Services has a smaller published share.

The six domain headings are official examination organization. A real packet may involve several at once. The objective statements beneath the headings tell you whether Cisco expects recognition, explanation, configuration or interpretation. Build preparation tasks according to those verbs instead of attempting to deploy every technology mentioned in the same way.

Network Fundamentals — 20%: establish what the network is doing

Fundamentals cover the roles of routers, Layer 2 and Layer 3 switches, security devices, access points, controllers, servers, endpoints and Power over Ethernet. The objective list also includes network topologies, physical interfaces, cable types and symptoms such as errors, collisions or speed and duplex mismatches. These concepts tell a candidate where to begin an investigation before any routing protocol is involved.

IP addressing is a major applied foundation. Cisco expects configuration and verification of IPv4 addresses and subnetting, understanding private addressing, and configuration or verification of IPv6 addresses and prefixes. A candidate should explain what the subnet mask or prefix means to the host: does the destination appear local, or should a frame go to the default gateway?

Use IPv4 subnetting with actual test addresses rather than only conversion tables. A correct answer includes network and host ranges and what a client will do when attempting a remote destination. For IPv6, learn address types and neighbor behavior, recognizing that IPv6 is not simply IPv4 with a longer address string.

Also review TCP versus UDP, wireless radio principles, virtualization and switching behavior. The guide includes server virtualization, containers and virtual routing/forwarding at an introductory level. MAC learning and frame flooding are not merely vocabulary: they explain why a switch may forward one known destination differently from an unknown one.

Network Access — 20%: configure and interpret local connectivity

This domain covers VLANs, access ports, voice/data VLAN considerations, 802.1Q trunks, native VLAN behavior and inter-VLAN connectivity. Cisco expects candidates to configure and verify several of these features rather than recognize only their definitions. A switch accepting a VLAN command is not proof that the VLAN can traverse the intended trunk or that the host has a correct default gateway.

Use a two-switch lab with an approved test topology. Verify VLAN membership and the allowed trunk set, then introduce a reversible missing-VLAN fault. Predict which hosts should fail and which should remain operational. The negative observation is part of the skill: a trunk can be working for VLAN 10 while dropping traffic for VLAN 20.

Network Access also includes CDP and LLDP, EtherChannel using LACP, and interpretation of Rapid PVST+ Spanning Tree. Link aggregation and loop prevention solve different problems. A bundle may provide additional aggregate capacity or member-link fault tolerance under supported configurations, but it does not automatically protect against failure of a switch shared by all links.

Wireless infrastructure is represented through Cisco wireless architecture, AP modes, controller connections and interpretation of wireless LAN configuration. A candidate should recognize how WLAN settings, security and physical/controller connectivity affect client access. The objective to interpret a GUI is different from a demand to design an entire enterprise wireless management system.

IP Connectivity — 25%: explain the actual forwarding decision

This is the highest-weighted v1.1 domain. Candidates should interpret routing-table entries: routing protocol codes, prefixes and masks, next hops, administrative distance, metrics and the gateway of last resort. They must explain why a router selects the path it uses, including longest prefix match and subsequent preference rules for comparable routes.

CIDR matters because a more-specific network route can match a destination before a less-specific default path is used. Memorizing one administrative-distance number cannot replace knowing which prefix matches the packet in the first place.

Cisco lists configuring and verifying IPv4 and IPv6 static routes, including network, host, default and floating routes. These can be examined through small topologies and route tables. A configured static route is not necessarily usable if its next hop is unreachable or the remote side lacks the return route.

The v1.1 guide specifically includes configuring and verifying single-area OSPFv2. The candidate should understand neighbor formation, router IDs, point-to-point and broadcast segment behavior, including DR/BDR selection. The existence of an OSPF neighbor does not automatically prove every required prefix is present in the routing table or every application flow is permitted.

First-hop redundancy protocols appear through their purpose, functions and concepts. A candidate should distinguish the availability goal from the separate security, switching and routing conditions a client still needs. The domain is about predicting and verifying IP paths under stated configurations, not designing every advanced enterprise routing feature.

IP Services — 10%: support applications and management

IP Services includes configuring or verifying supported NAT behavior, NTP client/server operation, and DHCP client or relay functions. The guide also covers explaining DHCP and DNS roles, SNMP, syslog facilities and severity levels, QoS concepts and supported remote-access or file-transfer mechanisms.

A host may have a valid route and still fail by name because its resolver does not return an appropriate address. The DNS process answers a naming question, while routing answers where the packet is forwarded. A client with an incorrect DHCP-provided gateway has a different fault from one whose hostname points to the wrong service.

QoS terminology should be understood by its function: classifying, marking, queuing, congestion management, policing or shaping. These mechanisms influence how traffic is handled under competing demands; they do not automatically add bandwidth or repair a broken physical link. Likewise, syslog and SNMP provide observations or management information, not guarantees that the application will behave correctly.

Because this area is only 10%, candidates sometimes skim it. That is unwise when other domains depend on the services it supplies. One controlled exercise showing a DHCP relay, DNS lookup and test application connection can make the distinctions easier to retain.

Security Fundamentals — 15%: enforce and verify boundaries

Cisco tests basic security concepts and operational protection: threats and mitigation, security awareness and physical protection, local device access, password and authentication-policy ideas, VPN concepts, ACLs, Layer 2 protections and wireless security. The objective verbs distinguish what a candidate needs to configure from what they should describe.

A well-designed ACL test includes both a permitted flow and a prohibited flow. If a rule denies an inappropriate management connection but also blocks the legitimate application, the configuration has failed the business requirement. Source address, destination, protocol, direction and ordered match conditions matter.

At the access layer, port security, DHCP snooping and dynamic ARP inspection address different misuse and spoofing conditions. They do not replace application authorization. Wireless protocols including WPA, WPA2 and WPA3 serve access-protection roles, while the v1.1 guide explicitly includes interpreting or configuring specified WLAN behaviors rather than assuming every wireless product feature is tested.

Authentication, authorization and accounting remain distinct. A valid device login proves one identity process succeeded; it does not grant permission to perform every administrative action. Security should be understood as enforceable boundaries with observable denials, not merely a list of threat labels.

Automation and Programmability — 10%: reason about intended state

The current v1.1 guide covers the effect of automation on network management, controller-based architecture, separation of control and data planes, northbound and southbound APIs, REST operations, authentication and data formats. Cisco also expects recognition of JSON and configuration-management mechanisms such as Ansible and Terraform.

A candidate should understand why a controller or automation job can coordinate configuration across devices while forwarding still follows the actual interfaces, VLANs, routes and security state installed in those devices. A successful API call does not prove the intended network traffic now works, and a faulty template can spread errors faster than a single manual change.

The v1.1 refresh added introductory material on generative and predictive AI and machine learning in network operations. The goal is to understand their role and limitations, not assume that generated network recommendations may be applied without validation. One useful exercise compares an intended policy with the resulting device state and explains the rollback if the change is wrong.

Ansible and Terraform are relevant to the distinction between orchestrating changes and describing infrastructure state. The exam’s introductory automation objectives do not replace the need to understand subnetting or route selection.

Control the version boundary before choosing study materials

Cisco launched v1.1 in August 2024 with targeted updates, including topics around AI/ML, cloud-managed device access, REST API authentication and Terraform. As of October 26, 2026, that is still the current six-domain examination. Cisco has published v2.0 objectives, but the new version does not become bookable until February 3, 2027; the current v1.1 exam’s last scheduled test day is February 2.

Do not import v2.0’s new five-domain structure or revised weightings into a v1.1 preparation article and call them current. A candidate planning to sit after the change should consult Cisco’s v2.0 objectives separately. The basic networking skills can carry over, but formal exam versions and objective verbs must be represented accurately.

Use the official v1.1 skills document to sample each group and the relevant tasks beneath it. A candidate should be able to configure and verify the items marked for implementation, interpret actual outputs where required and explain the role of technologies whose objectives are descriptive. The accompanying CCNA verification labs help demonstrate that difference through a permitted, denied and observed network result.

The CCNA blueprint is most useful when it changes what you can prove: a valid host address, correctly carried VLAN, selected route, working service, enforced access policy and understood automation result. Domain percentages guide coverage, while technical evidence shows whether the knowledge transfers to a network the candidate has not already memorized.