mediumMultiple Choice
300-410 Practice Question: Configured IP SLA 30 to monitor the reachability…
A network engineer configured IP SLA 30 to monitor the reachability of a server (10.10.10.10) using ICMP echo probes. The IP SLA is linked to a track object that is used in a static default route. The engineer notices that the IP SLA state is 'Active', but the static route is not present in the routing table. The track object shows 'Up'. What should the engineer check first?
⚠ Common exam trap
300-410 often tests the requirement that a static route must explicitly include the 'track' keyword to be affected by IP SLA, causing candidates to overlook this and focus on IP SLA or server issues instead.
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
✓
Verify that the static route includes the 'track' keyword and references the correct track object number.
The most likely issue is that the static route does not include the 'track' keyword or references the wrong track object number. Even if the IP SLA and track object are up, the route will not be installed if it is not explicitly linked to the track object. The engineer should first verify the static route configuration to ensure it includes 'track <object-number>' and that the number matches the track object.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Verify that the static route includes the 'track' keyword and references the correct track object number.
Why this is correct
The track object reports Up, so the SLA and tracking are functioning; the fault lies in the route's binding. Without the 'track' keyword referencing that object, the static route installs unconditionally or not at all, so verifying the route's track association is the logical first check.
- ✗
Check if the server is responding to ICMP echo requests.
Why it's wrong here
The track object already reports Up, so ICMP replies are arriving; the fault lies in how the route references the track, such as a missing or mismatched track number. It tempts because unreachable probes are the usual cause of a down track object.
- ✗
Ensure the IP SLA probe is configured with a timeout value less than the frequency.
Why it's wrong here
A timeout shorter than the frequency cannot explain a missing route: the track object already reports Up, so probes are succeeding. Timeout tuning only affects how quickly a probe is declared failed, which matters when tuning SLA responsiveness, not when the track is already satisfied and the route still absent.
- ✗
Reboot the router to clear any routing table inconsistencies.
Why it's wrong here
Rebooting clears transient state but cannot fix a misconfigured track reference, and the track already shows Up, so the route's tracking configuration is the real fault. It tempts as a familiar first-line remedy for stubborn routing anomalies.
Go deeper
Related to this question
About these practice questions
One of 1,401 original 300-410 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Cisco exam blueprint
This 300-410 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 300-410 exam.