Refer to the exhibit. The administrator noticed that the connection was flapping between the two ISPs instead of switching to ISP2 when the ISP1 failed. Which action resolves the issue?
A.
Include a valid source-interface keyword in the icmp-echo statement.
B.
Reference the track object 1 on the default route through ISP2 instead of ISP1.
C.
Modify the static routes to refer both to the next hop and the outgoing interface.
D.
Modify the threshold to match the administrative distance of the ISP2 route.
If you ISP 1 fails the IP SLA will start pinging out via ISP 2. They the IP SLA will start responding again and put the static router back in for ISP 1. This will continue until ISP is back online.
IP SLA 1
icmp-echo 8.8.8.8 source-interface g1/0
For more control over that, IP SLA may fall back to ISP2 in case source address can reach 8.8.8.8 by another than ISP1. You'll need to control that by adding:
ip route 8.8.8.8 255.255.255.255 g1/0
ip route 8.8.8.8 255.255.255.255 Null0 2
Note this is a bad idea with a common DNS like google. Ideally you ping some WAN specific interface that is only reachable from ISP1 exclusively, it prevents the complexity.
yes, option A. look this:
https://www.lead2pass.com/downloadable/download/sample/sample_id/7350/
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.300-410 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
DUBC89x
Highly Voted 2 years, 4 months agoellen_AA
2 years, 3 months agoPietjeplukgeluk
9 months, 3 weeks agoHungarianDish_111
1 year, 11 months ago[Removed]
Most Recent 9 months ago[Removed]
9 months, 1 week agointeldarvid
1 year, 9 months ago