CCNA IP Routing Practice Test 20 — 15 Questions

Question 1

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'.. Option A is correct because 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 2

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.. To achieve reachability to R2's loopback, OSPFv3 must be enabled on R1's and R2's G0/0 interfaces in area 0, and on R2's loopback0 so its prefix is advertised. Option A shows the minimal correct configuration. Option B omits enabling OSPF on loopback0, so the route to 2001:db8:1:2::/64 is not advertised. Option C incorrectly uses the 'network' command, which is not supported in OSPFv3; OSPFv3 relies on interface-level 'ipv6 ospf ... area' commands. Option D adds 'passive-interface GigabitEthernet0/0', which prevents OSPF from forming a neighbor adjacency on the link, breaking the required connectivity.

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 3

You are connected to R1. The network must route IPv6 traffic between two directly connected routers using OSPFv3. Configure OSPFv3 on R1's GigabitEthernet0/0 interface in area 0, enable IPv6 unicast routing, and verify that R1 forms an OSPFv3 neighbor adjacency with R2 and learns the remote network 2001:DB8:CAFE:2::/64 via OSPFv3.

Accepted Answer

Enable OSPFv3 on the interface with 'ipv6 ospf 1 area 0' under GigabitEthernet0/0.. The issue is that OSPFv3 is not enabled on R1's GigabitEthernet0/0 interface, and the OSPFv3 routing process has not been started. To fix this, first ensure ipv6 unicast-routing is already enabled (it is). Then configure the OSPFv3 process with a process ID (e.g., 1) and enable OSPFv3 on the interface in area 0 using the command 'ipv6 ospf 1 area 0' under the interface. After that, R1 will form a neighbor adjacency with R2 and learn the remote route.

Answer

Configure 'ipv6 router ospf 1' and then 'network 2001:DB8:CAFE:1::/64 area 0' under the OSPFv3 process.

Answer

Enable OSPFv3 on the interface with 'ipv6 ospf 1 area 0' under the OSPFv3 router configuration mode.

Answer

Configure 'ipv6 unicast-routing' and then 'ipv6 ospf 1 area 0' under the interface.

Question 4

You are connected to R1. Configure OSPFv3 for IPv6 on R1 and R2 so that they can exchange IPv6 routes. R1's GigabitEthernet0/0 is connected to R2's GigabitEthernet0/0. R1 has a loopback0 with IPv6 address 2001:db8:1::1/32, and R2 has a loopback0 with IPv6 address 2001:db8:2::2/32. Ensure OSPFv3 is enabled on both routers, the link interfaces are in area 0, and R1 learns the loopback route from R2.

Accepted Answer

Configure 'ipv6 ospf 1 area 0' under GigabitEthernet0/0 and Loopback0 on both routers.. The provided configuration enables OSPFv3 on the interfaces, which is necessary, but it does not set a router-id. OSPFv3 requires a router-id to form adjacencies. Without any IPv4 addresses configured, the router-id defaults to 0.0.0.0, preventing neighbor formation and route exchange. Therefore, a valid solution must also include a router-id command under the OSPFv3 process (e.g., 'ipv6 router ospf 1' followed by 'router-id X.X.X.X').

Answer

Configure 'ipv6 router ospf 1' and then 'network 2001:db8:2::2/32 area 0' under the OSPFv3 process.

Answer

Configure 'ipv6 unicast-routing' and 'ipv6 ospf 1 area 0' under the global configuration.

Answer

Configure 'router ospf 1' and then 'ipv6 unicast-routing' under the OSPFv3 process.

Question 5

You are connected to R1. The network uses HSRP to provide first-hop redundancy for VLAN 10 clients. R1 should be the active router with a priority of 150, preempt enabled, and should track interface GigabitEthernet0/1 (decrement priority by 20 if it goes down). The virtual IP is 192.168.10.254. Currently, both routers are active for the same group. Fix the configuration on R1 so that it becomes the active router and preempts when possible.

Accepted Answer

interface Vlan10
 standby 10 ip 192.168.10.254
 standby 10 priority 150
 standby 10 preempt
 standby 10 track GigabitEthernet0/1 20. Both routers are active for HSRP group 10 because the virtual IP address is not configured or is mismatched, causing a split-brain scenario. The correct fix must include setting the virtual IP with 'standby 10 ip 192.168.10.254', raising R1's priority to 150, enabling preempt, and tracking GigabitEthernet0/1 with a decrement of 20. Option A supplies all required commands with proper syntax. Other options either omit the vital IP configuration or have invalid keywords like 'decrement' or 'preempt delay'.

Answer

interface Vlan10
 standby 10 ip 192.168.10.254
 standby 10 priority 150
 standby 10 preempt
 standby 10 track GigabitEthernet0/1 20 decrement

Answer

interface Vlan10
 standby 10 ip 192.168.10.254
 standby 10 priority 150
 standby 10 preempt delay 20
 standby 10 track GigabitEthernet0/1

Answer

interface Vlan10
 standby 10 ip 192.168.10.254
 standby 10 priority 150
 standby 10 preempt
 standby 10 track GigabitEthernet0/1 20 priority

Question 6

You are connected to R1. The network uses HSRP for default gateway redundancy. Currently, both routers R1 and R2 are in the 'Active' state for HSRP group 10, causing traffic issues. Configure HSRP on R1 so that it becomes the Active router with a priority of 150, preempt enabled, a virtual IP of 192.168.1.254, and track interface GigabitEthernet0/1 so that if it goes down, the priority decrements by 20. Then verify the configuration with 'show standby brief'.

Accepted Answer

standby 10 ip 192.168.1.254
standby 10 priority 150
standby 10 preempt
standby 10 track GigabitEthernet0/1 20. The required HSRP configuration consists of all four commands: virtual IP, priority 150, preempt, and tracking with a decrement of 20. Option A lists them correctly. Option B fails because the track command is missing the decrement value. Option C is incorrect because it omits the 'standby 10 preempt' command; without preempt, the router will not take over the active role even when its priority is higher. Option D uses a decrement of 10 instead of 20, which does not meet the requirement.

Answer

standby 10 ip 192.168.1.254
standby 10 priority 150
standby 10 preempt
standby 10 track GigabitEthernet0/1

Answer

standby 10 ip 192.168.1.254
standby 10 priority 150
standby 10 track GigabitEthernet0/1 20

Answer

standby 10 ip 192.168.1.254
standby 10 priority 150
standby 10 preempt
standby 10 track GigabitEthernet0/1 10

Question 7

You are connected to R1 via the console. R1 and R2 are running HSRP for the VLAN 10 subnet 192.168.10.0/24. Currently both routers are active for group 10, causing instability. Configure R1 so that it becomes the active router when its G0/0 interface is up, and R2 takes over only if R1's G0/0 fails. Also correct the virtual IP address to 192.168.10.1. Verify with show standby brief.

Accepted Answer

On R1: interface GigabitEthernet0/0, standby 10 ip 192.168.10.1, standby 10 preempt, standby 10 track GigabitEthernet0/0 decrement 60. On R2: standby 10 preempt.. The dual-active state was caused by R1 having an incorrect virtual IP address (192.168.10.254 instead of 192.168.10.1), making it active for a different HSRP group. Correcting the VIP to 192.168.10.1 on R1 aligns both routers to the same group. Enabling preempt on R2 (and it should already be enabled on R1) allows R1 to reclaim the active role after the VIP correction. Additionally, interface tracking with a decrement of 60 ensures that if R1's G0/0 fails, R1's priority drops below 100, allowing R2 to take over.

Answer

On R1: interface GigabitEthernet0/0, standby 10 ip 192.168.10.1, standby 10 preempt, standby 10 track GigabitEthernet0/0 decrement 10. On R2: no additional configuration.

Answer

On R1: interface GigabitEthernet0/0, standby 10 ip 192.168.10.1, standby 10 preempt, standby 10 track GigabitEthernet0/0 decrement 60. On R2: no additional configuration.

Answer

On R1: interface GigabitEthernet0/0, standby 10 ip 192.168.10.254, standby 10 preempt, standby 10 track GigabitEthernet0/0 decrement 60. On R2: standby 10 preempt.

Question 8

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 9

You are connected to R1. Configure HSRP on interface GigabitEthernet0/0 so that R1 becomes the active router for group 10 with a virtual IP of 192.0.2.254/24. Ensure that R1 preempts if it regains a higher priority, and track interface GigabitEthernet0/1 to decrement priority by 20 if it goes down. Additionally, troubleshoot the current configuration: both routers are showing as active for group 11 with virtual IP 203.0.113.1, which is incorrect — the virtual IP should be 203.0.113.254 for group 11.

Accepted Answer

interface GigabitEthernet0/0
 standby 10 ip 192.0.2.254
 standby 10 preempt
 standby 10 track GigabitEthernet0/1 20
 interface GigabitEthernet0/0
 standby 11 ip 203.0.113.254
 standby 11 preempt. Both routers showing active for group 11 indicates a mismatch in the virtual IP address or missing preempt. To fix group 11, correct the virtual IP to 203.0.113.254 with 'standby 11 ip 203.0.113.254'. Add preempt with 'standby 11 preempt' to break the tie. For group 10, to ensure R1 becomes active, you must configure preempt ('standby 10 preempt') and interface tracking ('standby 10 track GigabitEthernet0/1 20'). However, with default priority, R1 might not become active if R2's interface IP is higher; therefore, a priority command like 'standby 10 priority 110' may be necessary. The options shown do not include that priority command, so in practice the configuration is incomplete.

Answer

interface GigabitEthernet0/0
 standby 10 ip 192.0.2.254
 standby 10 preempt
 standby 10 track GigabitEthernet0/1 20
 interface GigabitEthernet0/0
 standby 11 ip 203.0.113.254

Answer

interface GigabitEthernet0/0
 standby 10 ip 192.0.2.254
 standby 10 track GigabitEthernet0/1 20
 interface GigabitEthernet0/0
 standby 11 ip 203.0.113.254
 standby 11 preempt

Answer

interface GigabitEthernet0/0
 standby 10 ip 192.0.2.254
 standby 10 preempt
 standby 10 track GigabitEthernet0/1 20
 interface GigabitEthernet0/0
 standby 11 ip 203.0.113.1
 standby 11 preempt

Question 10

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 11

You are connected to R1 via the console. The routers R1 and R2 are directly connected using their GigabitEthernet0/0 interfaces, which are in VLAN 100 and use subnet 192.168.1.0/24. Both routers are currently showing as active for HSRP group 10. Configure HSRP on R1's GigabitEthernet0/0 to become the active router (priority 150, preempt enabled, virtual IP 192.168.1.254). Ensure that if R1's GigabitEthernet0/1 WAN interface goes down, its HSRP priority decrements by 30 so that R2 can take over. Also, correct any existing misconfiguration in the HSRP setup.

Accepted Answer

Configure: interface GigabitEthernet0/0, standby 10 ip 192.168.1.254, standby 10 priority 150, standby 10 preempt, standby 10 track GigabitEthernet0/1 decrement 30. Also, ensure preempt is enabled on R1 (currently missing) and correct any duplicate virtual IP.. Both routers showing as active means either R2 has an equal or higher priority or preempt is missing, preventing a single active election. To fix this, on R1's GigabitEthernet0/0 interface, set standby priority 150 with preempt enabled. Add tracking of GigabitEthernet0/1 with decrement 30 so the priority drops to 120 if the WAN link fails, allowing R2 to become active. The existing misconfiguration is that preempt is either absent or disabled, causing a split-brain scenario; this solution makes R1 the active router and provides correct failover.

Answer

Configure: interface GigabitEthernet0/0, standby 10 ip 192.168.1.254, standby 10 priority 150, standby 10 preempt, standby 10 track GigabitEthernet0/1 decrement 30. No other changes needed because preempt is already enabled.

Answer

Configure: interface GigabitEthernet0/0, standby 10 ip 192.168.1.254, standby 10 priority 150, standby 10 preempt, standby 10 track GigabitEthernet0/1 decrement 30. Also, change the virtual IP to 192.168.1.1 because the current one is wrong.

Answer

Configure: interface GigabitEthernet0/0, standby 10 ip 192.168.1.254, standby 10 priority 150, standby 10 preempt, standby 10 track GigabitEthernet0/1 decrement 30. Also, remove the standby 10 track command from R2 to prevent conflicts.

Question 12

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 13

You are connected to R1, which is part of an HSRP group with R2. The current configuration has both routers active for the same virtual IP, causing instability. Configure R1 with a higher priority, enable preempt, and set the virtual IP to 192.168.1.1. Also, configure interface tracking so that if R1's G0/1 goes down, its priority decreases by 15. Verify with 'show standby brief'.

Accepted Answer

On R1, configure: standby 1 priority 110, standby 1 preempt, standby 1 ip 192.168.1.1, and standby 1 track GigabitEthernet0/1 15. The current configuration does not cause both routers to be Active; rather, R2 is likely the Active router because both have default priority (100) and no preempt, so R2 with the higher interface IP (192.168.1.3) wins the election. To ensure R1 becomes Active, set its priority to 110 and enable preempt. Also correct the virtual IP to 192.168.1.1. Interface tracking on G0/1 with a decrement of 15 ensures R1 yields to R2 if its tracked interface fails. Option A correctly applies all these settings. Option B uses the wrong virtual IP (192.168.1.254). Option C uses the wrong decrement value (10). Option D uses default priority (100), which will not make R1 the Active router if R2 retains default priority and higher IP.

Answer

On R1, configure: standby 1 priority 110, standby 1 preempt, standby 1 ip 192.168.1.254, and standby 1 track GigabitEthernet0/1 15

Answer

On R1, configure: standby 1 priority 110, standby 1 preempt, standby 1 ip 192.168.1.1, and standby 1 track GigabitEthernet0/1 10

Answer

On R1, configure: standby 1 priority 100, standby 1 preempt, standby 1 ip 192.168.1.1, and standby 1 track GigabitEthernet0/1 15

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 20 — 15 Questions

Exhibit

CCNA IP Routing Practice Test 20 — 15 Questions

Exhibit