Exhibit
R1# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
192.0.2.0/30 is subnetted, 1 subnets
C 192.0.2.0/30 is directly connected, GigabitEthernet1/0/1
L 192.0.2.1/32 is directly connected, GigabitEthernet1/0/1
198.51.100.0/30 is subnetted, 1 subnets
C 198.51.100.0/30 is directly connected, GigabitEthernet1/0/2
L 198.51.100.1/32 is directly connected, GigabitEthernet1/0/2
S 203.0.113.0/24 [1/0] via 192.0.2.2
S 203.0.113.0/24 [200/0] via 198.51.100.2
R1# show running-config | section ip route
ip route 203.0.113.0 255.255.255.0 192.0.2.2
ip route 203.0.113.0 255.255.255.0 198.51.100.2
R1# show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet1/0/1 192.0.2.1 YES manual up up
GigabitEthernet1/0/2 198.51.100.1 YES manual up up
(Simulate that after failure, show ip interface brief shows Gi1/0/1 down/down, but show ip route still shows the static route via 192.0.2.2 as the best route.)
R1# show ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
198.51.100.0/30 is subnetted, 1 subnets
C 198.51.100.0/30 is directly connected, GigabitEthernet1/0/2
L 198.51.100.1/32 is directly connected, GigabitEthernet1/0/2
S 203.0.113.0/24 [1/0] via 192.0.2.2
S 203.0.113.0/24 [200/0] via 198.51.100.2
(Note: The connected route for 192.0.2.0/30 is missing, but the static route via 192.0.2.2 remains with AD 1, blocking the floating static from being installed.)- A
Replace the primary static route with one that uses an exit interface: ip route 203.0.113.0 255.255.255.0 GigabitEthernet1/0/1 192.0.2.2
This is correct because when a static route specifies an exit interface, the route is directly dependent on the interface state. If the interface goes down, the route is automatically removed from the routing table, allowing the floating static route with a higher AD to take over.
- B
Increase the administrative distance of the floating static route to 255
Why wrong: This is incorrect because an AD of 255 means the route is considered unreachable and will never be installed in the routing table. The floating static route would never become active.
- C
Add the permanent keyword to the floating static route
Why wrong: This is incorrect because the permanent keyword keeps a static route in the routing table even if the next-hop becomes unreachable. This would prevent the floating static route from taking over, as the primary route would remain.
- D
Change the administrative distance of the primary static route to 200 and the floating static route to 1
Why wrong: This is incorrect because swapping the AD values would make the floating static route the primary route (lower AD) and the original primary route the backup. This does not fix the issue of the primary route not being removed when the interface fails.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.