Skip to content
BiliMind
Roadmap

How to learn the CCNA

This path assumes you can use a computer and have no networking background. It gets you to a pass on the 200-301 exam and, more importantly, to the point where you can configure and troubleshoot a small routed and switched network without notes.

Hours

110-140 hours

Calendar

about 18-23 weeks at 6 hours a week

Stages

6

Start from

Nothing beyond basic computer use. People wrongly believe they need programming or a helpdesk job first; you need neither.

Why the usual order fails

The CCNA fails people who treat it as a reading exam. The written test is not hard because the concepts are deep; it is hard because it asks you to apply subnetting, routing, and switching decisions in under a minute per question. Most study plans front-load theory — OSI model, cable types, port numbers — and leave subnetting and configuration for the final weeks. By then you have memorised facts but not the skill of doing it fast. That is the exact order the exam punishes.

This path puts subnetting on paper in week one, before you touch a single switch. You drill 30-minute timed exercises every week until the arithmetic is automatic. You also start in the command-line interface of Cisco Packet Tracer in week two, not week six, because the most common failing is not knowing the theory but freezing when asked to configure an interface under pressure. Most plans have you reading for a month first; this one has you typing 'ip route' and 'show ip ospf neighbour' within seven days.

The path, in the order it has to be walked.

Each stage assumes the one above it and nothing below it. The check at the foot of each is the point — you are meant to fail it, go back, and try again before moving on.

  1. Subnetting and IP addressing

    weeks 1-2

    Subnetting is the gate to every other CCNA topic because routing, ACLs, and NAT all assume you can read a CIDR block instantly. Starting here means the next ten weeks are spent applying it rather than panicking about it.

    • Binary and decimal conversion for octets
    • IPv4 address classes and private ranges
    • Variable-length subnet masking (VLSM)
    • CIDR notation /8 through /30
    • Subnet masks, network and broadcast addresses
    • Finding the number of usable hosts per subnet
    • Subnetting a /24 into /26, /27, /28, /29, /30

    You can now: Given any IPv4 address and prefix length, you can write the network address, broadcast address, and usable host range on paper in under 45 seconds without a calculator.

  2. Switching and Ethernet

    weeks 3-5

    Switching is the layer-2 foundation that makes VLANs, STP, and port security possible. It sits before routing because a routed network still depends on functioning switches underneath, and because the exam's switching questions are mostly configuration recall, not deep reasoning.

    • Ethernet frame structure and MAC addressing
    • Switch learning and forwarding tables
    • VLAN creation and access ports
    • 802.1Q trunking and native VLANs
    • Spanning Tree Protocol and root bridge election
    • PortFast and BPDU guard
    • Port security with sticky MAC addresses

    You can now: On a two-switch network with three VLANs, you can configure trunks, assign access ports, and verify that a host in VLAN 10 cannot reach a host in VLAN 20 without a router.

  3. Routing and IPv4

    weeks 6-9

    Routing turns connected networks into an internetwork. It comes after switching because you need VLANs and subnets to route between, and after subnetting because every route summarisation and wildcard mask decision depends on it.

    • Static routing and default routes
    • Router-on-a-stick and inter-VLAN routing
    • OSPFv2 areas, router ID, and neighbour states
    • OSPF cost, hello, and dead intervals
    • First Hop Redundancy Protocols: HSRP and VRRP
    • IPv4 access control lists: standard and extended
    • NAT and PAT configuration

    You can now: Given three routers and four subnets, you can build a working OSPF topology, verify neighbour adjacencies, and write an extended ACL that blocks HTTP from one subnet to another while allowing everything else.

  4. IPv6 and wireless

    weeks 10-11

    IPv6 and wireless are smaller topics in the exam blueprint but account for a predictable set of questions. They sit here because they depend on the routing and switching base, and because they are mostly configuration recall rather than new reasoning.

    • IPv6 address format and compression
    • IPv6 SLAAC, DHCPv6, and prefix delegation
    • IPv6 static routes and OSPFv3
    • Wireless standards: 802.11ax, 802.11ac, 802.11n
    • WLAN architecture: access points, controllers, and CAPWAP
    • WiFi security: WPA2, WPA3, and 802.1X

    You can now: Given an IPv6 prefix and a router interface, you can assign addresses, enable OSPFv3, and verify end-to-end reachability between two subnets, plus explain why a specific WiFi configuration fails authentication.

  5. Security and network services

    weeks 12-13

    Security and services are the last content block because they assume you can already route and switch. The exam asks about a specific set of services and attacks, and most of that material is recall plus a few configuration commands.

    • Common security threats: DoS, MITM, VLAN hopping
    • DHCP snooping and dynamic ARP inspection
    • Access control lists for traffic filtering
    • Network Time Protocol and Syslog
    • DNS and DHCP configuration on Cisco devices
    • Simple Network Management Protocol basics
    • Secure device management: SSH, passwords, and privilege levels

    You can now: You can configure DHCP snooping and DAI on a switch, verify that a rogue DHCP server is blocked, and interpret a syslog message to identify the source of a failed login.

  6. Automation, exam simulation, and review

    weeks 14-18

    This final stage is not new content but consolidation. Automation is a small part of the blueprint, and the rest of the time is spent on full-length timed exams and lab reviews, because the gap between knowing the material and performing it under a clock is where most candidates fail.

    • SDN concepts: control plane, data plane, and management plane
    • REST APIs and JSON data formats
    • Configuration management tools: Ansible, Puppet, and Chef
    • Cisco DNA Center and Cisco SD-Access overview
    • Timed subnetting drills: 50 questions in 60 minutes
    • Full 200-301 practice exams with 120 questions in 120 minutes
    • Lab review: one integrated topology with switching, OSPF, NAT, and ACLs

    You can now: You can complete a timed 120-question practice exam with a score above 85% and configure a full routed and switched network from a blank start in under two hours.

The hours are fixed. The calendar is yours.

The same path at three speeds, and what actually goes wrong at each.

3 hours a week

This pace takes about 10 months to finish. Subnetting skills fade between sessions, so you will spend the first 20 minutes of every session re-warming. Lab hours get squeezed out and the exam becomes a memory test rather than a skill test. It works only if you accept a long, slow build and never skip a week.

8 hours a week

This is the sustainable middle. Roughly 16 to 18 weeks to finish. You can keep a job and still get two or three lab sessions in per week. The risk at this pace is skipping review weeks; the material accumulates faster than you expect, and without the final review block, the score on the actual exam drops by 10-15 points.

20 hours a week

This compressed pace finishes in 6 to 7 weeks, but it breaks for most people. The subnetting drills need daily repetition, and the lab hours start to blur. You will pass if you have prior networking exposure, but without it, the retention is superficial and the exam feels like a coin flip on questions you half-remember.

What goes wrong

Four ways people lose a year on this.

Each of these is appealing for a real reason, which is why they are common. What they cost is the part nobody mentions.

  • Learning subnetting from videos instead of paper drills

    People watch subnetting tutorials, nod along, and then sit down to the exam with no timed practice. The appeal is that videos feel like progress. The cost is that the exam asks you to subnet under time pressure, and without 20-30 hours of paper drills, you will run out of time on the first ten questions.

  • Leaving Packet Tracer until the last month

    Many plans treat configuration practice as a final review activity. The appeal is that theory feels safer and more controllable. The cost is that the exam has simulation questions that ask you to fix a broken OSPF neighbour or a VLAN misconfiguration, and if you have only typed commands for two weeks, you freeze.

  • Memorising Cisco commands without understanding the output

    People learn 'show ip route' and 'show spanning-tree' as commands, not as diagnostic tools. The appeal is that it seems like the fastest way to get through the lab exercises. The cost is that the exam asks you to interpret output you have not seen before, and memorised commands without reading the output means you cannot tell a working network from a broken one.

  • Using old CCNA materials or dumps

    The 200-301 exam changed in 2020, and older books and question dumps still float around. The appeal is that they feel like a shortcut. The cost is that the exam now includes automation, SDN, and wireless topics that the old materials do not cover, and you will fail questions that should have been easy because you studied the wrong blueprint.

How to know it worked.

Not a syllabus you tick off — six things to attempt. If one of them is still hard, the stage it belongs to is the one to go back to.

  1. Write the network and broadcast address for 172.16.45.67/27 in under 30 seconds.
  2. Configure a VLAN 10 access port and a trunk on a Packet Tracer switch without looking at notes.
  3. Explain why a spanning tree root bridge election chooses the switch it does.
  4. Build a static route between two subnets and verify it with ping and traceroute.
  5. Configure OSPF on three routers and explain why two neighbours are not forming an adjacency.
  6. Write an extended ACL that blocks only HTTP traffic from 192.168.1.0/24 to 10.0.0.0/8.
Questions

Questions about learning the CCNA.

The five we hear most. The intro film answers most of them in a minute and a half.

how long does it take to study for the ccna

Most people need 110-140 hours of focused study. At 6 hours a week that is around 18 weeks. If you have prior networking experience you might do it in 90 hours, but the subnetting and lab work still require the same number of repetitions.

do i need to know programming for the ccna

No. The CCNA does not require programming. You need to read JSON and understand the concept of a REST API, but you will not write a single line of code. People confuse this with the DevNet certification, which is a different exam.

is the ccna hard

It is hard in a specific way. The content is not mathematically deep, but the exam is timed and asks you to apply subnetting and configuration under pressure. Most people who fail do not lack knowledge; they lack timed practice.

can i pass the ccna without any lab practice

It is possible but unlikely. The exam includes simulation questions that ask you to configure or troubleshoot a network in a simulated environment. Without at least 40 hours of hands-on Packet Tracer or real equipment work, you will not be able to do these fast enough.

is the ccna still worth it

For a networking or IT operations role, yes. It is still the most commonly requested certification in network administrator and entry-level network engineer job postings. But if you are aiming at software development or cloud engineering, it is less relevant than a cloud-specific certification.

A path is not a course.

This is the shape of the CCNA, not the teaching of it. Hand the same path to BiliMind and it writes the lessons onto it — in the form each one calls for, with practice that gets marked and a schedule that bends when your week does. Mapping a course is free and unlimited.

This roadmap was drafted on 18 September 2026 by the same engine that builds BiliMind courses, and reviewed before publishing. Hours are honest estimates for working competence, not for a demo — treat them as a starting point and adjust them against your own first fortnight.

The intro · 1:25