A network administrator intends to deploy a floating static route on router R1 as a backup path for the internal network . The primary path to this destination is currently learned through internal EIGRP (default Administrative Distance of ). During initial testing, the administrator notices that traffic destined for is immediately taking the static backup path across interface GigabitEthernet0/2, even though the primary EIGRP neighbor relationship remains active and healthy. Which two issues could cause the static route to be preferred over the active EIGRP route? (Select TWO.)
- The administrator configured the floating static route with an Administrative Distance of .Answer
- The static route was configured using a destination prefix of instead of .Answer
- CThe administrator configured the floating static route with an Administrative Distance of .
- DThe EIGRP composite metric for the primary path was higher than the default metric assigned to the static route.
Answer
The static route is preferred over the primary EIGRP route if the static route was configured with an Administrative Distance of 80 (which is lower than EIGRP's default Administrative Distance of 90) or if the static route was configured with a more specific subnet mask of /25 (which takes precedence due to the Longest Prefix Match rule).
A floating static route functions as a backup path only when its Administrative Distance (AD) is strictly higher than that of the primary routing protocol (internal EIGRP default AD = 90). Configuring an AD of 80 causes the static route to preempt EIGRP. Additionally, routers prioritize routes based on Longest Prefix Match before AD; configuring a /25 route creates a more specific entry than the /24 EIGRP route, forcing traffic onto the static path.
Step-by-Step Solution
Key Concept
Floating Static Route Administration and Prefix Matching
Estimated Time:1m 30s