A sanitation department aggregates provider-independent space before advertising upstream but must avoid leaking more-specifics that would undermine that traffic engineering. What should operators watch for?
Select an answer to reveal the explanation.
Short Explanation
An aggregate is the big dumpster route; the little /24s are bags inside it. If you advertise the aggregate for TE but then leak the bags out another door, traffic ignores your neat plan. Keep the components suppressed where the aggregate is supposed to steer.
Full Explanation
BGP aggregation summarizes components into a covering prefix for cleaner advertisements and traffic engineering. If more-specifics leak through another path, longest-match forwarding bypasses the aggregate and can undo TE intent. Operators must align suppression, filtering, and policy so components do not escape contrary to design. Atomic-aggregate attributes signal information loss but do not require always deleting AS paths or forbidding PI aggregation.