300-320 · Question #211
When designing the routing for an Enterprise Campus network it is important to keep which of the following route filtering aspects in mind?
The correct answer is B. It is best to filter (allow) the default and summary prefixes only in the Enterprise Edge to remote. At the Enterprise Edge toward remote and WAN sites, advertising only default and summary prefixes is the recommended route filtering practice to limit prefix propagation and protect internal topology detail.
Question
When designing the routing for an Enterprise Campus network it is important to keep which of the following route filtering aspects in mind?
Options
- AFiltering is only useful when combined with route summarization
- BIt is best to filter (allow) the default and summary prefixes only in the Enterprise Edge to remote
- CIGPs (for example EIGRP or OSPF) are superior to route filtering in avoiding inappropriate transit
- DThe primary limitation of router filtering is that it can only be applied on outbound updates
How the community answered
(19 responses)- A5% (1)
- B68% (13)
- C16% (3)
- D11% (2)
Why each option
At the Enterprise Edge toward remote and WAN sites, advertising only default and summary prefixes is the recommended route filtering practice to limit prefix propagation and protect internal topology detail.
Route filtering provides independent value by controlling which prefixes are advertised or accepted; it does not require summarization to be useful, and the two techniques complement rather than depend on each other.
Filtering outbound updates at the Enterprise Edge so that only the default route and aggregate summary prefixes are advertised to remote sites prevents detailed internal subnet information from leaking externally, reduces the routing table size on remote routers, and avoids topology exposure - while still providing full reachability through the summaries and default route.
IGPs such as EIGRP and OSPF propagate all learned routes throughout the routing domain by default and have no built-in mechanism to block inappropriate transit traffic; explicit route filtering or policy is required.
Route filtering can be applied on both inbound and outbound updates on Cisco routers; restricting it to outbound only is factually incorrect and would leave the design unable to control what routing information is accepted.
Concept tested: Enterprise Edge route filtering with default and summary prefixes
Source: https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/WAN_Design_Guide/WANdesign.html
Topics
Community Discussion
No community discussion yet for this question.