Everything mapped to the CCNA 200-301 blueprint. Articles tagged CCNA cover the exam topics in the order you actually learn them, each one backed by a lab you can build yourself.
Subnetting is the one CCNA skill you cannot fake. Every other topic gives you partial credit for concepts; subnetting questions have exactly one right answer, and the exam expects you to find it in under a minute. The good news:
The technical and behavioral questions network engineer interviews actually ask, with strong answers, 2026 salary bands, career paths after CCNA, and resume keywords that pass the ATS.
Still worth it for most people, with one big caveat. The honest take on the 2026 to 2027 exam change, what the cert actually gets you, and the AI question.
Every network has a network engineer who swears nothing changed, and a network that disagrees. This capstone builds the tool that settles the argument: an automated backup and drift detector that snapshots every device config to a golden baseline, re-
Everything you have scripted so far in this series has been imperative: do this, then this, on these devices. Configuration management tools flip the model. You declare the state you want, and the tool figures out whether anything needs doing.
Exam topic 6.5 asks you to describe the characteristics of REST-based APIs: HTTP verbs, authentication, data encoding, response codes. You could memorize those from a table, or you could spend twenty minutes actually doing them: getting a 401,
The CCNA 200-301 blueprint says it plainly: "Interpret JSON encoded data" (exam topic 6.7). Most candidates prepare for that line by staring at a sample blob the night before. In this lab you do what the
Reading the network is safe. Writing to it is where automation earns its keep, and where it earns its scars. In this lab your Python script enters configuration mode on three routers, provisions a new loopback interface on each, verifies
A CCNA-level engineer checks four devices by opening four consoles. An automation-minded one runs one script. This lab takes the single-router Netmiko connection you built in Lab auto-01 and scales it to the whole topology: R1,
Every network automation tutorial on the internet starts the same way: "first, install Python on your laptop." This one does not. In this lab you build the automation host inside the network, on the same Alpine Linux node
Real outages do not arrive one clean fault at a time. A change window goes wrong, three things break at once, and you get a single sentence from the user: "the branch is down, nothing works." This capstone
Security features are the only thing on a network designed to make traffic fail. That makes the tickets sneaky: the network is doing exactly what it was told, and what it was told is wrong. An ACL silently drops the