Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 400-007 Topic 3 Question 34 Discussion

Actual exam question for Cisco's 400-007 exam
Question #: 34
Topic #: 3
[All 400-007 Questions]

Refer to the exhibit.

Company XYZ BGP topology is as shown in the diagram. The interface on the LA router connected toward the 10.1.5.0/24 network is faulty and is going up and down, which affects the entire routing domain. Which routing technique can be used in the routing policy design so that the rest of the network is not affected by the flapping issue?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Jamie
3 months ago
Actually, using route aggregation on LA router to summarize the networks could also help in reducing the impact of the flapping interface.
upvoted 0 times
...
Kenny
3 months ago
But wouldn't route filtering on LA router be more effective in preventing the issue from spreading to other routers?
upvoted 0 times
...
Rashad
3 months ago
I think using route filtering on Chicago router to block the problematic network might be a better option.
upvoted 0 times
...
Jamie
4 months ago
I agree with Kenny. Route dampening can help stabilize the network during flapping events.
upvoted 0 times
...
Kenny
4 months ago
I think we should use route dampening on LA router to prevent the flapping from affecting the rest of the network.
upvoted 0 times
...
Kenda
4 months ago
Using route filtering on LA router to block the 10.1.5.0/24 network from getting propagated toward Chicago and New York could also work, right?
upvoted 0 times
...
Skye
5 months ago
I agree with Gertude, route dampening would help prevent the flapping issue from affecting the rest of the network.
upvoted 0 times
...
Deangelo
5 months ago
But wouldn't using route filtering on the Chicago router to block the 10.1.5.0/24 network also be a good solution?
upvoted 0 times
...
Gertude
5 months ago
I think the best option would be to use route dampening on the LA router for the 10.1.5.0/24 network.
upvoted 0 times
...
Deangelo
6 months ago
You know, I was just thinking the same thing. Route filtering is a more direct approach and might be a better option if the flapping is really problematic.
upvoted 0 times
...
Bernadine
6 months ago
But what if the flapping is really severe? Route dampening might not be enough to completely isolate the issue. Option B, using route filtering on the Chicago router to block the 10.1.5.0/24 network, could be a more reliable solution.
upvoted 0 times
...
Tequila
6 months ago
I think option A is the way to go. Using route dampening on the LA router for the 10.1.5.0/24 network will help suppress the route updates when the interface is flapping, so the rest of the network won't be affected.
upvoted 0 times
...
Jaime
6 months ago
Hmm, this is a tricky one. The issue seems to be with the interface on the LA router, which is causing the 10.1.5.0/24 network to flap up and down. We need to find a way to isolate that problem and prevent it from affecting the rest of the network.
upvoted 0 times
Beckie
5 months ago
C: Good point, route filtering might be too broad of a solution in this case
upvoted 0 times
...
Lenita
5 months ago
D: It might be better to isolate the problem at the source, the LA router, to avoid unnecessary traffic filtering
upvoted 0 times
...
Regenia
5 months ago
C: What about using route filtering on Chicago router to block the 10.1.5.0/24 network?
upvoted 0 times
...
Werner
5 months ago
A: Yes, route dampening can help stabilize the routing table in case of flapping interfaces
upvoted 0 times
...
Jade
5 months ago
B: That sounds like a good solution to prevent the flapping from affecting the rest of the network
upvoted 0 times
...
Dewitt
5 months ago
A: Use route dampening on LA router for the 10 1 5 0/24 network so that it does not get propagated when it flaps up and down
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77