Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
Used with a floating static route
Used to adjust HSRP priority
Used with policy-based routing
mediumMatching
IP SLA Tracking Objects: Applications in Static Routes, HSRP, and PBR
Drag and drop each IP SLA tracking object on the left to its application on the right.
Quick Answer
The correct answer is that the IP SLA tracking object is used to trigger event-based actions, such as adjusting a floating static route or modifying HSRP priority. This works because IP SLA generates continuous probes—like ICMP echo or HTTP requests—to monitor the reachability of a remote destination, and the tracking object ties the probe’s up/down state to a specific action. When the tracked object goes down, the associated application (e.g., a static route with a higher administrative distance or an HSRP priority decrement) is activated, enabling dynamic failover or path selection. On the ENCOR 350-401 exam, this concept often appears in drag-and-drop tasks where you must match tracking objects to their correct use cases, such as using a threshold-based track to trigger an event rather than simply reporting state. A common trap is confusing the track object itself (which monitors) with the action it triggers; remember that the tracking object is the trigger, not the result. Memory tip: think of IP SLA tracking as a “watchdog” that barks (triggers an event) when the path goes silent.
⚠ Common exam trap
Some candidates might mistakenly think that delay or threshold are valid IP SLA tracking objects, but only state and reachability are standard.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
track ip sla reachability: Used with a floating static route
IP SLA tracking uses only two standard object types: 'track ip sla <id> state' and 'track ip sla <id> reachability'. 'track ip sla <id> delay' and 'track ip sla <id> threshold' are not valid tracking objects. P1, P2, and P3 correctly map to their applications: reachability for floating static routes, state for adjusting HSRP priority, and reachability for policy-based routing. P4 and P5 are incorrect because the specified tracking objects do not exist.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
track ip sla reachability: Used with a floating static route
Why this is correct
Correct. 'track ip sla reachability' is used to monitor reachability for a floating static route.
- ✓
track ip sla 1 state: Used to adjust HSRP priority
Why this is correct
Correct. 'track ip sla 1 state' is used to adjust HSRP priority based on the state of the IP SLA operation.
- ✓
track ip sla 1 reachability: Used with policy-based routing
Why this is correct
Correct. 'track ip sla 1 reachability' is used with policy-based routing to influence traffic forwarding.
- ✗
track ip sla 1 delay: Used to debounce state changes
Why it's wrong here
Incorrect. 'track ip sla 1 delay' is not a valid IP SLA tracking object. The valid objects are state and reachability.
- ✗
track ip sla 1 threshold: Used to trigger event-based actions
Why it's wrong here
Incorrect. 'track ip sla 1 threshold' is not a valid IP SLA tracking object. It does not exist in Cisco IOS.
Go deeper
Related to this question
Key term
High Availability in Enterprise Networks
High Availability in Enterprise Networks is the design principle that ensures network services remain accessible and operational with minimal downtime, even when individual components fail.
Key term
First Hop Redundancy Protocol
A First Hop Redundancy Protocol provides automatic backup for the default gateway router on a network so that devices keep working if the primary router fails.
About these practice questions
Courseiva writes every 350-401 question from scratch — 1,923 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on 350-401
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which two statements about IP SLA with object tracking are true? (Choose two.)
medium- ✓ A.A tracking object can monitor the state of an IP SLA operation and change state when the operation fails.
- ✓ B.The 'track' command is used to create a tracking object that references an IP SLA operation by its operation number.
- C.Object tracking can only be used with static routes, not with dynamic routing protocols like EIGRP or OSPF.
- D.The tracking object automatically modifies the routing table when the IP SLA operation fails.
- E.An IP SLA operation can be configured after the tracking object that references it.
Why A: Option A is correct because a track object tied to an IP SLA operation (via 'track 1 ip sla 1 reachability' or 'state') polls that operation's return code and transitions the object between Up and Down when the probe fails or recovers, which is the core purpose of IP SLA object tracking. Option B is correct because the 'track' command creates the tracking object and references the IP SLA operation by its operation number (for example, 'track 1 ip sla 1'), linking the tracker to that specific probe. Option C is wrong because tracked objects can be referenced by static routes, policy-based routing, HSRP/VRRP, and dynamic routing protocols such as EIGRP or OSPF to influence their behavior. Option D is wrong because the tracking object only changes its own Up/Down state and notifies clients; it does not itself edit the routing table, since the referencing route or protocol must be configured to react to the tracker. Option E is wrong because the IP SLA operation must already exist before the tracking object can reference it by number, so the operation cannot be configured afterward.
Variation 2. Drag and drop each IP SLA tracking object on the left to its application on the right.
medium- ✓ P1.tracked static route: Install or remove a static route
- ✓ P2.tracked HSRP: Adjust HSRP priority
- ✓ P3.tracked PBR: Change policy routing
- ✓ P4.tracked VRRP: Adjust VRRP priority
- ✓ P5.tracked GLBP: Adjust GLBP weighting
Why P1: Static route uses tracking to install or remove a route; HSRP uses tracking to adjust priority; PBR uses tracking to change policy routing; VRRP uses tracking for priority; GLBP uses tracking for weighting.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 350-401 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-401 exam.