Static vs dynamic routing: when to use which
The decision in one paragraph
A static route is typed in by an administrator and never changes unless someone edits it; a dynamic route is learned from a routing protocol such as OSPF, EIGRP, RIP or BGP and updates itself when the topology changes. Use static routes where the path is fixed and small: a stub site with one exit, a default route to an ISP, a host route to one server. Use dynamic routing where there are many routers, several possible paths or frequent change. The exam rule: if the scenario says the network must adapt automatically to a failure, the answer is dynamic; if it says low overhead, a single path or tight control, the answer is static.
Scenario decision table
| Situation | Better fit | Reason |
|---|---|---|
| Branch router with one WAN link and one LAN | Static default route | One possible exit, so there is nothing to learn or recalculate |
| 40 routers with redundant links | Dynamic (an IGP such as OSPF) | Manual edits do not scale and cannot react to link failure |
| Reach a single server at 10.5.5.9 through a specific next hop | Static host route (/32) | Precise, no protocol traffic |
| Primary path is learned dynamically, with a backup circuit | Floating static route | Backup stays out of the table until the primary vanishes |
| Router must be locked down and exchange no routing information | Static | A dynamic protocol would advertise and accept routes |
| Two organisations connect and exchange reachability | BGP (exterior) | Policy between autonomous systems, not just best path |
| Network gains new subnets weekly | Dynamic | New networks propagate without logging in to every router |
What static routing costs and gives
Static routes use no bandwidth and almost no CPU, they are predictable, and the administrator controls the exact path. The AD of a static route is 1 by default, so it beats every dynamic source for the same prefix (administrative distance explains why). The cost is manual work: every router needs routes in both directions, and when a link or next hop fails, a plain static route stays in the table as long as its next hop is reachable, so traffic goes into a black hole until someone fixes it.
Three static route types appear in the CCNA objectives: a default route (0.0.0.0/0, or ::/0 for IPv6), a network route to a remote subnet, and a host route with a /32 (or /128) mask. A fourth, the floating static route, is a static route with an AD above the primary source. For example, with OSPF as the primary path at AD 110:
ip route 0.0.0.0 0.0.0.0 198.51.100.1 130
The trailing 130 keeps the route out of the routing table while OSPF supplies a default route. If the OSPF route is withdrawn, the static route is installed.
What dynamic routing costs and gives
Dynamic protocols discover neighbors, exchange routes and recompute paths after a change, so they scale and recover without a human. The costs are CPU and memory on the router, protocol traffic, convergence time, and a larger configuration surface (a wrong neighbor setting or an unwanted route can spread through the whole network).
Exam questions rely on a short classification:
| Property | Options |
|---|---|
| Scope | Interior gateway protocols (IGPs) run within one autonomous system: RIP, OSPF, EIGRP, IS-IS. Exterior: BGP between autonomous systems, see BGP basics |
| Algorithm | Distance vector (RIP, and EIGRP, which Cisco describes as advanced distance vector) shares routes with neighbors. Link state (OSPF, IS-IS) floods topology information so every router builds the same map and runs shortest path first |
| Metric | RIP uses hop count; OSPF uses cost derived from interface bandwidth; EIGRP combines bandwidth and delay by default |
| Default AD | EIGRP internal 90, OSPF 110, RIP 120, external BGP 20, internal BGP 200 |
RIP is the standard example of a limit: the maximum usable metric is 15 hops, and 16 means unreachable (RFC 2453), so it does not suit large networks. OSPF scales through areas; the single-area case, with neighbor states and the DR/BDR election, is in OSPF explained.
A worked example: choosing for a small company
A company has a head office router HQ and two branch routers B1 and B2. Each branch has one link to HQ, and HQ has two ISP links.
- B1 and B2 each need exactly one route: a default route towards HQ. Static, two commands in total.
- HQ needs routes to the two branch LANs: static network routes, or OSPF if branches are added often.
- HQ to the ISPs: a primary static default route with the default AD of 1, and a floating static default with AD 250 to the second ISP. If the first ISP’s next hop becomes unreachable, the second takes over.
One caveat the exam also likes: a floating static route only works as a failover when the primary route actually disappears from the table. If the primary link stays “up” but the ISP is broken further away, a plain static route remains in the table. The usual fix is route tracking or a dynamic protocol, which is beyond the entry-level objectives.
Which exams test this
| Exam | How the topic appears | Where on this site |
|---|---|---|
| CCNA 200-301 | v1.1 (until Feb 2, 2027): IP Connectivity (25%), 3.3 configure and verify IPv4 and IPv6 static routing (default, network, host, floating static). v2.0 (from Feb 3, 2027): IP Routing (20%), 3.2 troubleshoot static routing, same four types. Dynamic routing is tested through OSPF only | IP routing explained |
| CompTIA Network+ N10-009 | Network Implementation (20%), 2.1 characteristics of routing technologies: static routing and dynamic routing (BGP, EIGRP, OSPF). Troubleshooting (24%), 5.3 route selection and default routes | Network implementation explained covers static versus dynamic at concept level |
How exam questions are built around this choice
Questions rarely ask for a definition. They describe a network and a requirement and ask for the approach. The decisive words are “automatically” (dynamic), “a single path”, “minimal overhead” or “stub” (static), “backup only if” (floating static), and “between two ISPs” or “between organisations” (BGP). A common wrong answer is a dynamic protocol for a one-exit branch, which works but is more than the requirement asks for. Another is a static route with the wrong direction: a branch needs a route to HQ and HQ needs a route back to the branch, or return traffic is lost. Questions with an ip route line test whether you read the last number as AD, not as a metric. Subnet boundaries inside the route matter too; revisit subnetting step by step if the prefix arithmetic is slow.
Two practice questions
Question 1. A small branch office has one router with a single uplink to headquarters and no other connections. Which routing configuration is the most appropriate?
- A. OSPF with multiple areas
- B. BGP with an AS number for the branch
- C. A static default route to headquarters
- D. A /32 static host route for every headquarters device
Show answer
Answer: C
With one exit, a single static default route points all non-local traffic to headquarters, uses no bandwidth for protocol traffic and has nothing to recalculate. A dynamic protocol would work but adds overhead for no benefit. BGP is meant for exchanging routes between autonomous systems, and a host route for every headquarters device would be unmanageable.
Question 2. A router learns its default route from OSPF. An administrator adds a static default route to a backup ISP that must be used only if the OSPF default route is lost. Which command achieves this?
- A. ip route 0.0.0.0 0.0.0.0 198.51.100.1 200
- B. ip route 0.0.0.0 0.0.0.0 198.51.100.1
- C. ip route 0.0.0.0 0.0.0.0 198.51.100.1 110
- D. ip route 198.51.100.1 255.255.255.255 0.0.0.0
Show answer
Answer: A
A floating static route needs an AD higher than OSPF’s 110, and 200 qualifies. Without a trailing value the static route has AD 1 and would replace the OSPF route immediately. AD 1 and AD 110 do not keep the route as a backup, since 1 is preferred and 110 ties with OSPF. A /32 host route would not be a default route at all.
Go deeper
- RFC 2453, RIP Version 2, for the 15-hop limit
- Cisco: what is administrative distance, including floating static routes
- Related on this site: administrative distance and the routing table, NAT types, the CCNA IP routing guide and the Network+ implementation guide.