200-301 Question #1633: Real Exam Question with Answer & Explanation

Question

Lab Simulation 45 Guidelines This is a lab item in which tasks will be performed on virtual devices. - Refer to the Tasks tab to view the tasks for this lab item. - Refer to the Topology tab to access the device console(s) and perform the tasks. - Console access is available for all required devices by clicking the device icon or using the tab(s) above the console window. - All necessary preconfigurations have been applied. - Do not change the enable password or hostname for any device. - Save your configurations to NVRAM before moving to the next item. - Click Next at the bottom of the screen to submit this lab and move to the next question. - When Next is clicked, the lab doses and cannot be reopened. Topology Tasks Task 1 - Configure a static default route on R5 per the topology. - Configure a static default route on R1, preferring the path through R2 towards R6. - From R5, use traceroute and ping to verify the path towards and reachability of R6. Task 2 - Configure a floating static default route on R1, preferring the path through R3 towards R6 if the link to R2 should fail. - Configure the administrative distance for 200. - Configure a static route on R3 to forward the return traffic towards 10.100.110.0/25. - After shutting interface e0/0 on R1, use traceroute and ping from R5 to verify path towards and reachability of R6. Answer: See the below explanation

Options

• taskConfigure static default routes on R5 and R1 (preferring R2 towards R6). Verify reachability from R5 to R6. Configure a floating static default route on R1 (preferring R3 towards R6 if R2 fails) with an administrative distance of 200. Configure a static route on R3 for return traffic. Simulate a link failure on R1 and verify path and reachability from R5 to R6 again.
• prerequisitesAccess to virtual network device consoles (R1, R3, R5); all necessary preconfigurations applied.

Explanation

This lab simulation tests the ability to configure static and floating static default routes to control traffic paths and provide redundancy. The correct approach involves configuring a standard static default route on R5 pointing to R1, a primary static default route on R1 via R2 (default AD of 1), a floating static default route on R1 via R3 with AD of 200 (so it only activates when the primary route via R2 fails), and a return static route on R3 so bidirectional communication is maintained. The floating static route with AD 200 is the key mechanism - it remains inactive in the routing table as long as the lower-AD primary route exists, but automatically installs when the R2 link goes down, providing seamless failover verified via traceroute and ping from R5 to R6.

No community discussion yet for this question.