Exhibit
R1# show running-config | section ip route
ip route 0.0.0.0 0.0.0.0 10.0.0.2
ip route 0.0.0.0 0.0.0.0 10.0.0.6 10
ip route 192.168.10.0 255.255.255.0 10.0.0.2
!
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, E - EGP
i - IS-IS, 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
10.0.0.0/30 is subnetted, 2 subnets
C 10.0.0.0 is directly connected, GigabitEthernet0/0
L 10.0.0.1 is directly connected, GigabitEthernet0/0
C 10.0.0.4 is directly connected, GigabitEthernet0/1
L 10.0.0.5 is directly connected, GigabitEthernet0/1
S 192.168.10.0/24 [1/0] via 10.0.0.2
! Note: static default route to 10.0.0.2 is missing from routing table (recursive failure)
R1# show ipv6 interface brief
GigabitEthernet0/0 [up/up]
FE80::1
2001:DB8:1:1::1/64
GigabitEthernet0/1 [up/up]
FE80::1
2001:DB8:2:1::1/64
R1# show ipv6 route
IPv6 Routing Table - default - 4 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route, M - MIPv6
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D - EIGRP, EX - EIGRP external
C 2001:DB8:1:1::/64 [0/0]
via GigabitEthernet0/0, directly connected
L 2001:DB8:1:1::1/128 [0/0]
via GigabitEthernet0/0, receive
C 2001:DB8:2:1::/64 [0/0]
via GigabitEthernet0/1, directly connected
L 2001:DB8:2:1::1/128 [0/0]
via GigabitEthernet0/1, receive
! No IPv6 default route configured- A
Remove the existing incorrect IPv4 static default route and reconfigure the primary IPv4 default route with the correct next-hop address (10.0.0.2) and AD 1. Add the backup IPv4 default route via 10.0.0.6 with AD 10. Then add IPv6 static default routes: ipv6 route ::/0 2001:DB8:1:1::2 1 and ipv6 route ::/0 2001:DB8:2:1::2 10. Also add the static route for 192.168.10.0/24 via 10.0.0.2 with AD 1.
This correctly removes the misconfigured default route (pointing to nonexistent 10.0.0.3), installs the primary default route to R2 with AD 1, adds the backup default route to R3 with AD 10, and completes the floating static setup with IPv6 defaults and the required LAN static route.
- B
Add a static route to 10.0.0.0/30 via the backup link to R3, then the default route to 10.0.0.2 will work. Then configure IPv6 default routes with AD 1 and 10 as described.
Why wrong: This is incorrect because adding a static route to 10.0.0.0/30 via the backup link would cause the default route to use the backup path, defeating the purpose of having a primary path. The issue is that the next-hop 10.0.0.2 is not directly connected or reachable; the correct fix is to ensure the interface is up and the next-hop is on a directly connected subnet, not to add a static route via the backup.
- C
Change the administrative distance of the IPv4 default route to 10 and the backup to 1, so the backup becomes primary. Then configure IPv6 default routes with AD 10 and 1 respectively.
Why wrong: This is incorrect because it swaps the intended primary and backup paths. The requirement specifies that the primary path goes through R2 with AD 1 and backup through R3 with AD 10. Changing the AD values would make R3 the primary, which is not desired.
- D
Remove the existing IPv4 static default route and configure it with the next-hop as the exit interface (e.g., GigabitEthernet0/0) instead of the IP address. Then add IPv6 default routes using the exit interface as well.
Why wrong: This is incorrect because using an exit interface for a static route (point-to-point) is valid, but it does not fix the recursive routing failure if the next-hop IP is unreachable. The issue is likely that the next-hop IP is not in the routing table; using the interface might bypass the recursive lookup but would still require the interface to be up. However, the requirement specifies using next-hop IP addresses, and the IPv6 routes also need next-hop IPs. Moreover, the problem statement indicates the next-hop is 10.0.0.2, which should be directly connected; using the interface is not necessary and may not match the intended design.
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.