IP SLA

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

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?

Review the following IP SLA configuration on Router R1: ip sla 3 icmp-echo 10.3.3.3 frequency 30 ip sla schedule 3 life forever start-time now ip sla reaction-configuration 3 react rtt threshold-type xof 5 threshold-value 100 action-type triggerAndReset What is the purpose of the 'threshold-type xof 5' parameter?

Examine this IP SLA configuration on Router R1: ip sla 4 icmp-echo 10.4.4.4 frequency 10 ip sla schedule 4 life forever start-time now ip sla reaction-configuration 4 react timeout threshold-type immediate action-type triggerOnly Which of the following is missing from this configuration to make it useful for tracking?

Consider the following partial configuration on Router R1: ip sla 5 icmp-echo 10.5.5.5 frequency 10 ip sla schedule 5 life forever start-time now ip sla reaction-configuration 5 react rtt threshold-type immediate threshold-value 200 action-type triggerAndReset What is the effect of the 'action-type triggerAndReset' parameter?

Review this IP SLA configuration on Router R1: ip sla 6 icmp-echo 10.6.6.6 frequency 10 ip sla schedule 6 life forever start-time now ip sla reaction-configuration 6 react timeout threshold-type immediate action-type triggerOnly Which statement is true about the 'threshold-type immediate' parameter?

What is the default frequency (in seconds) for an IP SLA ICMP echo operation if not explicitly configured?

Which IP SLA operation type requires an IP SLA responder to be configured on the target device?

What is the purpose of the 'ip sla schedule' command in IP SLA configuration?

Drag and drop the steps of configuring an IP SLA UDP jitter operation into the correct order, from first to last.

Drag and drop the steps of configuring an IP SLA ICMP echo operation into the correct order, from first to last.

Drag and drop the steps of troubleshooting an IP SLA operation into the correct order, from first to last.

Drag and drop the steps of IP SLA with threshold and reaction configuration into the correct order, from first to last.

Drag and drop the steps of IP SLA HTTP operation for application monitoring into the correct order, from first to last.

Drag and drop the steps of IP SLA DNS lookup operation setup into the correct order, from first to last.

Drag and drop the steps of IP SLA scheduling with frequency and lifetime into the correct order, from first to last.

Drag and drop the steps of IP SLA tracking with static route failover into the correct order, from first to last.

Drag and drop the steps of IP SLA with threshold and reaction configuration into the correct order, from first to last.

Drag and drop the steps of IP SLA HTTP operation for application monitoring into the correct order, from first to last.

Drag and drop the steps of IP SLA DNS lookup operation setup into the correct order, from first to last.

Drag and drop the steps of IP SLA scheduling with frequency and lifetime into the correct order, from first to last.

Drag and drop the steps of IP SLA tracking with static route failover into the correct order, from first to last.

Drag and drop each IP SLA operation type on the left to its measured metric on the right.

Drag and drop each IP SLA threshold type on the left to its trigger condition on the right.

Drag and drop each IP SLA reaction on the left to its action on the right.

Drag and drop each IP SLA schedule parameter on the left to its function on the right.

Drag and drop each IP SLA tracking object on the left to its application on the right.

Drag and drop each IP SLA operation type on the left to its measured metric on the right.

Drag and drop each IP SLA threshold type on the left to its trigger condition on the right.

Drag and drop each IP SLA reaction action on the left to its corresponding behavior on the right.

Drag and drop each IP SLA schedule parameter on the left to its function on the right.

Drag and drop each IP SLA tracking object on the left to its application on the right.

Which three statements about IP SLA threshold monitoring and reaction configuration are true? (Choose three.)

Which two statements about IP SLA probe scheduling and operation states are true? (Choose two.)

Which three statements about IP SLA UDP jitter operation are true? (Choose three.)

Which two statements about IP SLA responder configuration are true? (Choose two.)

Which three statements about IP SLA threshold configuration and reaction are true? (Choose three.)

Which two statements about IP SLA with object tracking are true? (Choose two.)

Which three statements about IP SLA probe types and their characteristics are true? (Choose three.)