A school district steers a floating static default via a primary Metro path and must withdraw it when that path fails end-to-end. Which feature pairing drives that change?
Select an answer to reveal the explanation.
Short Explanation
A floating static is a spare tire—you want it to mount itself when the road ahead is closed. IP SLA pings the far side; tracking flips the route (or FHRP) when the echo fails. That beats waiting for the help desk to notice.
Full Explanation
IP SLA generates synthetic probes; object tracking consumes reachability state to install or withdraw routes and to influence FHRP priority. Binding a tracked object to a floating static provides automated failover when the primary path fails beyond the local interface. Manual AD changes or SNMP-only awareness lack automated control-plane reaction.