Merging two company network. No subnets overlap, but engineer must limit the networks advertised to new organization. Which feature implements this requirement?

Question

Options

• Ainterface ACL
• Bstub area
• Cpassive interface
• Droute filtering
• Eroute summary

• A
  3% (1)
• B
  11% (4)
• C
  8% (3)
• D
  3% (1)
• E
  76% (29)

Explanation

Route summarization (route summary) is the correct answer. When merging networks, even if subnets don't overlap, you may still have dozens or hundreds of specific prefixes you don't want to expose to the new organization. Route summarization aggregates multiple specific routes into a single, broader summary route (e.g., advertising 10.0.0.0/8 instead of 10.1.0.0/24, 10.2.0.0/24, etc.), thereby limiting the number and granularity of routes advertised. This reduces routing table size in the new org and provides a clean boundary between the merged networks. Route filtering (D) could also limit routes, but summarization is the preferred design tool here because it both limits AND aggregates - it is the more architecturally sound choice for this scenario.

No community discussion yet for this question.