# Static Routing

Static routing directs network traffic using explicitly configured destination-to-next-hop mappings rather than routes learned through a dynamic routing protocol.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/static-routing

> Static routes provide predictable forwarding paths between networks, gateways, and appliances without exchanging routing updates. They work well for stable topologies, but engineers must explicitly manage route changes, return paths, and failure recovery.

Practice exams covering Static Routing: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of Static Routing

Static routing provides explicit forwarding control while requiring deliberate prefix management, return-path configuration, route-preference checks, and resilience planning.

1. **Explicit destination-to-target configuration**: A static route maps a destination prefix to a configured next hop or forwarding target. Manage these entries as reviewed, versioned configuration to make intended paths auditable.
2. **Longest-prefix matching**: The most specific matching destination determines the forwarding path before equal-prefix preference rules apply. Check narrower routes when traffic does not follow an expected default or summary route.
3. **Independent of routing-protocol advertisements**: Static routes do not learn destinations or withdrawals through BGP or another dynamic routing protocol. Automating their creation through APIs does not make them dynamically learned routes.
4. **Explicit failure and backup design**: An ordinary static route does not verify end-to-end reachability or discover another connection. Use supported route tracking, managed resilience, or automation where needed, and test the resulting failure behavior.
5. **Platform-specific route preference**: Static and dynamically learned routes can coexist, but their preference for identical destination prefixes depends on the routing platform. A static route can unintentionally override a working propagated route rather than act as its backup.
6. **Bidirectional routing requirements**: A valid forward route does not establish a working return path. Verify routing in both directions and account for stateful inspection, NAT, and asymmetric paths.

## Cloud services for Static Routing

Amazon VPC route tables direct subnet traffic toward the appropriate connectivity gateway or transit gateway attachment. AWS Site-to-Site VPN provides encrypted hybrid connectivity and supports static routing or BGP with either virtual private gateway or transit gateway termination. AWS Transit Gateway adds a separate forwarding layer where static routes and supported route propagation connect multiple networks. AWS Direct Connect uses BGP on its virtual interfaces, even when surrounding cloud route tables contain static entries. Engineers must coordinate these layers, configure return paths, and test failures rather than infer a connection's routing protocol from a single route-table entry.

- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: VPC route tables use destination-to-target entries to control forwarding for associated subnets. Engineers configure static routes toward gateways, peering connections, transit gateways, and appliances, while checking longest-prefix matching and precedence over propagated routes.
- **[AWS Site-to-Site VPN](https://blowstack.com/tools/cloud-services-hub/aws-site-to-site-vpn)**: VPN connections terminating on either a virtual private gateway or a transit gateway support static routing or dynamic routing with BGP. Static routing requires explicit destination and return-path configuration; VPN ECMP through Transit Gateway requires BGP rather than static routing.
- **[AWS Transit Gateway](https://blowstack.com/tools/cloud-services-hub/aws-transit-gateway)**: Transit gateway route tables support static routes toward attachments and static blackhole routes that intentionally discard traffic. For statically routed VPN attachments, manually configure the required destination routes in the appropriate transit gateway route tables and verify attachment associations.
- **[AWS Direct Connect](https://blowstack.com/tools/cloud-services-hub/aws-direct-connect)**: Direct Connect virtual interfaces require BGP to exchange routing information. Static routes in surrounding VPC or transit gateway route tables can steer traffic toward the connectivity path, but they do not replace the virtual interface's BGP requirement.

## Static Routing exam questions

Real practice exam questions on Static Routing, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company connects an application VPC with CIDR block 10.60.0.0/16 to its data center through AWS Transit Gateway and an AWS Site-to-Site VPN connection. The customer gateway device does not support BGP.

The transit gateway has two route tables:
• Application-RT is associated with the VPC attachment. It contains a route for 172.20.10.0/24 targeting the VPN attachment.
• Edge-RT is associated with the VPN attachment. It contains a route for 10.60.0.0/16 targeting the VPC attachment.

The application subnet route tables contain 172.20.0.0/16 targeting the transit gateway. Connectivity between the application VPC and the existing data center subnet, 172.20.10.0/24, works.

The company adds data center subnet 172.20.20.0/24. Both VPN tunnels remain operational. The customer gateway has the required routes for the application VPC, and all security controls permit the new subnet. Neither transit gateway route table has any other route matching 172.20.20.0/24.

Which change will establish bidirectional connectivity between the application VPC and the new data center subnet?

**Correct answer:** Add a static route for 172.20.20.0/24 to Application-RT with the VPN attachment as its target.

**Explanation:** Application-RT processes traffic arriving from the VPC attachment and needs an explicit route to the new data center prefix through the VPN attachment. The VPC subnet routes already cover the new prefix, and Edge-RT and the customer gateway already provide the return path.

## Practice Static Routing in a full exam

Questions on Static Routing in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 4 questions

## What is Static Routing

Static routing is the practice of explicitly configuring a forwarding path for a destination network. A route identifies a destination prefix, such as 192.168.0.0/16, and a next-hop address, interface, or cloud resource target. Unlike dynamic routing, static routing does not use a protocol such as Border Gateway Protocol (BGP) to learn reachability from neighboring routers. Routes can be created through a console, API, or infrastructure-as-code tool; static describes how the route is supplied, not whether someone enters it manually.

Forwarding uses longest-prefix matching to select the most specific matching destination. For example, a route for 192.168.0.0/16 takes precedence over a default route of 0.0.0.0/0 when sending traffic to 192.168.10.20. A more specific route for 192.168.10.0/24 would take precedence over both. Default routes are useful for destinations without a more specific match, but they do not override narrower routes. IPv6 follows the same principle, with ::/0 representing the default route.

In cloud networks, static routes commonly direct traffic toward internet gateways, NAT gateways, private connectivity gateways, peering connections, transit gateways, or network appliances. Consider a cloud network using 10.20.0.0/16 and an on-premises network using 192.168.0.0/16. The cloud subnet route table needs a route for the on-premises prefix toward the hybrid connectivity gateway. The on-premises router also needs a return route for the cloud prefix through the appropriate connection. Routes alone are insufficient: firewall policies, security groups, network ACLs, tunnel configuration, and address translation must also permit the traffic.

Distinguish a connection's routing mode from the configuration of individual forwarding tables. AWS Site-to-Site VPN connections terminating on either a virtual private gateway or a transit gateway support static routing or dynamic routing with BGP. For a statically routed VPN attached to a transit gateway, engineers manually add the required destination routes to the transit gateway route table. A static VPC route pointing toward a transit gateway does not indicate whether the underlying VPN uses static routing or BGP. VPN equal-cost multipath routing through Transit Gateway requires dynamic routing with BGP and the appropriate ECMP configuration; static VPN routes do not provide that capability.

Static routing offers explicit control without requiring routing-protocol sessions. It suits small networks, stable destination sets, and deliberate traffic steering through inspection appliances. Its operational cost increases as the number of prefixes, sites, and alternate paths grows. Adding or removing an on-premises network may require coordinated changes across multiple routing tables. A broad summary route can reduce configuration, but it can also direct traffic toward destinations that the selected connection cannot actually reach.

An ordinary static route does not independently discover end-to-end failure or learn an alternate path. A route can remain configured while its destination is unreachable, causing traffic loss. Some routers support tracked static routes and floating static routes, while cloud platforms may provide managed target resilience or support health-driven automation. These mechanisms require explicit design and testing; configuring two possible targets does not by itself guarantee useful failover.

Dynamic routing uses advertisements and withdrawals to adapt routing information as reachability changes. BGP is therefore commonly preferred for larger hybrid networks and redundant connections, although it still requires correct policy and failure-detection configuration. AWS Direct Connect virtual interfaces require BGP; adding static routes to a VPC does not replace that requirement. Static routes and BGP-learned routes can coexist at different layers of the same architecture.

When identical destination prefixes have multiple route sources, preference rules depend on the platform. In AWS VPC route tables, a manually configured static route takes precedence over a propagated route for the same destination prefix. Do not assume that a static route automatically serves as a backup or that traditional router administrative-distance settings exist in every cloud routing table. During implementation, review route-table associations, propagation settings, overlapping prefixes, return paths, and appliance symmetry. Test both normal forwarding and connection failures before relying on the design.
