Static vs Dynamic Routing: A CCNA 200-301 Explainer

Few topics trip up new candidates on the Cisco Certified Network Associate (200-301) exam more than the difference between static and dynamic routing. On paper the distinction sounds trivial — you either type routes in by hand or you let a protocol figure them out — but the exam rarely asks it that plainly. It hands you a routing table with competing routes and asks which one the router will actually use, or drops you into a scenario and asks whether a static route or OSPF is the right tool. To answer confidently you need the machinery underneath the two approaches: how a router builds its table, how it breaks ties, and how it picks the most specific match. Those mechanics show up all over the CCNA 200-301 routing questions, so this explainer walks through all of them.

What a router is actually doing

Strip away the terminology and a router has one job: for every packet that arrives, look at the destination IP address and decide which interface to send it out of. It answers that by consulting its routing table, a list of known destination networks paired with the next hop or exit interface that gets a packet closer to each one. Static and dynamic routing are simply two ways of populating that table. With static routing, an administrator types each route in by hand. With dynamic routing, routers run a protocol — OSPF, EIGRP, and so on — that advertises the networks they know about and learns the rest from their neighbors. The forwarding decision afterward is identical; only the source of the information differs.

Static routing is predictable, uses no CPU or bandwidth to maintain, and is exactly what you want on a small network or a stub site with one way out. Its weakness is that it does not react: if a link fails, a static route keeps pointing at the dead path until a human fixes it. Dynamic routing solves that — when the topology changes, the protocol reconverges and installs new paths on its own — at the cost of complexity and overhead. Real networks mix both, and the 200-301 blueprint expects you to know when each earns its place.

Administrative distance: how a router trusts a source

Here is the scenario that catches people out. Suppose a router learns a route to the same network 10.1.1.0/24 from two sources — a static route you configured and OSPF running in the background. Which wins? The router breaks the tie with administrative distance (AD), a number rating how trustworthy each source of routing information is, where lower is more trusted. A directly connected network has an AD of 0, a static route defaults to 1, EIGRP internal routes sit at 90, and OSPF sits at 110. Because the static route's AD of 1 beats OSPF's 110, the static route gets installed in the table; OSPF's version is set aside unless the static route disappears.

Administrative distance only comes into play when two different route sources offer a path to the same destination, and it is decided before any metric is considered. This ordering is a classic exam gotcha: candidates reach for the "better metric" instinctively, but a route from a lower-AD source is chosen regardless of how good the losing source's metric looks. Memorizing the common AD values — connected 0, static 1, EIGRP 90, OSPF 110, RIP 120 — is one of the highest-yield things you can do for the routing questions on this exam.

Longest-prefix match: the most specific route wins

Administrative distance answers "which source do I trust for this network." A more fundamental rule answers "which route in my table matches this packet at all," and that rule is longest-prefix match. When a packet arrives, the router compares its destination against every route and selects the one with the longest matching prefix — the most specific one. If the table holds both 10.1.0.0/16 and 10.1.1.0/24, a packet bound for 10.1.1.5 matches both, but the /24 is more specific, so it wins; the /16 covers only the addresses the /24 does not.

Longest-prefix match sits above administrative distance and metrics in the decision order, and this is the part learners most often get backwards. The router does not first pick the lowest-AD route and then check specificity — it finds the most specific matching prefix first, and AD and metric only settle contests within routes to that same prefix. Consider a default route 0.0.0.0/0 learned via OSPF and a static 172.16.5.0/24: a packet for 172.16.5.9 takes the static /24 every time because /24 is longer than /0, and the AD comparison never happens because they are not routes to the same network. Keep those two mechanisms separate and a whole category of exam questions becomes straightforward. Working through practice questions for the CCNA 200-301 and reviewing each miss is the fastest way to make that decision order automatic.

A quick tour of OSPF and EIGRP

The 200-301 exam focuses its dynamic-routing depth on two protocols, and you should be able to describe how each thinks. OSPF (Open Shortest Path First) is a link-state protocol and an open standard, so it runs between equipment from any vendor. Every OSPF router floods information about its own links to all the others, so each independently builds a complete map of the area and runs the shortest-path algorithm over it. Its metric is cost, derived from interface bandwidth — lower cost, better path. Because every router shares the same map, OSPF converges cleanly and scales well when the network is divided into areas.

Cisco's EIGRP (Enhanced Interior Gateway Routing Protocol) takes a different approach. Rather than building a full map, each router learns routes from its neighbors and tracks backup paths, so when a primary path fails it can often switch to a pre-computed feasible successor almost instantly. Its metric factors in bandwidth and delay by default. You do not need to hand-calculate these metrics, but you do need the concepts: OSPF is standards-based and link-state with a cost metric; EIGRP is a Cisco advanced distance-vector protocol prized for fast convergence. Their default administrative distances — 110 and 90 respectively — tie straight back to the tiebreaking discussion above.

Default routes: the catch-all

One more piece completes the picture. No router can hold a route to every network on the internet, so it uses a default route — written 0.0.0.0/0 — as a catch-all for any destination it has no more specific entry for. By longest-prefix logic, a /0 is the least specific route possible, so it only gets used when nothing else matches, which is exactly what you want for "send everything I don't recognize toward my ISP." You can create one statically (a default static route, sometimes called the gateway of last resort) or have a protocol advertise it. Default routes are why a small branch office can reach the entire internet with a single line of configuration pointing at its upstream link.

Bringing it together for the exam

When you read a routing question on the 200-301, run the same checklist the router does. First find the most specific prefix that matches the destination — longest-prefix match. Only if two routes to that same network compete do you compare administrative distance, and only if two routes come from the same protocol do you compare the metric. Static versus dynamic is really a question of where a route came from and how much the router trusts it, and every other concept here hangs off that. Master this decision order and the routing portion of the Cisco Certified Network Associate exam stops being a memory test and becomes a logic puzzle you can reason through.

The way to lock it in is repetition against realistic scenarios rather than rereading notes. On ExamStudyApp, adaptive practice keeps serving you routing items from the exact areas where you are slipping — tables where AD and prefix length pull in different directions, say — while full-length timed 200-301 exam simulations mirror the real format and pass standard, so readiness tracking tells you when your scores are genuinely holding above the line. Study the mechanics until the router's logic feels like your own, validate it with timed runs, and static versus dynamic routing becomes one of the parts of the CCNA you can count on getting right.