IP SLA practice questions

A network engineer configures an IP SLA on a Cisco router to monitor reachability to a critical server at 10.1.1.1 using ICMP echo. The IP SLA is used as a track object for a static default route. After deployment, the engineer notices that the static route is never removed from the routing table, even when the server is unreachable. The IP SLA operation shows 'State: Active' and 'Latest RTT: NoConnection/Busy/Timeout'. What is the most likely cause?

Trap 1: The IP SLA operation is not configured with a timeout value, so it…

Incorrect because the timeout is configured by default (5000 ms) and the output shows a timeout, but the operation remains active because no threshold is set to mark it as down.

Trap 2: The track object must be configured with a 'down' delay to allow…

Incorrect because the down delay only affects how long the track object waits before declaring the tracked object down; it does not cause the operation to fail to transition to down.

Trap 3: The static route must be configured with a higher administrative…

Incorrect because the administrative distance does not affect whether the route is removed by the track object; it only influences route selection when multiple routes exist.

A
The IP SLA operation is not configured with a timeout value, so it never times out.
Why wrong: Incorrect because the timeout is configured by default (5000 ms) and the output shows a timeout, but the operation remains active because no threshold is set to mark it as down.
B
The IP SLA operation needs a threshold configured to mark the operation as 'down' when the RTT exceeds the threshold or a timeout occurs.
Correct. IP SLA uses thresholds to determine when an operation should be considered failed. Without a threshold, the operation stays active regardless of timeouts.
C
The track object must be configured with a 'down' delay to allow the route to be removed.
Why wrong: Incorrect because the down delay only affects how long the track object waits before declaring the tracked object down; it does not cause the operation to fail to transition to down.
D
The static route must be configured with a higher administrative distance to allow the IP SLA to remove it.
Why wrong: Incorrect because the administrative distance does not affect whether the route is removed by the track object; it only influences route selection when multiple routes exist.

Question 2hardmultiple choice

An engineer configures IP SLA 100 to monitor the jitter and latency of a VoIP call path between two branch routers. The configuration uses UDP jitter with a target of 192.168.2.2 on port 16384. The engineer notices that the IP SLA operation shows 'State: Active' but no jitter or latency statistics are collected. The router is generating the probe packets, but the remote router does not respond. What is the most likely reason?

Trap 1: The IP SLA operation must be configured with a 'request-data-size'…

Incorrect because the request-data-size is optional and does not affect whether the remote router responds; it only changes the size of the probe packets.

Trap 2: The source router needs a 'frequency' setting that matches the…

Incorrect because frequency only controls how often probes are sent, not whether the remote router responds.

Trap 3: The firewall on the remote router is blocking the UDP port 16384,…

Incorrect because even if the firewall blocks the probe, the IP SLA responder would still be needed to process the packet; the firewall is a secondary issue.

A
The IP SLA operation must be configured with a 'request-data-size' value to match the remote router's MTU.
Why wrong: Incorrect because the request-data-size is optional and does not affect whether the remote router responds; it only changes the size of the probe packets.
B
The remote router must have an IP SLA responder configured to process the UDP jitter probes.
Correct. For UDP jitter (and other UDP-based probes), the destination router must run the IP SLA responder to echo the packets back. Without it, the source cannot compute one-way metrics.
C
The source router needs a 'frequency' setting that matches the remote router's response interval.
Why wrong: Incorrect because frequency only controls how often probes are sent, not whether the remote router responds.
D
The firewall on the remote router is blocking the UDP port 16384, preventing the probe from reaching the target.
Why wrong: Incorrect because even if the firewall blocks the probe, the IP SLA responder would still be needed to process the packet; the firewall is a secondary issue.

Question 3mediummultiple choice

A network engineer configures IP SLA 1 to monitor HTTP server availability at 10.1.1.1 using HTTP GET. The operation is used as a track object for a backup static route. The engineer notices that the IP SLA operation shows 'State: Active' and 'Latest RTT: 200 ms', but the track object shows 'Track 1: up' even though the HTTP server returns a 404 error. What is the cause?

Trap 1: The IP SLA HTTP operation must be configured with a 'url' that…

Incorrect because the 404 is returned, but the operation still succeeds; the issue is that the operation does not treat 404 as a failure.

Trap 2: The track object must be configured with a 'down' threshold to…

Incorrect because the track object is already up; the issue is that the operation does not consider the 404 as a failure, not that the response time is too high.

Trap 3: The HTTP server is responding, so the IP SLA operation correctly…

Incorrect because the HTTP probe can be configured to match specific status codes; it is not necessary to use a different probe type.

A
The IP SLA HTTP operation must be configured with a 'url' that includes the full path, otherwise it defaults to the root and returns 404.
Why wrong: Incorrect because the 404 is returned, but the operation still succeeds; the issue is that the operation does not treat 404 as a failure.
B
The IP SLA HTTP operation does not interpret HTTP status codes by default; it only checks if a TCP connection is established.
Correct. IP SLA HTTP probe by default only verifies that the TCP handshake succeeds and a response is received. It does not parse the HTTP status code unless a 'status-code' match is configured.
C
The track object must be configured with a 'down' threshold to trigger when the HTTP response time exceeds a value.
Why wrong: Incorrect because the track object is already up; the issue is that the operation does not consider the 404 as a failure, not that the response time is too high.
D
The HTTP server is responding, so the IP SLA operation correctly shows success; the engineer must use a different type of probe, like TCP connect, to detect the 404.
Why wrong: Incorrect because the HTTP probe can be configured to match specific status codes; it is not necessary to use a different probe type.

Question 4hardmultiple choice

An engineer configures IP SLA 10 to monitor the reachability of a next-hop router at 10.1.1.1 using ICMP echo. The IP SLA is used as a track object for a static route. The engineer notices that the IP SLA operation shows 'State: Active' and 'Latest RTT: 1 ms', but the track object shows 'Track 10: up' even though the next-hop router is actually unreachable from the source. The source router has a default route pointing to 10.1.1.1. What is the most likely cause?

Trap 1: The IP SLA operation must be configured with a 'timeout' value…

Incorrect because the RTT is 1 ms, so a timeout would not help; the issue is that the probe is succeeding when it should not.

Trap 2: The track object must be configured with a 'down' delay to prevent…

Incorrect because the track object is up when it should be down; a delay would not change the state.

Trap 3: The static route must be configured with a higher administrative…

Incorrect because the administrative distance does not affect the IP SLA probe's ability to detect reachability.

A
The IP SLA operation is using the wrong source IP address; it should be sourced from the interface that connects to the next-hop router.
Correct. If the IP SLA probe is sourced from a different interface (e.g., loopback), it may take a different path and succeed even if the next-hop router is unreachable via the intended interface.
B
The IP SLA operation must be configured with a 'timeout' value lower than the RTT to force a failure.
Why wrong: Incorrect because the RTT is 1 ms, so a timeout would not help; the issue is that the probe is succeeding when it should not.
C
The track object must be configured with a 'down' delay to prevent flapping.
Why wrong: Incorrect because the track object is up when it should be down; a delay would not change the state.
D
The static route must be configured with a higher administrative distance to allow the IP SLA to remove it.
Why wrong: Incorrect because the administrative distance does not affect the IP SLA probe's ability to detect reachability.

Read the full DNS explanation →

Question 5mediummultiple choice

A network engineer configures IP SLA 20 to monitor the response time of a DNS server at 10.1.1.1 using DNS query for 'example.com'. The operation is used to influence routing decisions. The engineer notices that the IP SLA operation shows 'State: Active' and 'Latest RTT: 50 ms', but the DNS server is actually down and not responding to any queries. What is the most likely reason?

Trap 1: The IP SLA DNS probe must be configured with a 'timeout' value…

Incorrect because the RTT is 50 ms, so a timeout lower than that would cause a false failure; the issue is that the probe is getting a response from a cache.

Trap 2: The DNS server is responding to the probe but not to other queries…

Incorrect because DNS uses UDP port 53 by default; the probe uses the same port as regular queries.

Trap 3: The IP SLA operation is configured with a 'frequency' that is too…

Incorrect because frequency does not affect whether the probe receives a response; it only controls how often probes are sent.

A
The IP SLA DNS probe is using a cached DNS response from the router's DNS resolver, so it does not actually query the server.
Correct. If the router has DNS caching enabled, the IP SLA DNS probe may receive a cached response, making it appear as if the server is reachable when it is not.
B
The IP SLA DNS probe must be configured with a 'timeout' value lower than 50 ms to detect the failure.
Why wrong: Incorrect because the RTT is 50 ms, so a timeout lower than that would cause a false failure; the issue is that the probe is getting a response from a cache.
C
The DNS server is responding to the probe but not to other queries because the probe uses a different port.
Why wrong: Incorrect because DNS uses UDP port 53 by default; the probe uses the same port as regular queries.
D
The IP SLA operation is configured with a 'frequency' that is too low, causing the probe to be sent before the server times out.
Why wrong: Incorrect because frequency does not affect whether the probe receives a response; it only controls how often probes are sent.

Question 6hardmultiple choice

An engineer configures IP SLA 30 to monitor the one-way delay to a remote site using UDP jitter. The operation is used to adjust routing metrics via route maps. The engineer notices that the IP SLA operation shows 'State: Active' but the one-way delay values are inconsistent, sometimes showing negative values. What is the most likely cause?

Trap 1: The IP SLA operation is not configured with a 'request-data-size'…

Incorrect because fragmentation would cause packet loss or increased delay, not negative values.

Trap 2: The IP SLA operation is using a 'frequency' that is too high,…

Incorrect because overlapping probes would cause packet drops or retransmissions, not negative delay values.

Trap 3: The remote router's IP SLA responder is not configured, so the…

Incorrect because without a responder, the UDP jitter operation would not work at all, not produce negative values.

A
The IP SLA operation is not configured with a 'request-data-size' that matches the remote router's MTU, causing fragmentation and delay variations.
Why wrong: Incorrect because fragmentation would cause packet loss or increased delay, not negative values.
B
The source and destination routers do not have synchronized clocks via NTP, causing one-way delay calculations to be inaccurate.
Correct. One-way delay is computed by subtracting the send timestamp from the receive timestamp. If clocks are not synchronized, the result can be negative or wildly inaccurate.
C
The IP SLA operation is using a 'frequency' that is too high, causing the probes to overlap and corrupt the statistics.
Why wrong: Incorrect because overlapping probes would cause packet drops or retransmissions, not negative delay values.
D
The remote router's IP SLA responder is not configured, so the source is using a different method to estimate delay.
Why wrong: Incorrect because without a responder, the UDP jitter operation would not work at all, not produce negative values.

Question 7easymultiple choice

A network engineer configures IP SLA 40 to monitor the reachability of a server at 10.1.1.1 using ICMP echo. The operation is used as a track object for a static route. The engineer notices that the IP SLA operation shows 'State: Active' and 'Latest RTT: 10 ms', but the track object shows 'Track 40: down'. The engineer checks the track configuration and sees 'track 40 ip sla 40 reachability'. What is the most likely cause?

Trap 1: The track object must be configured with 'ip sla 40 state' instead…

Incorrect because 'reachability' is a valid keyword that tracks whether the operation is up or down; the issue is that the operation is down due to threshold.

Trap 2: The IP SLA operation is not configured with a 'frequency', so it…

Incorrect because without a frequency, the operation runs once and then stops, but it does not go down; it remains in an 'active' state with no further probes.

Trap 3: The static route is configured with a higher administrative…

Incorrect because the administrative distance of the static route does not affect the track object's state.

A
The IP SLA operation has a threshold configured that is lower than the RTT, causing the operation to be marked as 'down'.
Correct. If a threshold is configured and the RTT exceeds it, the IP SLA operation transitions to a 'down' state, which then causes the track object to go down.
B
The track object must be configured with 'ip sla 40 state' instead of 'reachability' to match the operation state.
Why wrong: Incorrect because 'reachability' is a valid keyword that tracks whether the operation is up or down; the issue is that the operation is down due to threshold.
C
The IP SLA operation is not configured with a 'frequency', so it only runs once and then goes down.
Why wrong: Incorrect because without a frequency, the operation runs once and then stops, but it does not go down; it remains in an 'active' state with no further probes.
D
The static route is configured with a higher administrative distance, causing the track object to go down.
Why wrong: Incorrect because the administrative distance of the static route does not affect the track object's state.

Question 8easymultiple choice

An engineer configures IP SLA 50 to monitor the response time of a TCP connection to a server at 10.1.1.1 on port 80. The operation is used to trigger a backup path. The engineer notices that the IP SLA operation shows 'State: Active' and 'Latest RTT: 100 ms', but the server is actually down and not responding to TCP SYN packets. What is the most likely reason?

Trap 1: The IP SLA TCP connect probe does not actually verify that the…

Incorrect because the TCP connect probe does perform a full three-way handshake; if a SYN-ACK is received, it considers the connection successful.

Trap 2: The IP SLA operation must be configured with a 'timeout' value…

Incorrect because the RTT is 100 ms, so a timeout lower than that would cause a false failure; the issue is that the probe is getting a response from a device other than the server.

Trap 3: The server is actually responding to the probe but not to other…

Incorrect because the probe uses the router's IP address as source, which is a legitimate source; the server would respond to it if it were up.

A
A stateful firewall or load balancer is responding to the TCP SYN on behalf of the server, causing the probe to succeed.
Correct. If a network device intercepts the TCP handshake and responds, the IP SLA probe will consider the connection successful even if the actual server is down.
B
The IP SLA TCP connect probe does not actually verify that the server responds; it only checks if the port is open.
Why wrong: Incorrect because the TCP connect probe does perform a full three-way handshake; if a SYN-ACK is received, it considers the connection successful.
C
The IP SLA operation must be configured with a 'timeout' value lower than 100 ms to detect the failure.
Why wrong: Incorrect because the RTT is 100 ms, so a timeout lower than that would cause a false failure; the issue is that the probe is getting a response from a device other than the server.
D
The server is actually responding to the probe but not to other traffic because the probe uses a different source IP.
Why wrong: Incorrect because the probe uses the router's IP address as source, which is a legitimate source; the server would respond to it if it were up.

Question 9mediummultiple choice

A network engineer configures IP SLA 60 to monitor the jitter of a VoIP call path between two sites. The operation uses UDP jitter with a target of 192.168.3.3 on port 16384. The engineer notices that the IP SLA operation shows 'State: Active' and 'Latest RTT: 10 ms', but the jitter values are all zero. The remote router has an IP SLA responder configured. What is the most likely cause?

Trap 1: The remote router's IP SLA responder is not configured to calculate…

Incorrect because the responder only echoes packets; the jitter calculation is done by the source router based on the timing of the returned packets.

Trap 2: The IP SLA operation is using a 'frequency' that is too high,…

Incorrect because frequency does not affect the number of packets per probe; it only controls how often probes are sent.

Trap 3: The network path has no variable delay, so jitter is naturally zero.

Incorrect because even in a stable network, there is usually some variation; but the more direct cause is the single packet configuration.

A
The IP SLA operation is configured with a 'num-packets' value of 1, so only one packet is sent per probe, and jitter cannot be calculated.
Correct. Jitter requires at least two packets to measure variation. By default, UDP jitter sends 10 packets, but if the engineer changed it to 1, jitter will be zero.
B
The remote router's IP SLA responder is not configured to calculate jitter, only to echo packets.
Why wrong: Incorrect because the responder only echoes packets; the jitter calculation is done by the source router based on the timing of the returned packets.
C
The IP SLA operation is using a 'frequency' that is too high, causing the probes to be sent too quickly and jitter to be zero.
Why wrong: Incorrect because frequency does not affect the number of packets per probe; it only controls how often probes are sent.
D
The network path has no variable delay, so jitter is naturally zero.
Why wrong: Incorrect because even in a stable network, there is usually some variation; but the more direct cause is the single packet configuration.

Question 10mediummultiple choice

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.10 Success OK 1 2 icmp-echo 192.168.1.20 Success OK 2 3 udp-jitter 192.168.1.30 Success OK 3 *4 icmp-echo 192.168.1.40 Success OK 10

Based on this output, what can be concluded?

Trap 1: All IP SLA operations are active.

Only ID 4 shows an asterisk indicating active status.

Trap 2: IP SLA operation 3 has failed.

The output shows 'Success' for operation 3, not failure.

Trap 3: IP SLA operation 1 has the highest round-trip time.

The 'Last' column shows time in seconds, not necessarily RTT; operation 1 has a value of 1, which is low.

A
All IP SLA operations are active.
Why wrong: Only ID 4 shows an asterisk indicating active status.
B
IP SLA operation 4 is currently active.
The asterisk next to ID 4 indicates it is active.
C
IP SLA operation 3 has failed.
Why wrong: The output shows 'Success' for operation 3, not failure.
D
IP SLA operation 1 has the highest round-trip time.
Why wrong: The 'Last' column shows time in seconds, not necessarily RTT; operation 1 has a value of 1, which is low.

Read the full network assurance explanation →

Question 11easymultiple choice

A network engineer executes the following command on Router R2:

R2# show ip sla configuration 1

IP SLAs Infrastructure Engine-II

Entry number: 1 Owner: admin Tag: Type of operation to perform: icmp-echo Target address: 192.168.2.10 Source address: 192.168.2.1 Type Of Service parameter: 0x0 Request size (ARR data portion): 28 Operation timeout (milliseconds): 5000 Frequency (seconds): 60 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday, Starting Time: 00:00:01) Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Distribution Statistics: Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History:

Based on this output, what is the frequency of the IP SLA operation?

Trap 1: 30 seconds

The frequency is explicitly set to 60 seconds.

Trap 2: 120 seconds

The frequency is 60 seconds, not 120.

Trap 3: 5000 milliseconds

5000 milliseconds is the timeout, not the frequency.

A
30 seconds
Why wrong: The frequency is explicitly set to 60 seconds.
B
60 seconds
The output shows 'Frequency (seconds): 60'.
C
120 seconds
Why wrong: The frequency is 60 seconds, not 120.
D
5000 milliseconds
Why wrong: 5000 milliseconds is the timeout, not the frequency.

Question 12mediummultiple choice

A network engineer issues the following command on Router R3:

R3# show ip sla statistics 2

Round Trip Time (RTT) for Index 2 Latest RTT: 12 ms Latest RTT: NoConnection/Busy/Timeout Latest Operation Start Time: 12:00:00.000 UTC Mon Mar 1 2021 Latest Operation Return Code: Timeout Number of successes: 45 Number of failures: 5 Over thresholds: 0

Based on this output, what is the most likely issue?

Trap 1: The IP SLA operation has never succeeded.

There are 45 successes, so it has succeeded before.

Trap 2: The target is unreachable due to a persistent failure.

The failures are only 5 out of 50, so it is intermittent, not persistent.

Trap 3: The round-trip time is 12 ms, which is above the threshold.

The latest RTT shows 12 ms, but the 'Over thresholds' count is 0, so it is not above threshold.

A
The IP SLA operation has never succeeded.
Why wrong: There are 45 successes, so it has succeeded before.
B
The target is unreachable due to a persistent failure.
Why wrong: The failures are only 5 out of 50, so it is intermittent, not persistent.
C
The most recent probe timed out, indicating a possible connectivity issue.
The return code 'Timeout' for the latest operation suggests a recent failure.
D
The round-trip time is 12 ms, which is above the threshold.
Why wrong: The latest RTT shows 12 ms, but the 'Over thresholds' count is 0, so it is not above threshold.

Question 13easymultiple choice

A network engineer runs the following command on Router R4:

R4# show ip sla monitor statistics 3

Round Trip Time (RTT) for Index 3 Latest RTT: 25 ms Latest Operation Start Time: 14:30:00.000 UTC Mon Mar 1 2021 Latest Operation Return Code: OK Number of successes: 100 Number of failures: 0 Over thresholds: 0

Based on this output, what can be concluded about the IP SLA operation?

Trap 1: The operation has experienced failures.

Number of failures is 0.

Trap 2: The operation is currently failing.

The return code is 'OK', indicating success.

Trap 3: The round-trip time exceeds the threshold.

Over thresholds count is 0, so it does not exceed.

A
The operation has experienced failures.
Why wrong: Number of failures is 0.
B
The operation is currently failing.
Why wrong: The return code is 'OK', indicating success.
C
The operation is working correctly with no failures.
100 successes and 0 failures confirm proper operation.
D
The round-trip time exceeds the threshold.
Why wrong: Over thresholds count is 0, so it does not exceed.

Read the full network assurance explanation →

Question 14easymultiple choice

A network engineer executes the following command on Router R5:

R5# show ip sla monitor configuration 4

IP SLAs Monitor Configuration

Entry number: 4 Owner: Tag: Type of operation to perform: udp-jitter Target address: 192.168.5.10 Target port: 16384 Source address: 192.168.5.1 Source port: 0 Type Of Service parameter: 0x0 Request size (ARR data portion): 32 Operation timeout (milliseconds): 5000 Frequency (seconds): 60 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday, Starting Time: 00:00:01) Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Distribution Statistics: Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History:

Based on this output, what type of IP SLA operation is configured?

Trap 1: ICMP echo

The type is udp-jitter, not icmp-echo.

Trap 2: TCP connect

The type is udp-jitter, not TCP connect.

Trap 3: HTTP get

The type is udp-jitter, not HTTP get.

A
ICMP echo
Why wrong: The type is udp-jitter, not icmp-echo.
B
UDP jitter
The output explicitly states 'udp-jitter'.
C
TCP connect
Why wrong: The type is udp-jitter, not TCP connect.
D
HTTP get
Why wrong: The type is udp-jitter, not HTTP get.

Question 15mediummultiple choice

A network engineer issues the following command on Router R6:

R6# show ip sla statistics 5

Round Trip Time (RTT) for Index 5 Latest RTT: 150 ms Latest Operation Start Time: 16:00:00.000 UTC Mon Mar 1 2021 Latest Operation Return Code: OK Number of successes: 10 Number of failures: 0 Over thresholds: 8

Based on this output, what does the 'Over thresholds: 8' indicate?

Trap 1: 8 probes failed to reach the target.

Failures are 0, so no probes failed.

Trap 2: 8 probes were sent in total.

Total successes are 10, so more than 8 probes were sent.

Trap 3: The threshold is set to 150 ms.

The threshold is not shown in this output; it is configured separately.

A
8 probes failed to reach the target.
Why wrong: Failures are 0, so no probes failed.
B
8 probes had RTT exceeding the configured threshold.
Over thresholds count indicates threshold violations.
C
8 probes were sent in total.
Why wrong: Total successes are 10, so more than 8 probes were sent.
D
The threshold is set to 150 ms.
Why wrong: The threshold is not shown in this output; it is configured separately.

Question 16hardmultiple choice

A network engineer runs the following command on Router R7:

R7# show ip sla monitor statistics 6

Round Trip Time (RTT) for Index 6 Latest RTT: NoConnection/Busy/Timeout Latest Operation Start Time: 18:00:00.000 UTC Mon Mar 1 2021 Latest Operation Return Code: Timeout Number of successes: 0 Number of failures: 15 Over thresholds: 0

Based on this output, what is the status of the IP SLA operation?

Trap 1: The operation is functioning normally with occasional timeouts.

All 15 probes failed, not occasional.

Trap 2: The target is reachable but with high latency.

The return code is Timeout, not high latency.

Trap 3: The operation has been configured but not started.

The statistics show 15 failures, so it has started.

A
The operation is functioning normally with occasional timeouts.
Why wrong: All 15 probes failed, not occasional.
B
The target is reachable but with high latency.
Why wrong: The return code is Timeout, not high latency.
C
The target is unreachable, as all probes have timed out.
15 failures and timeout indicate unreachable target.
D
The operation has been configured but not started.
Why wrong: The statistics show 15 failures, so it has started.

Question 17mediummultiple choice

A network engineer executes the following command on Router R8:

R8# show ip sla monitor summary

IP SLAs Monitor Summary

Codes: * active, ^ inactive, ~ pending

ID Type Destination Stats Return Code Last *1 icmp-echo 192.168.8.10 Success OK 1 ^2 udp-jitter 192.168.8.20 Success OK 2 *3 icmp-echo 192.168.8.30 Success OK 3

Based on this output, which IP SLA operations are currently active?

Trap 1: Only ID 1

ID 3 also has an asterisk.

Trap 2: Only ID 2

ID 2 has a caret, meaning inactive.

Trap 3: All three operations

ID 2 is inactive.

A
Only ID 1
Why wrong: ID 3 also has an asterisk.
B
Only ID 2
Why wrong: ID 2 has a caret, meaning inactive.
C
IDs 1 and 3
Both IDs 1 and 3 show asterisks.
D
All three operations
Why wrong: ID 2 is inactive.

Read the full network assurance explanation →

Question 18mediummultiple choice

A network engineer issues the following command on Router R9:

R9# show ip sla configuration 7

IP SLAs Infrastructure Engine-II

Entry number: 7 Owner: Tag: Type of operation to perform: icmp-echo Target address: 192.168.9.10 Source address: 192.168.9.1 Type Of Service parameter: 0x0 Request size (ARR data portion): 28 Operation timeout (milliseconds): 5000 Frequency (seconds): 30 Next Scheduled Start Time: Start Time already passed Group Scheduled : FALSE Life (seconds): 3600 Entry Ageout (seconds): never Recurring (Starting Everyday, Starting Time: 00:00:01) Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Distribution Statistics: Number of statistic hours kept: 2 Number of statistic distribution buckets kept: 1 Statistic distribution interval (milliseconds): 20 Enhanced History:

Based on this output, how long will this IP SLA operation run?

Trap 1: Forever

The life is set to 3600 seconds, not forever.

Trap 2: 30 seconds

30 seconds is the frequency, not the lifetime.

Trap 3: 5000 milliseconds

5000 milliseconds is the timeout, not the lifetime.

A
Forever
Why wrong: The life is set to 3600 seconds, not forever.
B
30 seconds
Why wrong: 30 seconds is the frequency, not the lifetime.
C
3600 seconds
The life is explicitly 3600 seconds.
D
5000 milliseconds
Why wrong: 5000 milliseconds is the timeout, not the lifetime.

Read the full IP SLA explanation →

Question 19mediummultiple choice

Examine the following IP SLA configuration:

ip sla 1

icmp-echo 10.1.1.1 frequency 10

ip sla schedule 1 life forever start-time now

What is the effect of this configuration?

Trap 1: It sends ICMP echo requests to 10.1.1.1 every 10 seconds, but only…

The 'life forever' parameter makes the operation run indefinitely, not for a limited time.

Trap 2: It sends ICMP echo requests to 10.1.1.1 every 60 seconds by default.

The 'frequency 10' overrides the default of 60 seconds, setting it to 10 seconds.

Trap 3: It sends ICMP echo requests to 10.1.1.1 every 10 seconds, but only…

ICMP echo operations do not require an IP SLA responder; they use standard ICMP.

A
It sends ICMP echo requests to 10.1.1.1 every 10 seconds, starting immediately and running forever.
The 'frequency 10' sets the interval to 10 seconds, 'start-time now' starts it immediately, and 'life forever' keeps it running indefinitely.
B
It sends ICMP echo requests to 10.1.1.1 every 10 seconds, but only for 10 minutes.
Why wrong: The 'life forever' parameter makes the operation run indefinitely, not for a limited time.
C
It sends ICMP echo requests to 10.1.1.1 every 60 seconds by default.
Why wrong: The 'frequency 10' overrides the default of 60 seconds, setting it to 10 seconds.
D
It sends ICMP echo requests to 10.1.1.1 every 10 seconds, but only if an IP SLA responder is configured on the target.
Why wrong: ICMP echo operations do not require an IP SLA responder; they use standard ICMP.

Question 20mediummultiple choice

Consider the following partial configuration on Router R1:

ip sla 2

icmp-echo 10.2.2.2 frequency 15

ip sla schedule 2 life forever start-time now
ip sla reaction-configuration 2 react timeout threshold-type immediate action-type triggerOnly

Which statement about this configuration is true?

Trap 1: The IP SLA operation will send ICMP echo requests every 15 seconds…

'action-type triggerOnly' limits the trigger to one occurrence; for continuous triggering, 'action-type triggerAndReset' would be used.

Trap 2: The IP SLA operation will send ICMP echo requests every 15 seconds…

The 'react timeout' monitors for timeouts, not round-trip time thresholds. For RTT thresholds, 'react rtt' would be used.

Trap 3: The IP SLA operation will send ICMP echo requests every 15 seconds,…

The command is valid; 'threshold-type immediate' does not require a numeric threshold value.

A
The IP SLA operation will send ICMP echo requests every 15 seconds and trigger an event if a timeout occurs, but the trigger will only activate once.
'threshold-type immediate' triggers as soon as a timeout occurs, and 'action-type triggerOnly' ensures it triggers only once.
B
The IP SLA operation will send ICMP echo requests every 15 seconds and continuously trigger events for each timeout.
Why wrong: 'action-type triggerOnly' limits the trigger to one occurrence; for continuous triggering, 'action-type triggerAndReset' would be used.
C
The IP SLA operation will send ICMP echo requests every 15 seconds and trigger an event if the round-trip time exceeds a threshold.
Why wrong: The 'react timeout' monitors for timeouts, not round-trip time thresholds. For RTT thresholds, 'react rtt' would be used.
D
The IP SLA operation will send ICMP echo requests every 15 seconds, but the 'reaction-configuration' command is invalid because it requires a threshold value.
Why wrong: The command is valid; 'threshold-type immediate' does not require a numeric threshold value.