Refer to exhibit. What are two reasons for IP SLA tracking failure? (Choose two)

Question

Exhibits

Options

• AThe destination must be 172.30.30.2 for icmp-echo
• BThe threshold value is wrong
• CA route back to the R1 LAN network is missing in R2
• DThe source-interface is configured incorrectly.
• EThe default route has the wrong next hop IP address

• A
  6% (3)
• B
  77% (41)
• D
  13% (7)
• E
  4% (2)

Explanation

IP SLA Tracking Failure Explanation

Why B and C are correct: Option B is correct because the IP SLA threshold value must be less than the timeout value - if the threshold exceeds the timeout, the SLA operation will always be marked as failed since it can never meet the threshold condition before timing out. Option C is correct because IP SLA uses a two-way (round-trip) test - if R2 has no route back to R1's LAN (source network), the ICMP echo reply will never return, causing the SLA probe to fail even if the forward path works perfectly.

Why the distractors are wrong:

• A is incorrect because the destination IP for icmp-echo is valid as configured; the destination address itself is not the issue.
• D is incorrect because the source-interface configuration is typically valid and appropriate for binding SLA probes to a specific interface.
• E is incorrect because the next-hop IP in the default route is not necessarily wrong - the failure stems from the return path and threshold misconfiguration, not the tracked route itself.

Memory Tip

Think "Round Trip + Realistic Thresholds" - IP SLA always needs a path back, and your threshold must be achievable within the timeout window. If either condition fails, your SLA tracking fails!

No community discussion yet for this question.