200-301 v2.0 — Cisco CCNA (200-301 v2.0) Exam Blueprint

How to Use This Exam Blueprint

This independent Exam Blueprint translates the Cisco CCNA (200-301 v2.0) exam scope into practical readiness tasks. Use it to find weak areas, guide final review, and decide whether you can solve networking problems without relying on memorized answers.

For each topic area, ask:

• Can I explain the concept clearly?
• Can I choose the right technology in a scenario?
• Can I recognize correct Cisco IOS-style configuration and verification output?
• Can I troubleshoot from symptoms, not just from commands?
• Can I eliminate plausible wrong answers under time pressure?

Do not treat this as an exact scoring guide. Exact exam weights, policies, and delivery details should be checked with Cisco. This page is a study blueprint and readiness checklist for exam code 200-301 v2.0.

High-level readiness map

Network fundamentals checklist

Core concepts to review

Can you do this?

• Explain what changes at each hop as a packet moves from one subnet to another.
• Distinguish a MAC address lookup problem from an IP routing problem.
• Identify whether a symptom points to Layer 1, Layer 2, Layer 3, DNS, or application failure.
• Explain why a switch forwards, floods, filters, or drops a frame.
• Describe how ARP supports IPv4 communication on a local network.
• Describe the equivalent neighbor discovery role in IPv6 at a high level.
• Recognize the difference between broadcast, multicast, unicast, and anycast concepts.
• Explain why default gateways matter for inter-subnet communication.
• Interpret common interface states and error counters.
• Identify likely causes of latency, jitter, packet loss, and asymmetric routing.

Addressing, subnetting, and route math

Subnetting is a major readiness divider. You should not merely recognize subnet terms; you should be able to calculate networks, hosts, broadcast addresses, wildcard masks, and summaries quickly.

IPv4 subnetting readiness

Useful formulas:

Subnetting speed checks

IPv6 readiness

Common traps

• Confusing host bits with borrowed subnet bits.
• Forgetting that wildcard masks are inverse masks.
• Treating all /31 and /32 scenarios like ordinary host subnets without considering context.
• Assuming the numerically smallest route wins instead of longest-prefix match.
• Misreading IPv6 compressed zeros.
• Forgetting that IPv6 link-local addresses are not globally routable.
• Overlooking the default gateway when hosts in different subnets cannot communicate.

Switching and Layer 2 readiness

VLANs, trunks, and switching behavior

Spanning Tree and EtherChannel

Can you do this?

• Given a switchport configuration, identify whether the port is access, trunk, routed, or misconfigured.
• Given show vlan brief, determine whether an endpoint is in the expected VLAN.
• Given show interfaces trunk, identify whether a VLAN is allowed and active on a trunk.
• Given show spanning-tree, determine the root bridge and port roles.
• Explain why a host can reach devices in the same VLAN but not another VLAN.
• Identify when router-on-a-stick requires subinterfaces and 802.1Q tags.
• Explain why a native VLAN mismatch can cause unexpected traffic behavior.
• Recognize an EtherChannel that is configured but not bundled.
• Distinguish a Layer 2 loop from a routing loop symptom.
• Explain how broadcast storms affect network performance.

Wireless readiness

Wireless topics often test whether you can map design decisions to symptoms and constraints, not just define acronyms.

Wireless scenario checks

Routing and IP connectivity

Routing fundamentals

OSPF readiness

Inter-VLAN routing choices

Can you do this?

• Given a routing table, identify the route used for a destination.
• Explain why a default route is used only when no more specific match exists.
• Determine whether a static route points to a reachable next hop.
• Recognize a missing return route symptom.
• Troubleshoot OSPF neighbors stuck or missing.
• Distinguish routing failure from ACL denial.
• Explain why two hosts in the same subnet should not need a router.
• Identify when VLAN, trunk, or SVI problems masquerade as routing problems.
• Interpret IPv6 next-hop behavior using link-local addresses.
• Recognize asymmetric routing as a potential troubleshooting complication.

IP services readiness

Core services

NAT/PAT readiness

DHCP readiness

Security fundamentals checklist

Device and management security

ACL readiness

Layer 2 security readiness

Security threat recognition

• Identify phishing, malware, credential theft, brute force, and social engineering at a basic level.
• Match spoofing and man-in-the-middle risks to appropriate controls.
• Recognize why segmentation limits blast radius.
• Explain how ACLs differ from stateful firewall inspection.
• Understand the purpose of VPNs at a conceptual level.
• Recognize why least privilege matters for administrators and users.
• Distinguish confidentiality, integrity, and availability impacts.
• Explain why logging without time synchronization can weaken investigations.

Automation and programmability readiness

The Cisco CCNA (200-301 v2.0) candidate should be comfortable with the operational language of modern networks: controllers, APIs, structured data, and repeatable configuration.

Concepts to review

Data format recognition

You should be able to read small structured examples like this and identify keys, values, lists, and nesting:

{
  "interface": "GigabitEthernet0/1",
  "description": "User access port",
  "enabled": true,
  "vlan": 20
}

Readiness checks:

• Identify whether data is JSON, YAML, or XML from syntax.
• Explain why APIs are useful for repeatable network operations.
• Match REST methods to common actions.
• Interpret an HTTP status success or failure at a basic level.
• Distinguish intent-based policy from manual per-device commands.
• Explain why automation can reduce configuration drift.
• Recognize that automation errors can scale quickly without validation.
• Understand why source control, review, and rollback plans matter.

Cisco IOS-style command recognition

You do not need to memorize every possible command variant, but you should recognize common verification and troubleshooting commands and know what problem each command helps isolate.

Verification command checklist

Configuration recognition examples

Use snippets like these as recognition practice. Focus on purpose, required pieces, and likely verification steps.

interface GigabitEthernet0/1
 switchport mode access
 switchport access vlan 20
 spanning-tree portfast
 spanning-tree bpduguard enable

Readiness cue: access port in VLAN 20 with edge-port behavior and BPDU protection.

interface GigabitEthernet0/1
 switchport mode trunk
 switchport trunk allowed vlan 10,20,30

Readiness cue: trunk carrying selected VLANs; verify with trunk and VLAN output.

interface GigabitEthernet0/0.20
 encapsulation dot1Q 20
 ip address 192.168.20.1 255.255.255.0

Readiness cue: router-on-a-stick subinterface for VLAN 20.

ip route 0.0.0.0 0.0.0.0 203.0.113.1
ipv6 route ::/0 2001:db8:1::1

Readiness cue: IPv4 and IPv6 default routes.

router ospf 1
 network 192.168.10.0 0.0.0.255 area 0
 passive-interface GigabitEthernet0/2

Readiness cue: OSPF enabled for matching interfaces, with one interface not forming neighbors.

access-list 10 permit 192.168.10.0 0.0.0.255

Readiness cue: standard ACL matching a source subnet using a wildcard mask.

access-list 101 permit tcp 192.168.10.0 0.0.0.255 any eq 443
access-list 101 deny ip any any

Readiness cue: extended ACL allowing HTTPS from a subnet, then explicitly denying other IP traffic.

interface GigabitEthernet0/0
 ip nat inside

interface GigabitEthernet0/1
 ip nat outside

access-list 1 permit 192.168.10.0 0.0.0.255
ip nat inside source list 1 interface GigabitEthernet0/1 overload

Readiness cue: PAT for inside subnet traffic using an outside interface.

interface Vlan20
 ip address 192.168.20.1 255.255.255.0
 ip helper-address 192.168.100.10

Readiness cue: SVI provides default gateway for VLAN 20 and relays DHCP to a server.

Troubleshooting decision checks

Fast isolation workflow

    flowchart TD
	    A[User reports network failure] --> B{Link lights / interface up?}
	    B -- No --> L1[Check cable, speed, duplex, admin state, errors]
	    B -- Yes --> C{Valid IP, mask, gateway, DNS?}
	    C -- No --> IP[Check DHCP, static config, VLAN, relay]
	    C -- Yes --> D{Can reach local gateway?}
	    D -- No --> L2[Check VLAN, trunk, ARP, MAC table, port security]
	    D -- Yes --> E{Can reach remote IP?}
	    E -- No --> L3[Check routes, ACLs, NAT, return path]
	    E -- Yes --> F{Can reach by hostname?}
	    F -- No --> DNS[Check DNS server and name resolution]
	    F -- Yes --> APP[Check application, firewall, policy, server]

Symptom-to-cause table

Scenario and decision-point practice

Use these prompts to test judgment. For each, decide the most likely issue and the first verification command or artifact you would inspect.

Layer 2 and VLAN scenarios

Routing scenarios

Security scenarios

Services scenarios

Common weak areas and traps

Final-week review checklist

Technical review

• Rework subnetting drills covering /24 through smaller and larger subnets.
• Convert subnet masks to wildcard masks without hesitation.
• Review IPv6 address types, compression, and default route syntax recognition.
• Read routing tables until you can choose the selected route quickly.
• Review static, default, and floating static route scenarios.
• Review OSPF neighbor formation, passive interfaces, router ID, and route verification.
• Practice VLAN, trunk, native VLAN, and router-on-a-stick questions.
• Review STP root bridge, port roles, PortFast, and BPDU Guard.
• Review EtherChannel negotiation and consistency requirements.
• Review DHCP, relay, DNS, NAT/PAT, NTP, SNMP, syslog, SSH, and QoS concepts.
• Review ACL placement, direction, wildcard masks, implicit deny, and top-down matching.
• Review device hardening and secure management steps.
• Review wireless authentication, WLC/AP roles, SSID-to-VLAN mapping, and RF symptoms.
• Review controller-based networking, APIs, JSON, and automation benefits/risks.

Command and output review

• For each common show command, state what problem it helps confirm or eliminate.
• Practice interpreting partial outputs rather than full lab walkthroughs.
• Identify whether an issue is Layer 1, Layer 2, Layer 3, service, security, or application-related.
• Review configuration snippets for VLANs, trunks, SVIs, subinterfaces, static routes, OSPF, ACLs, NAT, DHCP relay, and SSH.
• Practice explaining the expected verification command after a configuration change.

Exam-readiness checks

• You can solve subnetting questions quickly and accurately.
• You can read a small topology and predict traffic flow.
• You can choose between similar troubleshooting commands.
• You can explain why a wrong answer is wrong.
• You can handle mixed scenarios involving VLANs, routing, ACLs, and NAT together.
• You are not relying only on memorized definitions.
• You have reviewed your missed practice questions by topic, not just by score.
• You have a short list of last-minute weak areas and a plan to revisit them.

Practical next step

Use this checklist as a gap analysis. Mark every item as confident, uncertain, or weak. Then focus practice on the weak and uncertain areas with hands-on labs, command-output interpretation, subnetting drills, and scenario-based questions for Cisco CCNA (200-301 v2.0), exam code 200-301 v2.0.