A metro interconnect starts injecting large volumes of external prefixes into the city’s IP fabric underlay. What boundary practice protects fabric scale?
Select an answer to reveal the explanation.
Short Explanation
The underlay should stay a clean city map, not the entire world’s phone book. Filter at the border so metro/Internet sprawl never lands on every leaf—hand off defaults or selective aggregates instead.
Full Explanation
Data-center underlays are sized for fabric infrastructure and controlled reachability, not Internet-scale routing tables. Border filtering (and defaults or selective aggregates where appropriate) prevents external prefix explosion from consuming leaf RIB/FIB. Redistributing full tables into the underlay, swapping protocol family as a workaround, or administratively shutting spines does not constitute sound fabric-scale boundary design.