352-001 · Question #243
What are two valid reasons for aggregating routing information within a network? (Choose two.)
The correct answer is B. to reduce the impact of topology changes C. to reduce the amount of information any specific router within the network must store and process. Route aggregation reduces the propagation of topology instability and lowers per-router routing table overhead. It does not guarantee optimal routing and is unrelated to DDoS mitigation.
Question
What are two valid reasons for aggregating routing information within a network? (Choose two.)
Options
- Ato reduce the size of the output of various show commands
- Bto reduce the impact of topology changes
- Cto reduce the amount of information any specific router within the network must store and process
- Dto improve optimal routing within the network
- Eto isolate the impact of DDoS attacks
How the community answered
(59 responses)- A3% (2)
- B88% (52)
- D7% (4)
- E2% (1)
Why each option
Route aggregation reduces the propagation of topology instability and lowers per-router routing table overhead. It does not guarantee optimal routing and is unrelated to DDoS mitigation.
Shorter show command output is a cosmetic side effect of having fewer prefixes and is not a valid network engineering justification for deploying route aggregation.
Aggregation suppresses the withdrawal and re-advertisement of more-specific prefixes when the aggregate route remains reachable, preventing individual subnet flaps from propagating across the network and reducing reconvergence scope.
Advertising one summary prefix in place of many component prefixes directly reduces the number of routing table entries each router must store, process, and evaluate during best-path calculations, lowering both memory and CPU consumption.
Aggregation can degrade routing optimality by concealing more-specific path information, which may force traffic onto a longer or less-efficient path when a better specific route exists via a different neighbor.
DDoS attack mitigation is addressed through techniques such as remotely triggered blackhole routing, ACLs, and traffic scrubbing - none of which are related to route summarization.
Concept tested: Route aggregation benefits and trade-offs
Source: https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13753-25.html
Topics
Community Discussion
No community discussion yet for this question.