300-410 IP SLA • Complete Question Bank
Complete 300-410 IP SLA question bank — all 0 questions with answers and detailed explanations.
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?
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?
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?
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?
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 1Based on this output, which statement is correct?
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 2Based on this output, which statement is correct?
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.0Routing 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?
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?
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 5Based on this output, which statement is correct?
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?
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?
Consider this IP SLA configuration on router R3:
ip sla 30
icmp-echo 192.168.2.1 frequency 5
ip sla schedule 30 life forever start-time now
What is missing from this configuration?
Given this IP SLA configuration on router R4:
ip sla 40
icmp-echo 10.10.10.1 source-ip 172.16.1.1 frequency 15
ip sla schedule 40 life forever start-time now
Which statement is true?
Examine this IP SLA configuration on router R5:
ip sla 50
icmp-echo 10.20.20.1 source-ip 192.168.10.1 frequency 10
ip sla schedule 50 life forever start-time now
What is the effect of this configuration?
Consider this IP SLA configuration on router R6:
ip sla 60
udp-echo 203.0.113.1 2000 source-ip 198.51.100.1 frequency 20
ip sla schedule 60 life forever start-time now
What is the purpose of this configuration?
A large enterprise network is experiencing intermittent reachability to a critical server (10.10.10.10). Router R1 has the following relevant configuration:
ip sla 1
icmp-echo 10.10.10.10 source-ip 192.168.1.1 frequency 10
ip sla schedule 1 life forever start-time now track 1 ip sla 1 reachability
delay down 5 up 5
ip route 0.0.0.0 0.0.0.0 192.168.1.2 track 1 Router R2 (the next-hop) shows:
show ip route | include 10.10.10.10
S 10.10.10.0/24 [1/0] via 10.0.0.1
What is the root cause?
A network engineer configured IP SLA to track a BGP next-hop for a backup path. Router R1 has:
ip sla 2
icmp-echo 192.168.2.2 source-ip 192.168.1.1 frequency 5
ip sla schedule 2 life forever start-time now track 2 ip sla 2 reachability router bgp 65001
bgp log-neighbor-changes
neighbor 192.168.2.2 remote-as 65002 neighbor 192.168.2.2 fall-over bfd neighbor 192.168.2.2 track 2
However, when the link to 192.168.2.2 goes down, the BGP session does not reset immediately. What is the root cause?
An enterprise uses IP SLA to track a route to a remote site via two ISPs. Router R1 has:
ip sla 3
icmp-echo 8.8.8.8 source-ip 10.0.0.1 frequency 10
ip sla schedule 3 life forever start-time now track 3 ip sla 3 reachability ip route 10.10.10.0 255.255.255.0 10.0.0.2 track 3 ip route 10.10.10.0 255.255.255.0 10.0.1.2 10
When the primary ISP fails, the backup route is used, but traffic to 10.10.10.0/24 is intermittently lost. Show output on R1:
show ip route 10.10.10.0 Routing entry for 10.10.10.0/24 Known via "static", distance 1, metric 0 Last update from 10.0.0.2 on GigabitEthernet0/0
* 10.0.1.2, via GigabitEthernet0/1
What is the root cause?
An engineer configures IP SLA to track a route to a loopback address for BGP next-hop tracking. Router R1 has:
ip sla 4
icmp-echo 192.168.100.1 source-ip 10.0.0.1 frequency 5
ip sla schedule 4 life forever start-time now track 4 ip sla 4 reachability router bgp 65001 neighbor 10.0.0.2 remote-as 65002 neighbor 10.0.0.2 update-source Loopback0 neighbor 10.0.0.2 ebgp-multihop 2 neighbor 10.0.0.2 fall-over bfd
But the BGP session to 10.0.0.2 is flapping every 5 seconds. What is the root cause?
A company uses IP SLA to track a route to a remote network via a DMVPN tunnel. Router R1 (hub) has:
ip sla 5
icmp-echo 172.16.0.1 source-ip 10.0.0.1 frequency 10
ip sla schedule 5 life forever start-time now track 5 ip sla 5 reachability ip route 192.168.1.0 255.255.255.0 Tunnel0 track 5
Tunnel0 is a DMVPN tunnel to spoke R2. The tunnel is up, but the route is intermittently removed. Show output on R1:
show ip route 192.168.1.0 % Subnet not in table
show track 5
Track 5 IP SLA 5 reachability
Reachability is Down 2 changes, last change 00:00:05
What is the root cause?
An engineer configures IP SLA to track a route to a server in a VRF. Router R1 has:
ip sla 6
icmp-echo 10.10.10.10 source-ip 192.168.1.1 frequency 10
ip sla schedule 6 life forever start-time now track 6 ip sla 6 reachability ip route vrf BLUE 0.0.0.0 0.0.0.0 192.168.1.2 track 6
But the route is never installed in the VRF routing table. Show output:
show ip route vrf BLUE | include 0.0.0.0 % No default route found
What is the root cause?
A network engineer configures IP SLA to track a BGP next-hop for a backup path. Router R1 has:
ip sla 7
icmp-echo 192.168.3.3 source-ip 10.0.0.1 frequency 5
ip sla schedule 7 life forever start-time now track 7 ip sla 7 reachability router bgp 65001 neighbor 192.168.3.3 remote-as 65003 neighbor 192.168.3.3 fall-over bfd neighbor 192.168.3.3 track 7
But when the link to 192.168.3.3 goes down, the BGP session resets after 5 seconds, but the backup route is not used immediately. What is the root cause?
A large enterprise uses IP SLA to track a route to a remote site via an MPLS L3VPN. Router R1 (PE) has:
ip sla 8
icmp-echo 10.10.10.10 source-ip 192.168.1.1 frequency 10
ip sla schedule 8 life forever start-time now track 8 ip sla 8 reachability ip route vrf CUSTOMER 10.10.10.0 255.255.255.0 192.168.1.2 track 8
The MPLS network is operational, but the route is intermittently removed. Show output on R1:
show ip route vrf CUSTOMER 10.10.10.0 Routing entry for 10.10.10.0/24 Known via "static", distance 1, metric 0 Last update from 192.168.1.2 on GigabitEthernet0/0
* 192.168.1.2, via GigabitEthernet0/0
But the track is down:
show track 8
Track 8 IP SLA 8 reachability
Reachability is Down 3 changes, last change 00:00:15
What is the root cause?
An engineer configures IP SLA to track a route to a server that is reachable via a GRE tunnel. Router R1 has:
ip sla 9
icmp-echo 172.16.0.1 source-ip 10.0.0.1 frequency 10
ip sla schedule 9 life forever start-time now track 9 ip sla 9 reachability ip route 192.168.2.0 255.255.255.0 Tunnel0 track 9
The GRE tunnel is up, but the route is flapping. Show output on R1:
show interface Tunnel0 Tunnel0 is up, line protocol is up
show track 9
Track 9 IP SLA 9 reachability
Reachability is Up 10 changes, last change 00:00:05
What is the root cause?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla statistics 10
Round Trip Time (RTT) for Index 10 Latest RTT: 12 ms Latest RTT (milliseconds): 12 Latest RTT (microseconds): 12000 Last operation start time: 12:34:56.789 UTC Mon Mar 1 2021 Last operation return code: OK Number of successes: 100 Number of failures: 0 Operation time to live: Forever
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla configuration 10 IP SLAs, Infrastructure Engine-II.
Entry number: 10 Owner: Tag: Type of operation to perform: icmp-echo Target address: 192.168.1.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 occurred Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Distribution Statistics: Number of history intervals kept: 0 Number of history buckets kept: 15 History Statistics: Number of history Lives kept: 0
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla statistics 10 detail
Round Trip Time (RTT) for Index 10 Latest RTT: 12 ms Latest RTT (milliseconds): 12 Latest RTT (microseconds): 12000 Last operation start time: 12:34:56.789 UTC Mon Mar 1 2021 Last operation return code: OK Number of successes: 100 Number of failures: 0 Operation time to live: Forever Last operation response time: 12 ms Latest operation start time: 12:34:56.789 UTC Mon Mar 1 2021 Latest operation return code: OK Over thresholds occurred: FALSE Threshold (milliseconds): 5000 RTT Values: RTTAvg: 12 RTTMin: 10 RTTMax: 15 RTTNum: 100 RTTStdDev: 1
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla history 10
Point by Point History Entry = 10 Life = 1 Time of Event = 12:34:56.789 UTC Mon Mar 1 2021 Start Time = 12:34:56.789 UTC Mon Mar 1 2021 Completion Time = 12:34:57.001 UTC Mon Mar 1 2021 Return Code = OK RTT = 12 ms
Life = 2 Time of Event = 12:35:56.789 UTC Mon Mar 1 2021 Start Time = 12:35:56.789 UTC Mon Mar 1 2021 Completion Time = 12:35:57.001 UTC Mon Mar 1 2021 Return Code = OK RTT = 14 ms
Life = 3 Time of Event = 12:36:56.789 UTC Mon Mar 1 2021 Start Time = 12:36:56.789 UTC Mon Mar 1 2021 Completion Time = 12:36:57.001 UTC Mon Mar 1 2021 Return Code = OK RTT = 11 ms
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla application IP Service Level Agreements
Version: 2.0
IP SLAs Responder: Disabled IP SLAs Low Memory: Disabled IP SLAs ICMP Echo: Enabled IP SLAs ICMP Jitter: Enabled IP SLAs HTTP: Disabled IP SLAs FTP: Disabled IP SLAs UDP Jitter: Enabled IP SLAs TCP Connect: Enabled IP SLAs DNS: Disabled IP SLAs DHCP: Disabled IP SLAs DLSw: Disabled IP SLAs VoIP: Disabled IP SLAs Metro Ethernet: Disabled IP SLAs Video: Disabled IP SLAs LSP: Disabled IP SLAs LSP Group: Disabled IP SLAs VPLS: Disabled IP SLAs MPLS: Disabled IP SLAs MPLS Group: Disabled IP SLAs LDP: Disabled IP SLAs LDP Group: Disabled IP SLAs BFD: Disabled
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla monitor statistics 10
Round Trip Time (RTT) for Index 10 Latest RTT: 12 ms Latest RTT (milliseconds): 12 Latest RTT (microseconds): 12000 Last operation start time: 12:34:56.789 UTC Mon Mar 1 2021 Last operation return code: OK Number of successes: 100 Number of failures: 0 Operation time to live: Forever
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# show ip sla monitor configuration 10 IP SLAs Monitor, Infrastructure Engine-II.
Entry number: 10 Owner: Tag: Type of operation to perform: icmp-echo Target address: 192.168.1.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 occurred Group Scheduled : FALSE Life (seconds): Forever Entry Ageout (seconds): never Recurring (Starting Everyday): FALSE Status of entry (SNMP RowStatus): Active Threshold (milliseconds): 5000 Distribution Statistics: Number of history intervals kept: 0 Number of history buckets kept: 15 History Statistics: Number of history Lives kept: 0
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# debug ip sla monitor trace IP SLAs Monitor trace debugging is on *Mar 1 12:34:56.789: IP SLAs Monitor: Starting operation 10 *Mar 1 12:34:56.789: IP SLAs Monitor: Sending ICMP echo request to 192.168.1.1 *Mar 1 12:34:56.790: IP SLAs Monitor: Received ICMP echo reply from 192.168.1.1 *Mar 1 12:34:56.790: IP SLAs Monitor: RTT = 12 ms *Mar 1 12:34:56.790: IP SLAs Monitor: Operation 10 completed successfully *Mar 1 12:35:56.789: IP SLAs Monitor: Starting operation 10 *Mar 1 12:35:56.789: IP SLAs Monitor: Sending ICMP echo request to 192.168.1.1 *Mar 1 12:35:56.790: IP SLAs Monitor: Received ICMP echo reply from 192.168.1.1 *Mar 1 12:35:56.790: IP SLAs Monitor: RTT = 14 ms *Mar 1 12:35:56.790: IP SLAs Monitor: Operation 10 completed successfully
What does this output indicate?
A network engineer runs the following command to troubleshoot an IP SLA issue:
R1# debug ip sla trace IP SLAs trace debugging is on *Mar 1 12:34:56.789: IP SLAs: Starting operation 10 *Mar 1 12:34:56.789: IP SLAs: Sending ICMP echo request to 192.168.1.1 *Mar 1 12:34:56.790: IP SLAs: Received ICMP echo reply from 192.168.1.1 *Mar 1 12:34:56.790: IP SLAs: RTT = 12 ms *Mar 1 12:34:56.790: IP SLAs: Operation 10 completed successfully *Mar 1 12:35:56.789: IP SLAs: Starting operation 10 *Mar 1 12:35:56.789: IP SLAs: Sending ICMP echo request to 192.168.1.1 *Mar 1 12:35:56.790: IP SLAs: Received ICMP echo reply from 192.168.1.1 *Mar 1 12:35:56.790: IP SLAs: RTT = 14 ms *Mar 1 12:35:56.790: IP SLAs: Operation 10 completed successfully
What does this output indicate?