Which BGP Dampening Config Fixes Routes Withdrawn From Peers?
Refer to the exhibit. In Cisco DNA Center, a network engineer identifies that BGP-learned networks are repeatedly withdrawn from peers. Which configuration must the engineer apply to resolve the issue? -
- 
Community Votes
73% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests whether you can map the scope word "peers" to a process-wide BGP dampening configuration; the trap is choosing a neighbor-scoped dampening route-map that looks syntactically precise but only fixes one session.
This 300-410 exhibit question asks which configuration stops BGP-learned networks from being repeatedly withdrawn from peers, and the correct answer is the global bgp dampening command under router bgp 100 (A). The route-map Dampening option only dampens routes on a single neighbor, which does not match the plural scope in the stem.
Many candidates pick the route-map Dampening permit 10 option because the neighbor-level dampening syntax looks like a cleaner fix, but that route-map is attached inbound to one neighbor and cannot suppress flapping across every peer described in the question.
Community Discussion (8 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The stem states that BGP-learned networks are repeatedly withdrawn from peers, meaning the churn is observed across more than one BGP session, not just a single neighbor. Applying the bare "bgp dampening" command inside "router bgp 100" (option A) enables route dampening for the whole BGP process, so any flapping prefix received from those peers is suppressed after it crosses the suppress threshold instead of being continually re-advertised and withdrawn. The command also takes the default half-life, reuse, suppress and max-suppress values, so no extra parameters are required to make the configuration complete. The first exhibit shows exactly this global placement, while the second exhibit shows the neighbor-scoped alternative, making scope the deciding factor.Why the Other Options Are Wrong
Option D uses "route-map Dampening permit 10" with a set dampening action attached to a specific neighbor, so it only affects the routes learned from that one session and leaves the other flapping peers untouched. Option C shows the same route-map construct and fails for the same reason: the stem talks about peers plural, and a single-neighbor remedy does not satisfy that scope. Option B, the second "router bgp 100" entry in the exhibit, does not match the global dampening behavior demonstrated for A and is not the configuration that suppresses flapping process-wide. Even the vote minority for D focused on syntax from a single-neighbor example rather than on the multi-peer wording, which is why the route-map variants lose.Community Comment Notes
Most commenters chose A. As wwwwaaaa reasoned, A fits "just because of 'from peers' so not a single peer/route", implying the fix must be global rather than per-neighbor. NazgulNr5 echoed that the question says the problem occurs with 'peers' and noted that D "only applies to one neighbor", which is precisely the limitation the stem rules out. dapardo still preferred D and referenced a BGP route-dampening example, while Sammy3637 argued that the router bgp 100 variant is "close but incomplete" without threshold parameters. Despite that dissent, the thread converges on A because the exhibit's global dampening placement matches a multi-peer flapping scenario.Official Reference
Exam Strategy
When a BGP stem uses a plural scope word such as "peers", immediately eliminate any option that is attached to one specific neighbor and look for the command that enables the feature process-wide under router bgp. On exhibit questions, compare where the configuration is applied (router bgp versus neighbor) before comparing the damping parameters themselves.
Frequently Asked Questions
Why is a neighbor route-map with set dampening wrong for flapping peers?
The route-map is referenced inbound on one neighbor only, so it suppresses the flapping network on that session but not across all peers as the stem requires.
Does the bare 'bgp dampening' command need half-life and suppress thresholds?
No; the command uses defaults (15-minute half-life, 750 reuse, 2000 suppress, 60-minute max suppress), so option A is a complete, valid configuration.
Related Analysis
Practice All 300-410 Questions
Access 159 questions with complete answers and detailed explanations.
View Full 300-410 Practice Test →