CCNA IP Routing Practice Test 22 — 15 Questions

Question 1

You have console access to both R1 and R2. Configure OSPFv2 on both routers to establish a single-area adjacency in area 0. The link between R1 and R2 uses 10.0.0.0/30. Currently, OSPF is not configured on either router. After configuration, verify the adjacency forms and routes are exchanged.

Accepted Answer

Configure 'router ospf 1' on R1 and R2, set router-id, and use 'network 10.0.0.0 0.0.0.3 area 0' on both routers.. The essential requirement is enabling OSPFv2 on both routers with matching area 0 on the 10.0.0.0/30 link. On R1 and R2, enter 'router ospf 1', set a unique router-id, and use 'network 10.0.0.0 0.0.0.3 area 0' to advertise the link. The solution commands include optional networks (192.168.1.0/24 and Loopback0) that are not required for the adjacency and are shown only as examples; candidates should focus on the link network. After configuration, 'show ip ospf neighbor' should show a FULL state. Common mistakes include using a subnet mask instead of a wildcard mask (option C) or a /32 wildcard (option D), and not configuring OSPF on R2 (option B).

Answer

Configure 'router ospf 1' on R1 only, and use 'network 10.0.0.0 0.0.0.3 area 0' on R1; R2 does not need OSPF configuration because it will learn routes via the directly connected interface.

Answer

Configure 'router ospf 1' on both routers, set router-id, and use 'network 10.0.0.0 255.255.255.252 area 0' on both routers.

Answer

Configure 'router ospf 1' on both routers, set router-id, and use 'network 10.0.0.0 0.0.0.0 area 0' on both routers.

Question 2

You are connected to R1. R1 has OSPF configured on GigabitEthernet0/0 with network 10.0.0.0 0.0.0.3 area 1, ip ospf hello-interval 10, and ip ospf dead-interval 40. R2 has OSPF configured on its GigabitEthernet0/0 with network 10.0.0.0 0.0.0.3 area 0, ip ospf hello-interval 5, and ip ospf dead-interval 20. Correct these mismatches so that R1 and R2 become OSPF neighbors.

Accepted Answer

On R1, change the network statement to area 0 and set ip ospf hello-interval 5 and ip ospf dead-interval 20 under the interface.. The OSPF adjacency fails due to two mismatches. First, the area is mismatched: R1 uses area 1, R2 uses area 0 (both must be the same area, typically area 0). Second, the hello and dead timers are mismatched: R1 uses Hello 10/Dead 40, R2 uses Hello 5/Dead 20. To fix, on R1 change the network statement to area 0 and adjust timers to match R2 (or vice versa). The solution below changes R1's area to 0 and sets hello to 5 and dead to 20 to match R2.

Answer

On R2, change the network statement to area 1 and set ip ospf hello-interval 10 and ip ospf dead-interval 40 under the interface.

Answer

On R1, change the network statement to area 0 and set ip ospf hello-interval 10 and ip ospf dead-interval 40 under the interface.

Answer

On R2, change the network statement to area 0 and set ip ospf hello-interval 10 and ip ospf dead-interval 40 under the interface.

Question 3

You are connected to R1 via the console. Configure single-area OSPFv2 on R1, R2, and R3 so that all three routers can exchange routes. The current configuration has mismatched hello/dead timers on the link between R1 and R2, and an area mismatch on the link between R2 and R3. Correct these issues and ensure OSPF adjacencies form.

Accepted Answer

On R2, configure interface G0/0 with 'ip ospf hello-interval 10' and 'ip ospf dead-interval 40', and modify the OSPF network statement for 10.0.23.0/30 to area 0.. The adjacency between R1 and R2 fails because R1 has hello/dead timers of 10/40, while R2 has 30/120 on G0/0. The adjacency between R2 and R3 fails because R2's G0/1 is in area 1, but R3's G0/1 is in area 0. On R2, change the hello/dead timers on G0/0 to match R1 (10/40) using 'ip ospf hello-interval 10' and 'ip ospf dead-interval 40'. Also change the network statement for 10.0.23.0/30 to area 0 using 'network 10.0.23.0 0.0.0.3 area 0'. Verify with 'show ip ospf neighbor' on all routers.

Answer

On R2, configure interface G0/0 with 'ip ospf hello-interval 30' and 'ip ospf dead-interval 120', and modify the OSPF network statement for 10.0.23.0/30 to area 1.

Answer

On R1, configure interface G0/0 with 'ip ospf hello-interval 30' and 'ip ospf dead-interval 120', and on R3, change the OSPF network statement for 10.0.23.0/30 to area 1.

Answer

On R1, configure interface G0/0 with 'ip ospf hello-interval 10' and 'ip ospf dead-interval 40', and on R2, modify the OSPF network statement for 10.0.23.0/30 to area 1.

Question 4

You are connected to R1. Configure OSPFv2 on R1 and R2 so that they form a full adjacency and can exchange routes. The current configuration has mismatched hello/dead timers blocking the adjacency. Adjust only the necessary settings on R1 to match R2's OSPF timers.

Accepted Answer

Configure 'ip ospf hello-interval 5' and 'ip ospf dead-interval 20' on R1's GigabitEthernet0/0 interface.. The adjacency between R1 and R2 is not forming because the OSPF hello and dead timers are mismatched. R1 has default timers (Hello 10, Dead 40) while R2 has custom timers (Hello 5, Dead 20). To form an adjacency, OSPF timers must match on both ends. On R1, you need to configure the OSPF interface timers to match R2 by issuing 'ip ospf hello-interval 5' and 'ip ospf dead-interval 20' on interface GigabitEthernet0/0. After applying these commands, the adjacency should come up.

Answer

Configure 'ip ospf hello-interval 10' and 'ip ospf dead-interval 40' on R2's interface to match R1's default timers.

Answer

Configure 'ip ospf hello-interval 5' on R1's GigabitEthernet0/0 interface only; the dead interval will adjust automatically.

Answer

Configure 'ip ospf dead-interval 20' on R1's GigabitEthernet0/0 interface only; the hello interval will adjust automatically.

Question 5

You are connected to R1 via console. R1 and R2 are directly connected via their GigabitEthernet0/0 interfaces. Configure OSPFv3 for IPv6 on both routers so that the loopback0 interface on R2 (with IPv6 address 2001:db8:acad:2::1/64) is reachable from R1. Enable IPv6 unicast routing, enable OSPFv3 on the appropriate interfaces, and verify the neighbor adjacency and routing table. (Note: R2 already has OSPFv3 configured and is waiting for R1 to complete its configuration.)

Accepted Answer

Enable IPv6 unicast routing, configure OSPFv3 process with router-id, enable OSPFv3 on GigabitEthernet0/0 in area 0, and verify neighbor and route.. The issue is that OSPFv3 process is not enabled on R1. To fix, first ensure IPv6 unicast routing is enabled (already done). Then configure OSPFv3 routing process with a process ID (e.g., 1) and router-id using the `ipv6 router ospf 1` command and `router-id` command. Then enable OSPFv3 on the GigabitEthernet0/0 interface with `ipv6 ospf 1 area 0`. Finally, verify with `show ospfv3 neighbor` to see R2's router ID (e.g., 2.2.2.2) and `show ipv6 route ospf` to see the route to 2001:db8:acad:2::/64.

Answer

Enable IPv6 unicast routing, configure OSPFv2 process with router-id, enable OSPFv2 on GigabitEthernet0/0 in area 0, and verify neighbor and route.

Answer

Enable IPv6 unicast routing, configure OSPFv3 process without a router-id, enable OSPFv3 on GigabitEthernet0/0 in area 0, and verify neighbor and route.

Answer

Enable IPv6 unicast routing, configure OSPFv3 process with router-id, enable OSPFv3 on GigabitEthernet0/0 in area 0, but do not verify neighbor or route.

Question 6

You are connected to R1, a router that must establish OSPFv3 adjacency with R2 over the directly connected link G0/0. The current configuration is incomplete: OSPFv3 process is configured but not enabled on the interface, and global IPv6 unicast routing is missing. Configure R1 so that it becomes an OSPFv3 neighbor with R2 and learns the loopback route 2001:db8:1:2::/64 via OSPFv3. Then verify neighbor state and routing table.

Accepted Answer

Enable IPv6 unicast routing globally and activate OSPFv3 on GigabitEthernet0/0 with the command 'ipv6 ospf 1 area 0'.. R1 is missing two critical configurations: global IPv6 unicast routing must be enabled with 'ipv6 unicast-routing', and OSPFv3 must be activated on GigabitEthernet0/0 using 'ipv6 ospf 1 area 0' under the interface. Without these, R1 cannot send or receive OSPFv3 hellos, so no adjacency forms and routes are not exchanged. After applying both commands, the neighbor state becomes FULL and the remote loopback appears in the IPv6 routing table.

Answer

Enable IPv6 unicast routing globally and configure OSPFv3 process 1 with the 'network' command under the OSPFv3 router configuration mode.

Answer

Enable IPv6 unicast routing globally and configure OSPFv3 process 1 with the 'router-id' command to ensure adjacency.

Answer

Enable IPv6 unicast routing globally and configure OSPFv3 process 1 with the 'passive-interface default' command to allow adjacency.

Question 7

You are connected to R1 via console. Configure OSPFv3 for IPv6 on R1 and R2 so that IPv6 loopback interfaces on both routers can communicate. R1's GigabitEthernet0/0 and R2's GigabitEthernet0/1 are directly connected. Ensure OSPFv3 is enabled on the correct interfaces and verify neighbors and routes.

Accepted Answer

Enable OSPFv3 on R1's GigabitEthernet0/0 and Loopback0, and on R2's GigabitEthernet0/1 and Loopback0.. The issue is that OSPFv3 is not enabled on the interfaces. On R1, OSPFv3 must be enabled on GigabitEthernet0/0 (the link to R2) and Loopback0 (to advertise the loopback). On R2, OSPFv3 must be enabled on GigabitEthernet0/1 (the link to R1) and Loopback0. After enabling OSPFv3 on the correct interfaces, the neighbor adjacency forms and routes are exchanged.

Answer

Enable OSPFv3 only on the loopback interfaces of both routers.

Answer

Enable OSPFv3 on R1's GigabitEthernet0/0 and R2's GigabitEthernet0/1 only, without loopbacks.

Answer

Enable OSPFv3 on R1's Loopback0 and R2's GigabitEthernet0/1 only.

Question 8

You are connected to R1. Configure OSPFv3 for IPv6 on R1 and R2 so that the loopback0 interface on R1 (IPv6 address 2001:db8:1::1/64) can ping the loopback0 interface on R2 (IPv6 address 2001:db8:2::1/64). The routers are connected via their GigabitEthernet0/0 interfaces using IPv6 addresses 2001:db8:12::1/64 (R1) and 2001:db8:12::2/64 (R2). OSPFv3 process ID 100 must be used, and all interfaces must be in area 0.

Accepted Answer

R1(config)# ipv6 unicast-routing
R1(config)# ipv6 router ospf 100
R1(config-rtr)# router-id 1.1.1.1
R1(config-rtr)# interface gigabitethernet0/0
R1(config-if)# ipv6 ospf 100 area 0
R1(config-if)# interface loopback0
R1(config-if)# ipv6 ospf 100 area 0

R2(config)# ipv6 unicast-routing
R2(config)# ipv6 router ospf 100
R2(config-rtr)# router-id 2.2.2.2
R2(config-rtr)# interface gigabitethernet0/0
R2(config-if)# ipv6 ospf 100 area 0
R2(config-if)# interface loopback0
R2(config-if)# ipv6 ospf 100 area 0. OSPFv3 for IPv6 requires enabling IPv6 unicast routing globally and configuring OSPFv3 on interfaces. The missing step was enabling OSPFv3 process 100 and assigning area 0 to the interfaces. On R1, the commands 'ipv6 router ospf 100' and 'router-id 1.1.1.1' create the OSPFv3 process, then 'ipv6 ospf 100 area 0' under each interface enables OSPFv3 on those interfaces. Similar commands on R2 with a unique router-id complete the configuration. Verification with 'show ospfv3 neighbor' should show R2's router-id, and 'show ipv6 route ospf' should display the remote loopback network.

Answer

R1(config)# ipv6 unicast-routing
R1(config)# ipv6 router ospf 100
R1(config-rtr)# router-id 1.1.1.1
R1(config-rtr)# network 2001:db8:12::0/64 area 0
R1(config-rtr)# network 2001:db8:1::0/64 area 0

R2(config)# ipv6 unicast-routing
R2(config)# ipv6 router ospf 100
R2(config-rtr)# router-id 2.2.2.2
R2(config-rtr)# network 2001:db8:12::0/64 area 0
R2(config-rtr)# network 2001:db8:2::0/64 area 0

Answer

R1(config)# ipv6 unicast-routing
R1(config)# ipv6 router ospf 100
R1(config-rtr)# router-id 1.1.1.1
R1(config-rtr)# interface gigabitethernet0/0
R1(config-if)# ipv6 ospf 100 area 0

R2(config)# ipv6 unicast-routing
R2(config)# ipv6 router ospf 100
R2(config-rtr)# router-id 2.2.2.2
R2(config-rtr)# interface gigabitethernet0/0
R2(config-if)# ipv6 ospf 100 area 0

Answer

R1(config)# ipv6 unicast-routing
R1(config)# ipv6 router ospf 100
R1(config-rtr)# router-id 1.1.1.1
R1(config-rtr)# interface gigabitethernet0/0
R1(config-if)# ipv6 ospf 100 area 0
R1(config-if)# interface loopback0
R1(config-if)# ipv6 ospf 100 area 0

R2(config)# ipv6 unicast-routing
R2(config)# ipv6 router ospf 100
R2(config-rtr)# router-id 1.1.1.1
R2(config-rtr)# interface gigabitethernet0/0
R2(config-if)# ipv6 ospf 100 area 0
R2(config-if)# interface loopback0
R2(config-if)# ipv6 ospf 100 area 0

Question 9

You are connected to R1. Configure OSPFv3 for IPv6 so that R1 and R2 can exchange IPv6 routes over their directly connected link. Enable IPv6 routing, assign OSPFv3 process and area on the interface, and verify that the neighbor adjacency forms and routes appear in the IPv6 routing table.

Accepted Answer

Enable IPv6 routing with 'ipv6 unicast-routing', configure OSPFv3 on the interface with 'ipv6 ospf 1 area 0', and verify with 'show ospfv3 neighbor' and 'show ipv6 route ospf'.. It includes enabling IPv6 routing with 'ipv6 unicast-routing', applying OSPFv3 to the interface using 'ipv6 ospf 1 area 0', and verifying with the correct OSPFv3-specific commands 'show ospfv3 neighbor' and 'show ipv6 route ospf'. Option B is incorrect because it adds a global 'router ospfv3 1' command, which is unnecessary; OSPFv3 can be configured directly on the interface without a global process. Option C is incorrect because it uses IPv4 OSPF verification commands 'show ip ospf neighbor' and 'show ip route ospf', which are not valid for OSPFv3. Option D is incorrect because although it uses the correct 'show ospfv3 neighbor', the 'show ipv6 route' command does not filter to OSPF-learned routes, so it displays all IPv6 routes rather than just OSPF routes.

Answer

Enable IPv6 routing with 'ipv6 unicast-routing', configure OSPFv3 globally with 'router ospfv3 1' and 'router-id 1.1.1.1', then assign the interface to area 0 with 'ipv6 ospf 1 area 0'.

Answer

Enable IPv6 routing with 'ipv6 unicast-routing', configure OSPFv3 on the interface with 'ipv6 ospf 1 area 0', and verify with 'show ip ospf neighbor' and 'show ip route ospf'.

Answer

Enable IPv6 routing with 'ipv6 unicast-routing', configure OSPFv3 on the interface with 'ipv6 ospf 1 area 0', and verify with 'show ospfv3 neighbor' and 'show ipv6 route'.

Question 10

You are connected to R1 via console. Configure OSPFv3 for IPv6 on both R1 and R2 so that the loopback0 interface on R2 (IPv6 address 2001:db8:1:2::1/64) is reachable from R1. The link between R1 and R2 uses the subnet 2001:db8:1:1::/64 with R1's G0/0 having IPv6 address 2001:db8:1:1::1/64 and R2's G0/0 having 2001:db8:1:1::2/64. OSPFv3 process ID must be 100 and all interfaces must be in area 0. After configuration, verify OSPFv3 neighbors and the IPv6 route to the loopback0 network.

Accepted Answer

On R1: ipv6 router ospf 100, router-id 1.1.1.1, interface g0/0: ipv6 ospf 100 area 0. On R2: ipv6 router ospf 100, router-id 2.2.2.2, interface g0/0: ipv6 ospf 100 area 0, interface loopback0: ipv6 ospf 100 area 0.. OSPFv3 is enabled per-interface using the 'ipv6 ospf area ' command; there is no 'network' statement under the OSPFv3 process like in OSPFv2. To make the loopback reachable, the loopback interface must also be enabled for OSPFv3 in area 0. Option A correctly configures both routers with process ID 100, area 0, and includes the loopback on R2.

Answer

On R1: ipv6 router ospf 100, router-id 1.1.1.1, interface g0/0: ipv6 ospf 100 area 0. On R2: ipv6 router ospf 100, router-id 2.2.2.2, interface g0/0: ipv6 ospf 100 area 0. No configuration on loopback0.

Answer

On R1: ipv6 router ospf 100, router-id 1.1.1.1, interface g0/0: ipv6 ospf 100 area 0. On R2: ipv6 router ospf 100, router-id 2.2.2.2, interface g0/0: ipv6 ospf 100 area 0, interface loopback0: ipv6 ospf 100 area 0, and also configure 'network 2001:db8:1:2::/64 area 0' under the OSPFv3 process.

Answer

On R1: ipv6 router ospf 100, router-id 1.1.1.1, interface g0/0: ipv6 ospf 100 area 0. On R2: ipv6 router ospf 100, router-id 2.2.2.2, interface g0/0: ipv6 ospf 100 area 0, interface loopback0: ipv6 ospf 100 area 0, and also configure 'passive-interface GigabitEthernet0/0' under the OSPFv3 process.

Question 11

You are connected to R1. Configure HSRP so that R1 becomes the active router for VLAN 10, with a virtual IP of 192.168.10.1. Ensure that R1 preempts if it comes back online after a failure. Also, configure R1 to decrement its HSRP priority by 20 if its GigabitEthernet0/1 interface goes down. The current configuration shows both routers as active — identify and fix the issues.

Accepted Answer

Change the virtual IP to 192.168.10.1, set priority to 110, enable preempt, and track interface GigabitEthernet0/1 with decrement 20.. The scenario indicates both routers appear as Active, which is abnormal. This could result from a misconfigured virtual IP or group number mismatch. The required fix is to set the virtual IP to 192.168.10.1, assign R1 a higher priority (110 vs R2's default 100), enable preempt so R1 reclaims active role after failure, and track GigabitEthernet0/1 with a decrement of 20 to lower priority if that interface goes down.

Answer

Change the virtual IP to 192.168.10.1, set priority to 100, enable preempt, and track interface GigabitEthernet0/1 with decrement 20.

Answer

Change the virtual IP to 192.168.10.254, set priority to 110, enable preempt, and track interface GigabitEthernet0/1 with decrement 20.

Answer

Change the virtual IP to 192.168.10.1, set priority to 110, enable preempt, but do not track any interface.

Question 12

You are connected to R1. Configure HSRP on R1 and R2 so that R1 is the active gateway for VLAN 100 with a virtual IP of 192.0.2.254. R1 should preempt and track its G0/1 interface to decrement priority by 20 if it goes down. Currently, both routers show active for the group, and the virtual IP is incorrectly set. Troubleshoot and fix the configuration on R1 only.

Accepted Answer

Change the virtual IP to 192.0.2.254 and set priority to 110.. The issue is that both routers are active because the virtual IP on R1 was 192.168.100.254, which is not in the same subnet as the interface IP (192.0.2.1/24), so HSRP couldn't form a common group. Changing the virtual IP to 192.0.2.254 fixes the subnet mismatch. Additionally, setting R1's priority to 110 ensures it becomes the active router because it has preempt configured, and the higher priority overrides R2's default 100. The track command remains correct as it reduces priority if G0/1 fails.

Answer

Change the virtual IP to 192.0.2.254 and remove the track command.

Answer

Change the virtual IP to 192.0.2.254 and configure preempt on R2.

Answer

Change the virtual IP to 192.0.2.254 and set priority to 100.

Question 13

You are connected to R1. The network requires HSRP for default gateway redundancy on subnet 192.168.1.0/24. R2 should be the active router, and R1 the standby. Currently, both routers show as active. Configure R1 with priority 90, enable preempt, ensure the virtual IP is 192.168.1.254, and configure tracking of interface GigabitEthernet0/1 (subnet 203.0.113.0/30) so that if R1's tracked interface goes down, its priority decreases by 20. Verify the final state with 'show standby brief'.

Accepted Answer

interface GigabitEthernet0/0
 standby version 2
 standby 1 ip 192.168.1.254
 standby 1 priority 90
 standby 1 preempt
 standby 1 track GigabitEthernet0/1 20. The scenario requires R2 to be the HSRP active router. By default, both routers have priority 100, and HSRP election would select the router with the higher IP address as active if priorities are equal. To ensure R2 becomes active, R1's priority must be lowered to 90. Additionally, tracking interface GigabitEthernet0/1 with a decrement of 20 is configured so that if R1's uplink fails, its priority drops to 70, further preventing it from becoming active. The correct configuration on R1 sets priority 90, enables preempt, and tracks the correct interface with decrement 20. Options B, C, and D are wrong because: B sets a higher priority (110) which would make R1 active; C uses an incorrect decrement of 30; and D tracks the wrong interface (Gig0/0 instead of Gig0/1).

Answer

interface GigabitEthernet0/0
 standby version 2
 standby 1 ip 192.168.1.254
 standby 1 priority 110
 standby 1 preempt
 standby 1 track GigabitEthernet0/1 20

Answer

interface GigabitEthernet0/0
 standby version 2
 standby 1 ip 192.168.1.254
 standby 1 priority 90
 standby 1 preempt
 standby 1 track GigabitEthernet0/1 30

Answer

interface GigabitEthernet0/0
 standby version 2
 standby 1 ip 192.168.1.254
 standby 1 priority 90
 standby 1 preempt
 standby 1 track GigabitEthernet0/0 20

Question 14

You are connected to R1, a multilayer switch acting as an HSRP active gateway for VLAN 100. The network requires R1 to be the active router with a virtual IP of 192.168.100.1. Currently, both R1 and the peer router R2 show as active in 'show standby brief', and the virtual IP is misconfigured. Configure HSRP on R1 to fix these issues: set priority to 110, enable preempt, correct the virtual IP, and track interface GigabitEthernet0/1 (decrement priority by 20 if it goes down).

Accepted Answer

interface Vlan100
 standby 100 ip 192.168.100.1
 standby 100 priority 110
 standby 100 preempt
 standby 100 track GigabitEthernet0/1 20. The problem had multiple issues: the virtual IP was wrong (192.168.100.254 instead of 192.168.100.1), preempt was not enabled (both routers could claim active), and priority was default (100). Additionally, interface tracking was missing to decrement priority if the upstream link failed. The solution consists of four commands: 'standby 100 ip 192.168.100.1' to set the correct virtual IP, 'standby 100 priority 110' to make R1 the active router, 'standby 100 preempt' to allow R1 to reclaim active role after recovery, and 'standby 100 track GigabitEthernet0/1 20' to reduce priority by 20 if that interface goes down.

Answer

interface Vlan100
 standby 100 ip 192.168.100.254
 standby 100 priority 110
 standby 100 preempt
 standby 100 track GigabitEthernet0/1 20

Answer

interface Vlan100
 standby 100 ip 192.168.100.1
 standby 100 priority 100
 standby 100 preempt
 standby 100 track GigabitEthernet0/1 20

Answer

interface Vlan100
 standby 100 ip 192.168.100.1
 standby 100 priority 110
 standby 100 track GigabitEthernet0/1 20

Question 15

You are troubleshooting connectivity from R1 to the 203.0.113.0/24 network. R1 is a multilayer switch running routed ports. Currently, R1 has two paths to reach that network: one via R2 (192.0.2.2) and one via R3 (198.51.100.2). The path via R2 is preferred, but after a link failure between R1 and R2, traffic should automatically fail over to the R3 path. However, after the failure, traffic is still being sent to R2. Examine the routing table and configuration, then fix the issue so that the floating static route takes over correctly when the primary route is lost.

Accepted Answer

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. The issue is that the primary static route to 203.0.113.0/24 via 192.0.2.2 has an administrative distance of 1 (default), and the backup floating static route via 198.51.100.2 has an AD of 200. When the next-hop interface (Gi1/0/1) goes down, the route via 192.0.2.2 should be removed from the routing table because its next-hop is unreachable. However, the show output indicates that the route remains, which suggests that the static route is configured with the 'permanent' keyword or that the next-hop is still considered reachable via some other mechanism (e.g., a recursive lookup to a still-active route). In this case, the most common fix is to add the 'track' option or to remove the static route and re-add it without the 'permanent' keyword, or to ensure that the static route uses an interface instead of just an IP address. The correct solution is to replace the primary static route with one that uses an exit interface, so that the route is automatically removed when the interface goes down. For example: 'ip route 203.0.113.0 255.255.255.0 GigabitEthernet1/0/1 192.0.2.2'. This causes the route to be directly dependent on the interface state.

Answer

Increase the administrative distance of the floating static route to 255

Answer

Add the permanent keyword to the floating static route

Answer

Change the administrative distance of the primary static route to 200 and the floating static route to 1

CCNA IP Routing Practice Test 22 — 15 Questions

Exhibit

CCNA IP Routing Practice Test 22 — 15 Questions

Exhibit