A parks department installs a floating static default toward LTE failover that must stay out of the RIB while the primary fiber-learned route remains valid. How should the floating static be designed?
Select an answer to reveal the explanation.
Short Explanation
A floating static is the spare tire bolted under the truck—present, but not rolling until the good tire is gone. Give it a worse (higher) AD than fiber’s route and it stays dormant. Lower AD would make LTE the daily driver, which nobody wants.
Full Explanation
A floating static uses a deliberately worse administrative distance than the preferred dynamic (or primary static) route so it remains inactive until the primary is withdrawn. Setting a lower AD or injecting a better IGP metric defeats the failover intent. Tracking can refine withdrawal conditions but the core pattern is higher AD than the winning primary source.