Quiz Entry - updated: 2026.07.14
When should you use static routing vs. dynamic routing, and what are the trade-offs?
Use static routes for small/stub networks, default routes to ISPs, and backup paths. Use dynamic routing for larger networks that change frequently. Most production networks use both — dynamic for internal routing, static for defaults and exceptions.
| Feature | Dynamic Routing | Static Routing |
|---|---|---|
| Configuration complexity | Independent of network size | Increases with network size |
| Topology changes | Automatically adapts | Requires admin intervention |
| Scalability | Simple to complex topologies | Only simple topologies |
| Security | Must be explicitly configured | Inherent — no routing updates to intercept |
| Resource usage | Uses CPU, memory, bandwidth | No additional resources |
| Path predictability | Depends on topology and protocol | Explicitly defined by admin |
When to use static routes:
- Default route to the ISP (gateway of last resort)
- Stub networks — networks with only one exit path (branch offices)
- Routes to networks outside the dynamic routing domain
- When the admin wants explicit control over the exact path
- Backup routes (floating static) for redundancy
When to use dynamic routing:
- Networks with many routers (10+) — static doesn't scale
- Networks where topology changes are common (link failures, new sites)
- When automatic failover and convergence are needed
- Complex topologies with multiple paths to the same destination
In practice — most networks use both:
- OSPF (Open Shortest Path First)/EIGRP (Enhanced Interior Gateway Routing Protocol) for internal routing between routers
- Static default route on the edge router pointing to the ISP
- Floating static routes as backup for critical links
Go deeper:
Static routing (Wikipedia) — its advantages (no overhead, predictability) and limits.- Dynamic routing (Wikipedia) — how protocols route around failures (the adaptability column).