How should I use these IP SLA practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just IP SLA questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the IP SLA domain.

300-410 · topic practice

IP SLA practice questions

Practise Cisco CCNP ENARSI 300-410 IP SLA practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: IP SLA

Practice 10 questions Browse domain →

What the exam tests

What to know about IP SLA

IP SLA questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Watch out for

Common IP SLA exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

IP SLA questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full VPN explanation →

A network engineer is troubleshooting a site-to-site VPN that intermittently drops. The engineer configured IP SLA 10 to track reachability of the remote LAN gateway (10.1.2.1) using ICMP echo probes every 5 seconds. The IP SLA is used in a static route to influence failover. The engineer notices that the IP SLA state shows 'Active' but the tracked route is not installed. What is the most likely cause?

Trap 1: The IP SLA probe is sending packets to the wrong destination IP.

The IP SLA shows 'Active', so the probe is reaching the destination; the destination IP is likely correct.

Trap 2: The IP SLA probe frequency is too high, causing the router to…

A high frequency does not cause the router to ignore results; it may increase CPU but does not prevent route installation.

Trap 3: The remote gateway is not responding to ICMP echo requests due to…

If the remote gateway were not responding, the IP SLA would show 'Timeout' or 'Down', not 'Active'.

Study all IP SLA common traps →

A
The IP SLA probe is sending packets to the wrong destination IP.
Why wrong: The IP SLA shows 'Active', so the probe is reaching the destination; the destination IP is likely correct.
B
The track object is configured with 'ip sla 10 reachability' but the static route references the track object incorrectly.
If the track object is not properly linked (e.g., 'track 1 ip sla 10 reachability' missing), or the static route uses a different track number, the route will not be installed even though the IP SLA is active.
C
The IP SLA probe frequency is too high, causing the router to ignore the results.
Why wrong: A high frequency does not cause the router to ignore results; it may increase CPU but does not prevent route installation.
D
The remote gateway is not responding to ICMP echo requests due to firewall rules.
Why wrong: If the remote gateway were not responding, the IP SLA would show 'Timeout' or 'Down', not 'Active'.

Full breakdown with real-world context →

Question 2hardmultiple choice

Study the full EIGRP explanation →

An engineer configured IP SLA 20 to monitor the reachability of a next-hop router (192.168.1.1) using UDP jitter probes. The goal is to use the IP SLA with a track object to influence EIGRP route selection. However, the EIGRP route is not being affected by the IP SLA state. The engineer verifies that the IP SLA is 'Active' and the track object shows 'Up'. What is the most likely misconfiguration?

Trap 1: The IP SLA probe type (UDP jitter) is not supported for tracking…

UDP jitter is supported for IP SLA; the probe type is not the issue.

Trap 2: The EIGRP route has a higher administrative distance than the…

Administrative distance is not related to IP SLA tracking; the route is still present but not affected by the track state.

Trap 3: The IP SLA threshold is set too low, causing flapping.

The track object shows 'Up', so the threshold is not causing flapping.

Study all IP SLA common traps →

A
The IP SLA probe type (UDP jitter) is not supported for tracking EIGRP routes.
Why wrong: UDP jitter is supported for IP SLA; the probe type is not the issue.
B
The track object is not configured to influence the EIGRP route; EIGRP does not support direct tracking of IP SLA for route metrics.
EIGRP does not have a mechanism to directly track IP SLA states. The engineer must use a tracked static route or policy-based routing to influence traffic.
C
The EIGRP route has a higher administrative distance than the tracked route.
Why wrong: Administrative distance is not related to IP SLA tracking; the route is still present but not affected by the track state.
D
The IP SLA threshold is set too low, causing flapping.
Why wrong: The track object shows 'Up', so the threshold is not causing flapping.

Full breakdown with real-world context →

Question 3mediummultiple choice

Review the full routing breakdown →

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?

Trap 1: Check if the server is responding to ICMP echo requests.

The IP SLA is 'Active', so the server is responding.

Trap 2: Ensure the IP SLA probe is configured with a timeout value less…

Timeout configuration does not affect route installation; it only affects probe failure detection.

Trap 3: Reboot the router to clear any routing table inconsistencies.

Rebooting is unnecessary; the issue is configuration-related.

Study all IP SLA common traps →

A
Verify that the static route includes the 'track' keyword and references the correct track object number.
The static route must be configured with 'ip route 0.0.0.0 0.0.0.0 <next-hop> track <track-number>'. If missing or wrong track number, the route will not be installed.
B
Check if the server is responding to ICMP echo requests.
Why wrong: The IP SLA is 'Active', so the server is responding.
C
Ensure the IP SLA probe is configured with a timeout value less than the frequency.
Why wrong: Timeout configuration does not affect route installation; it only affects probe failure detection.
D
Reboot the router to clear any routing table inconsistencies.
Why wrong: Rebooting is unnecessary; the issue is configuration-related.

Full breakdown with real-world context →

Question 4hardmultiple choice

Review the full routing breakdown →

An engineer configured IP SLA 40 with a UDP echo probe to monitor a remote server port 80. The IP SLA is used in a track object for a backup static route. The engineer observes that the IP SLA state is 'Timeout' even though the server is reachable via ping from the router. What is the most likely cause?

Trap 1: The router's firewall is blocking UDP packets to the server.

If the router's firewall were blocking, ICMP ping might also fail; the engineer confirmed ping works.

Trap 2: The IP SLA frequency is set too high, causing the router to miss…

Frequency does not cause timeout; it only affects how often probes are sent.

Trap 3: The track object is misconfigured with the wrong IP SLA number.

The IP SLA state is 'Timeout', indicating the probe is running but failing; the track object is not the issue.

Study all IP SLA common traps →

A
The router's firewall is blocking UDP packets to the server.
Why wrong: If the router's firewall were blocking, ICMP ping might also fail; the engineer confirmed ping works.
B
The server is not running a UDP service on port 80; HTTP uses TCP, so the UDP probe will fail.
UDP echo probes expect a UDP service on the target port. Port 80 is typically TCP, so the probe times out.
C
The IP SLA frequency is set too high, causing the router to miss responses.
Why wrong: Frequency does not cause timeout; it only affects how often probes are sent.
D
The track object is misconfigured with the wrong IP SLA number.
Why wrong: The IP SLA state is 'Timeout', indicating the probe is running but failing; the track object is not the issue.

Full breakdown with real-world context →

Question 5hardmultiple choice

Read the full NAT/PAT explanation →

A network engineer configured IP SLA 50 to monitor a remote router's loopback (5.5.5.5) using ICMP echo. The IP SLA is linked to a track object that is used in a PBR (policy-based routing) route-map. The engineer notices that the PBR is not applying the alternate path when the IP SLA goes down. The track object shows 'Down'. What is the most likely misconfiguration?

Trap 1: The IP SLA probe is using the wrong source interface.

The IP SLA state is 'Down', indicating the probe is failing; source interface is not the issue.

Trap 2: The track object is configured with a delay that prevents immediate…

Delay affects when the track state changes, but the track is already 'Down'.

Trap 3: The PBR is applied to the wrong interface.

If PBR were on the wrong interface, the alternate path would never be used, but the symptom is that PBR is not reacting to the track state.

Study all IP SLA common traps →

A
The route-map is missing the 'set ip next-hop verify-availability' command with the track object.
Without 'verify-availability', PBR does not check the track state and will continue using the primary next-hop even if the track is down.
B
The IP SLA probe is using the wrong source interface.
Why wrong: The IP SLA state is 'Down', indicating the probe is failing; source interface is not the issue.
C
The track object is configured with a delay that prevents immediate reaction.
Why wrong: Delay affects when the track state changes, but the track is already 'Down'.
D
The PBR is applied to the wrong interface.
Why wrong: If PBR were on the wrong interface, the alternate path would never be used, but the symptom is that PBR is not reacting to the track state.

Full breakdown with real-world context →

Question 6mediummultiple choice

Study the full EIGRP explanation →

An engineer configured IP SLA 60 to monitor the reachability of a WAN link's next-hop (203.0.113.1) using ICMP echo. The IP SLA is used in a track object for a floating static route. The engineer notices that the primary route (EIGRP) is present, but the floating static route is not installed when the primary fails. The track object shows 'Down' after the primary fails. What should the engineer check?

Trap 1: Check if the IP SLA probe is configured with a timeout greater than…

Timeout configuration does not affect route installation; the track is already 'Down'.

Trap 2: Ensure the primary route is removed from the routing table before…

The static route should be installed when the primary route is removed; the issue is likely AD-related.

Trap 3: Reboot the router to clear the routing table.

Rebooting is unnecessary; the issue is configuration-related.

Study all IP SLA common traps →

A
Verify that the static route's administrative distance is higher than the EIGRP route (e.g., 170 vs 90).
If the static route has an AD lower than EIGRP (e.g., 1), it would be installed even when the primary is up, causing issues. For a floating static, AD must be higher.
B
Check if the IP SLA probe is configured with a timeout greater than the frequency.
Why wrong: Timeout configuration does not affect route installation; the track is already 'Down'.
C
Ensure the primary route is removed from the routing table before the static route is installed.
Why wrong: The static route should be installed when the primary route is removed; the issue is likely AD-related.
D
Reboot the router to clear the routing table.
Why wrong: Rebooting is unnecessary; the issue is configuration-related.

Full breakdown with real-world context →

Question 7mediummultiple choice

Review the full routing breakdown →

A network engineer configured IP SLA 70 to monitor a remote site's LAN gateway (172.16.1.1) using ICMP echo. The IP SLA is linked to a track object that is used in a static route for a backup link. The engineer notices that the IP SLA state is 'Active', but the backup static route is installed in the routing table even when the primary route is available. What is the most likely cause?

Trap 1: The IP SLA probe is failing intermittently, causing the track…

The IP SLA shows 'Active', so it is not failing.

Trap 2: The primary route has a higher administrative distance than the…

If the primary route had higher AD, it would not be the primary; the issue is that the static route is installed despite the primary being available.

Trap 3: The track object is configured with a delay that causes the static…

Delay would affect when the track state changes, but the track is 'Active', so the static route should not be installed.

Study all IP SLA common traps →

A
The static route is configured without the 'track' keyword, so it is always installed regardless of the IP SLA state.
Without the 'track' keyword, the static route is permanent and will be installed if its AD is lower than the primary route.
B
The IP SLA probe is failing intermittently, causing the track object to flap.
Why wrong: The IP SLA shows 'Active', so it is not failing.
C
The primary route has a higher administrative distance than the static route.
Why wrong: If the primary route had higher AD, it would not be the primary; the issue is that the static route is installed despite the primary being available.
D
The track object is configured with a delay that causes the static route to be installed prematurely.
Why wrong: Delay would affect when the track state changes, but the track is 'Active', so the static route should not be installed.

Full breakdown with real-world context →

Question 8hardmultiple choice

Review the full routing breakdown →

An engineer configured IP SLA 80 to monitor a remote server (192.168.100.100) using ICMP echo. The IP SLA is used in a track object for a static route. The engineer notices that the IP SLA state is 'Active', but the track object shows 'Down'. What is the most likely cause?

Trap 1: The IP SLA probe is using a different source IP than expected.

Source IP does not affect the track object state; the IP SLA is 'Active'.

Trap 2: The track object is referencing the wrong IP SLA number.

If the track referenced the wrong IP SLA, the track would likely show 'Up' or 'Down' based on that other SLA, but the symptom is a mismatch.

Trap 3: The router's routing table is full, preventing the track object…

Routing table fullness does not affect track object state.

Study all IP SLA common traps →

A
The track object is configured with a 'delay up' timer that has not yet expired.
A 'delay up' timer forces the track to wait before transitioning to 'Up' after the IP SLA becomes 'Active'. This is a common cause of mismatch.
B
The IP SLA probe is using a different source IP than expected.
Why wrong: Source IP does not affect the track object state; the IP SLA is 'Active'.
C
The track object is referencing the wrong IP SLA number.
Why wrong: If the track referenced the wrong IP SLA, the track would likely show 'Up' or 'Down' based on that other SLA, but the symptom is a mismatch.
D
The router's routing table is full, preventing the track object from updating.
Why wrong: Routing table fullness does not affect track object state.

Full breakdown with real-world context →

Question 9easymultiple choice

Read the full NAT/PAT explanation →

A network engineer configured IP SLA 90 to monitor a remote router's loopback (10.0.0.1) using ICMP echo. The IP SLA is linked to a track object that is used in a static route. The engineer notices that the IP SLA state is 'Active', but the static route is not installed. The track object shows 'Up'. The engineer checks the routing table and sees a different route to the same destination with a lower administrative distance. What should the engineer do to ensure the IP SLA-tracked route is used when the primary fails?

Trap 1: Increase the administrative distance of the IP SLA-tracked static…

Increasing the AD would make the tracked route less preferred; it should be higher than the primary only if it is a floating static. The issue is that the tracked route is not being installed because the primary route has a lower AD.

Trap 2: Change the IP SLA probe to use UDP instead of ICMP.

The probe type does not affect route installation.

Trap 3: Add a 'set metric' command to the IP SLA configuration.

IP SLA does not have a 'set metric' command; metrics are not relevant to static route installation.

Study all IP SLA common traps →

A
Increase the administrative distance of the IP SLA-tracked static route to be higher than the primary route.
Why wrong: Increasing the AD would make the tracked route less preferred; it should be higher than the primary only if it is a floating static. The issue is that the tracked route is not being installed because the primary route has a lower AD.
B
Remove the primary route from the routing table.
To install the tracked route, the primary route must be removed (e.g., by shutting down the interface or redistributing). The tracked route will then be installed.
C
Change the IP SLA probe to use UDP instead of ICMP.
Why wrong: The probe type does not affect route installation.
D
Add a 'set metric' command to the IP SLA configuration.
Why wrong: IP SLA does not have a 'set metric' command; metrics are not relevant to static route installation.

Full breakdown with real-world context →

Question 10mediummultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 1

Round Trip Time (RTT) for Index 1 Latest RTT: 200 ms Latest RTT (milliseconds): 200 Latest RTT (microseconds): 200000 Number of successes: 50 Number of failures: 10 Operation time to live: Forever Output: Over threshold

Based on this output, which statement is correct?

Trap 1: The IP SLA operation has failed due to a timeout.

The output shows successes (50) and failures (10), but the operation is still active. 'Over threshold' does not indicate a timeout.

Trap 2: The IP SLA operation is not reachable and has been disabled.

The operation is still running (Time to live: Forever) and has successes, so it is not disabled.

Trap 3: The IP SLA responder is not configured on the target device.

There is no indication of responder issues; the operation is completing with successes and failures.

Study all IP SLA common traps →

A
The IP SLA operation has failed due to a timeout.
Why wrong: The output shows successes (50) and failures (10), but the operation is still active. 'Over threshold' does not indicate a timeout.
B
The latest RTT has exceeded the configured threshold value.
'Output: Over threshold' directly means the measured RTT was above the threshold set in the IP SLA configuration.
C
The IP SLA operation is not reachable and has been disabled.
Why wrong: The operation is still running (Time to live: Forever) and has successes, so it is not disabled.
D
The IP SLA responder is not configured on the target device.
Why wrong: There is no indication of responder issues; the operation is completing with successes and failures.

Full breakdown with real-world context →

Question 11mediummultiple choice

Read the full NAT/PAT explanation →

A network engineer runs the following command on Router R1:

R1# show ip sla summary

IPSLAs Latest Operation Summary

Codes: * active, ^ inactive, ~ pending

ID Type Destination Stats Return Code Last 1 icmp-echo 192.168.1.1 RTT=50ms OK 1s ago 2 icmp-echo 192.168.1.2 RTT=2000ms Over threshold 2s ago 3 icmp-echo 192.168.1.3 RTT=100ms OK 3s ago

Based on this output, which statement is correct?

Trap 1: IP SLA operation 2 has failed because the destination is…

'Over threshold' means the RTT was high, not that the destination is unreachable. Unreachability would show a different return code like 'Timeout'.

Trap 2: IP SLA operation 1 is not active because it shows 'OK'.

'OK' means the operation completed successfully; it is active.

Trap 3: IP SLA operation 3 has a pending status.

The status shows no pending indicator; it is active with an OK return code.

Study all IP SLA common traps →

A
IP SLA operation 2 has failed because the destination is unreachable.
Why wrong: 'Over threshold' means the RTT was high, not that the destination is unreachable. Unreachability would show a different return code like 'Timeout'.
B
IP SLA operation 2 is experiencing high latency, exceeding the configured threshold.
The return code 'Over threshold' directly indicates that the RTT exceeded the threshold, implying high latency.
C
IP SLA operation 1 is not active because it shows 'OK'.
Why wrong: 'OK' means the operation completed successfully; it is active.
D
IP SLA operation 3 has a pending status.
Why wrong: The status shows no pending indicator; it is active with an OK return code.

Full breakdown with real-world context →

Question 12hardmultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla configuration 1

IP SLAs Infrastructure Engine-II

Entry number: 1 Owner: Tag: Type of operation to perform: icmp-echo Target address: 192.168.1.1 Source address: 0.0.0.0 Source interface: none Type Of Service parameter: 0 Verify data: No Operation timeout (milliseconds): 5000 Request size (ARR data block): 28 Threshold (milliseconds): 100 Frequency (seconds): 10 Life (seconds): Forever Ageout (seconds): 0

Based on this output, what is the primary problem with this IP SLA configuration?

Trap 1: The threshold value is too low, causing frequent threshold…

While the threshold is low, it is not necessarily a problem; it depends on the network. The source address issue is more critical.

Trap 2: The frequency is set to 10 seconds, which is too fast for accurate…

A 10-second frequency is typical and not inherently problematic.

Trap 3: The operation timeout is too high, causing delays in failure…

A 5000 ms timeout is reasonable; it does not cause a direct problem.

Study all IP SLA common traps →

A
The threshold value is too low, causing frequent threshold violations.
Why wrong: While the threshold is low, it is not necessarily a problem; it depends on the network. The source address issue is more critical.
B
The source address is set to 0.0.0.0, which may cause the probe to fail if the router does not have a valid route.
A source address of 0.0.0.0 means the router uses the IP of the egress interface, but if that interface is down or has no IP, the probe may fail. This is a common misconfiguration.
C
The frequency is set to 10 seconds, which is too fast for accurate measurements.
Why wrong: A 10-second frequency is typical and not inherently problematic.
D
The operation timeout is too high, causing delays in failure detection.
Why wrong: A 5000 ms timeout is reasonable; it does not cause a direct problem.

Full breakdown with real-world context →

Question 13mediummultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 2

Round Trip Time (RTT) for Index 2 Latest RTT: No connection Latest RTT (milliseconds): No connection Latest RTT (microseconds): No connection Number of successes: 0 Number of failures: 100 Operation time to live: Forever Output: No connection

Based on this output, which statement is correct?

Trap 1: The IP SLA operation is working correctly but the RTT is too high…

'No connection' means the probe did not receive any response, not that RTT is high.

Trap 2: The IP SLA operation has been manually disabled.

There is no indication of manual disablement; the operation is still running but failing.

Trap 3: The IP SLA responder is misconfigured on the source router.

The responder is on the target, not the source. The source is sending probes.

Study all IP SLA common traps →

A
The IP SLA operation is working correctly but the RTT is too high to measure.
Why wrong: 'No connection' means the probe did not receive any response, not that RTT is high.
B
The target device is not responding to ICMP echo requests, or there is a routing problem.
'No connection' indicates that the probe failed to reach the target, likely due to unreachability or lack of response.
C
The IP SLA operation has been manually disabled.
Why wrong: There is no indication of manual disablement; the operation is still running but failing.
D
The IP SLA responder is misconfigured on the source router.
Why wrong: The responder is on the target, not the source. The source is sending probes.

Full breakdown with real-world context →

Question 14hardmultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 3

Round Trip Time (RTT) for Index 3 Latest RTT: 150 ms Latest RTT (milliseconds): 150 Latest RTT (microseconds): 150000 Number of successes: 80 Number of failures: 20 Operation time to live: Forever Output: OK

R1# show track 1
Track 1
  IP SLA 3 reachability

Reachability is Up 2 changes, last change 00:00:10 Latest operation return code: OK Latest RTT (milliseconds): 150

Tracked by:
    ip route 0.0.0.0 0.0.0.0 192.168.1.1 track 1

Based on this output, which statement is correct?

Trap 1: The static route is removed because the IP SLA operation has…

The track is up, so the static route remains. Failures alone do not bring the track down unless they exceed a threshold.

Trap 2: The IP SLA operation has a 20% failure rate, so the track should be…

The track is up, so the failure rate is within the configured threshold. The track does not automatically go down with failures.

Trap 3: The IP SLA operation is using a wrong source address.

There is no indication of source address issues; the operation is succeeding.

Study all IP SLA common traps →

A
The static route is removed because the IP SLA operation has failures.
Why wrong: The track is up, so the static route remains. Failures alone do not bring the track down unless they exceed a threshold.
B
The IP SLA operation is considered reachable, and the tracked static route is active.
The track shows 'Up', meaning the IP SLA is reachable, and the static route is installed.
C
The IP SLA operation has a 20% failure rate, so the track should be down.
Why wrong: The track is up, so the failure rate is within the configured threshold. The track does not automatically go down with failures.
D
The IP SLA operation is using a wrong source address.
Why wrong: There is no indication of source address issues; the operation is succeeding.

Full breakdown with real-world context →

Question 15hardmultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 4

Round Trip Time (RTT) for Index 4 Latest RTT: 300 ms Latest RTT (milliseconds): 300 Latest RTT (microseconds): 300000 Number of successes: 45 Number of failures: 55 Operation time to live: Forever Output: Over threshold

R1# show track 2
Track 2
  IP SLA 4 reachability

Reachability is Down 5 changes, last change 00:00:05 Latest operation return code: Over threshold Latest RTT (milliseconds): 300

Tracked by:
    ip route 0.0.0.0 0.0.0.0 192.168.2.1 track 2

Based on this output, which statement is correct?

Trap 1: The IP SLA operation is failing because the target is unreachable.

The return code is 'Over threshold', not 'No connection', so the target is reachable but with high latency.

Trap 2: The tracked static route is active because the IP SLA has successes.

The track is down, so the static route is removed from the routing table.

Trap 3: The IP SLA operation has a 55% failure rate, but the track is still…

The track is down, not up.

Study all IP SLA common traps →

A
The IP SLA operation is failing because the target is unreachable.
Why wrong: The return code is 'Over threshold', not 'No connection', so the target is reachable but with high latency.
B
The tracked static route is active because the IP SLA has successes.
Why wrong: The track is down, so the static route is removed from the routing table.
C
The IP SLA threshold has been exceeded, causing the track to go down and the static route to be removed.
The track is down due to 'Over threshold', which means the static route is no longer installed.
D
The IP SLA operation has a 55% failure rate, but the track is still up.
Why wrong: The track is down, not up.

Full breakdown with real-world context →

Question 16mediummultiple choice

Read the full NAT/PAT explanation →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 5

Round Trip Time (RTT) for Index 5 Latest RTT: 50 ms Latest RTT (milliseconds): 50 Latest RTT (microseconds): 50000 Number of successes: 100 Number of failures: 0 Operation time to live: Forever Output: OK

R1# show track 3
Track 3
  IP SLA 5 reachability

Reachability is Up 1 change, last change 00:10:00 Latest operation return code: OK Latest RTT (milliseconds): 50

Tracked by:
    ip route 0.0.0.0 0.0.0.0 192.168.3.1 track 3

R1# show ip route 0.0.0.0 0.0.0.0

Routing entry for 0.0.0.0/0, supernet Known via "static", distance 1, metric 0, candidate default path Last update from 192.168.3.1 on GigabitEthernet0/0 Routing Descriptor Blocks:

* 192.168.3.1, via GigabitEthernet0/0

Route metric is 0, traffic share count is 1

Based on this output, which statement is correct?

Trap 1: The static route is not installed because the track is up.

The track being up means the route is installed, as shown in the routing table.

Trap 2: The IP SLA operation is failing, causing the track to go down.

The IP SLA has 100 successes and no failures, so it is not failing.

Trap 3: The IP SLA operation has a threshold violation.

The output shows 'OK', not 'Over threshold'.

Study all IP SLA common traps →

A
The static route is not installed because the track is up.
Why wrong: The track being up means the route is installed, as shown in the routing table.
B
The IP SLA operation is failing, causing the track to go down.
Why wrong: The IP SLA has 100 successes and no failures, so it is not failing.
C
The static route is active and reachable via 192.168.3.1.
The routing table shows the static route is installed with next-hop 192.168.3.1, and the track confirms reachability.
D
The IP SLA operation has a threshold violation.
Why wrong: The output shows 'OK', not 'Over threshold'.

Full breakdown with real-world context →

Question 17mediummultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 6

Round Trip Time (RTT) for Index 6 Latest RTT: 0 ms Latest RTT (milliseconds): 0 Latest RTT (microseconds): 0 Number of successes: 0 Number of failures: 100 Operation time to live: Forever Output: No connection

R1# show track 4
Track 4
  IP SLA 6 reachability

Reachability is Down 3 changes, last change 00:05:00 Latest operation return code: No connection Latest RTT (milliseconds): 0

Tracked by:
    ip route 0.0.0.0 0.0.0.0 192.168.4.1 track 4

R1# show ip route 0.0.0.0 0.0.0.0

% Network not in table

Based on this output, which statement is correct?

Trap 1: The static route is still present because the track is down.

When the track goes down, the static route is removed from the routing table.

Trap 2: The IP SLA operation is successful, but the track is misconfigured.

The IP SLA shows 'No connection', so it is not successful.

Trap 3: The IP SLA operation has a threshold violation, but the route is…

The return code is 'No connection', not 'Over threshold', and the route is not active.

Study all IP SLA common traps →

A
The static route is still present because the track is down.
Why wrong: When the track goes down, the static route is removed from the routing table.
B
The IP SLA operation is successful, but the track is misconfigured.
Why wrong: The IP SLA shows 'No connection', so it is not successful.
C
The target 192.168.4.1 is unreachable, causing the IP SLA to fail and the static route to be removed.
The 'No connection' indicates unreachability, and the track down removes the static route.
D
The IP SLA operation has a threshold violation, but the route is still active.
Why wrong: The return code is 'No connection', not 'Over threshold', and the route is not active.

Full breakdown with real-world context →

Question 18hardmultiple choice

Review the full routing breakdown →

A network engineer runs the following command on Router R1:

R1# show ip sla statistics 7

Round Trip Time (RTT) for Index 7 Latest RTT: 500 ms Latest RTT (milliseconds): 500 Latest RTT (microseconds): 500000 Number of successes: 30 Number of failures: 70 Operation time to live: Forever Output: Over threshold

R1# show track 5
Track 5
  IP SLA 7 reachability

Reachability is Up 1 change, last change 00:20:00 Latest operation return code: Over threshold Latest RTT (milliseconds): 500

Tracked by:
    ip route 0.0.0.0 0.0.0.0 192.168.5.1 track 5

Based on this output, which statement is correct?

Trap 1: The track is down because the IP SLA return code is 'Over…

The track shows 'Up', so it is not down.

Trap 2: The static route is removed because of the threshold violation.

The track is up, so the static route is still installed.

Trap 3: The IP SLA operation is not responding because of a network issue.

The operation is responding with RTT values, so it is not a no-connection issue.

Study all IP SLA common traps →

A
The track is down because the IP SLA return code is 'Over threshold'.
Why wrong: The track shows 'Up', so it is not down.
B
The IP SLA operation has a high failure rate, but the track remains up due to the configured threshold parameters.
The track is up, meaning the failure rate is within the acceptable range defined in the track configuration.
C
The static route is removed because of the threshold violation.
Why wrong: The track is up, so the static route is still installed.
D
The IP SLA operation is not responding because of a network issue.
Why wrong: The operation is responding with RTT values, so it is not a no-connection issue.

Full breakdown with real-world context →

Question 19mediummultiple choice

Review the full routing breakdown →

Given the following partial configuration on router R1:

ip sla 10

icmp-echo 192.168.1.1 source-ip 10.0.0.1 frequency 10

ip sla schedule 10 life forever start-time now

Which statement best describes the effect of this configuration?

Trap 1: It sends ICMP echo requests from 192.168.1.1 to 10.0.0.1 every 10…

The source-ip is the local address, not the destination.

Trap 2: It sends ICMP echo requests every 10 seconds but only after the…

The schedule starts immediately, regardless of replies.

Trap 3: It sends ICMP echo requests only once and then stops.

The frequency 10 and life forever ensure continuous probing.

Study all IP SLA common traps →

A
It sends ICMP echo requests from 10.0.0.1 to 192.168.1.1 every 10 seconds.
The icmp-echo command defines the destination, source-ip sets the source, and frequency sets the interval.
B
It sends ICMP echo requests from 192.168.1.1 to 10.0.0.1 every 10 seconds.
Why wrong: The source-ip is the local address, not the destination.
C
It sends ICMP echo requests every 10 seconds but only after the first successful reply.
Why wrong: The schedule starts immediately, regardless of replies.
D
It sends ICMP echo requests only once and then stops.
Why wrong: The frequency 10 and life forever ensure continuous probing.

Full breakdown with real-world context →

Question 20mediummultiple choice

Review the full routing breakdown →

Examine this IP SLA configuration on router R2:

ip sla 20

udp-jitter 203.0.113.10 16384 source-ip 198.51.100.1 source-port 16384 frequency 30

ip sla schedule 20 life forever start-time now

Which statement is true?

Trap 1: It measures only packet loss, not delay or jitter.

UDP jitter measures multiple metrics including delay and jitter.

Trap 2: It uses TCP to measure round-trip time.

It uses UDP, not TCP.

Trap 3: It sends ICMP echo requests to test connectivity.

It uses UDP jitter, not ICMP.

Study all IP SLA common traps →

A
It measures one-way delay and jitter using UDP packets.
UDP jitter operation measures delay, jitter, and packet loss.
B
It measures only packet loss, not delay or jitter.
Why wrong: UDP jitter measures multiple metrics including delay and jitter.
C
It uses TCP to measure round-trip time.
Why wrong: It uses UDP, not TCP.
D
It sends ICMP echo requests to test connectivity.
Why wrong: It uses UDP jitter, not ICMP.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused IP SLA sessions

Start a IP SLA only practice session

Every question in these sessions is drawn from the IP SLA domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all IP SLA questions →Mixed 300-410 session

Frequently asked questions

What does the 300-410 exam test about IP SLA?: IP SLA questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just IP SLA questions in a focused session?: Yes — the session launcher on this page draws every question from the IP SLA domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other 300-410 topics?: Use the topic links above to move to related areas, or go back to the 300-410 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the 300-410 exam covers. They are not copied from any real exam or dump site.

IP SLA only

10 questions 20 questions 30 questions 50 questions

Mixed 300-410 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All 300-410 questions IP SLA domain overview 300-410 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

IP SLA practice questions

What to know about IP SLA

Common IP SLA exam traps

IP SLA questions

An engineer configured IP SLA 80 to monitor a remote server (192.168.100.100) using ICMP echo. The IP SLA is used in a track object for a static route. The engineer notices that the IP SLA state is 'Active', but the track object shows 'Down'. What is the most likely cause?

Track your progress over time

Start a IP SLA only practice session

Related 300-410 topic practice pages

Layer 3 Technologies practice questions

EIGRP Troubleshooting practice questions

OSPF Troubleshooting (v2/v3) practice questions

BGP Troubleshooting practice questions

Route Redistribution practice questions

Policy-Based Routing (PBR) practice questions

VRF-Lite practice questions

Route Maps and Route Filtering practice questions

Administrative Distance practice questions

Route Summarization practice questions

Bidirectional Forwarding Detection (BFD) practice questions

VPN Technologies practice questions

Frequently asked questions

Track your progress

Study resources

Exam traps to avoid