Refer to the exhibit. A router is receiving BGP routing updates from multiple neighbors for routes in AS 690. What is the reason that the router still sends traffic that is destined to AS 690 to a neighbor other than 10.222.1.1?
A.
The local preference value in another neighbor statement is higher than 250.
B.
The local preference value should be set to the same value as the weight in the route map.
C.
The route map is applied in the wrong direction.
D.
The weight value in another neighbor statement is higher than 200.
Sharing is irrelevant. The question is about what THIS router does. We don't know (or care) if there even are other routers in this AS. On THIS router, we have assigned a weight to one neighbor, and (according to the correct answer) we have assigned a higher weight to a different neighbor.
What is the reason that the router (this router) still sends traffic that is destined to AS 690 to a neighbor other than 10.222.1.1? Local preference could be one reason. However this router set the weightto 200 for this neighbor. If this router set the weight to any matching prefixes, to higher than 200, for other neighbors, then the answer is D.
The AS of the router is 100, the neighbor 10.22.22.1 is AS 1, then the route announce to this must be eBGP route, and it must have a 1 prepend in it. The patten ^690$ shall match any path list that start with 690 and end with 690, so it should not set any weight nor local preference on that.. while local preference does not have effect, the weight should make it prefer to other, but it should not be advertised by other but rather have another setting to set the WEIGHT higher..
Not only is the situation described disgustingly, but also regexp will not match prefixes from AS1.
We do not see the settings of "another neighbors".
The question is obviously on the knowledge of path selection, but it is not clear where to apply this knowledge here ...
correct answer is not in options - router is sending traffic elsewhere, because it can never receive update matching as-path statement ^690$ from neighbor in AS 1. So it must receive update from other neighbors and that's why it sends it the other way. But when following "excluding wrong options" approach, D remains the last.
We all know Weight is local to each router, right? So if one of the neighbors has already been set to a weight of 200 (which one has in this config), then the only reason a third neighbor would be used is if weight of a third neighbor was higher.
Because weight is more preferred than Local Pref, it won't matter what you set Local Pref to on any neighbor, the chosen one will always be the weight=200 UNLESS someone else has a higher weight.
And don't forget, we're only looking at this one router, not a set of routers in an AS.
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.
JingleJangus
Highly Voted 3 years, 2 months agoNate860000
1 year, 2 months agoEarl03
Highly Voted 4 years, 9 months agogeek1992
4 years, 3 months agotimtgh
2 years, 10 months agopc_evans
1 year, 1 month agobk989
1 year agoIntangibleW
Most Recent 5 months, 2 weeks ago[Removed]
9 months agoLl123123
1 year, 5 months agoMD_Shox
2 years, 4 months agowts
2 years, 7 months agoxziomal9
2 years, 11 months agowts
3 years, 1 month agolcy1
3 years, 1 month agoYaPet
3 years, 1 month agoNetworkingguy
3 years, 2 months agoStivostine
3 years, 4 months agoJOKERR
3 years, 4 months agogndrx78
3 years, 4 months agoCiscoSystems
3 years, 5 months agoAlnet
3 years, 5 months ago