Operators place every municipal agency's tenant interfaces and routes into inet.0 on the leaves. Why does that undermine multitenancy?
Select an answer to reveal the explanation.
Short Explanation
inet.0 is the town square—great for underlay, terrible as everyone's tenant apartment. Dump all agencies there and overlapping addresses, shared reachability, and accidental leaks become the default lifestyle. Routing instances exist so tenants do not share that square.
Full Explanation
Multitenancy depends on separate routing tables per tenant. Placing all tenant interfaces/routes in inet.0 merges them into the default unicast table and removes VRF-style isolation. Claims that inet.0 cannot hold a default, must use iso.0 for tenants, or is multicast-only are incorrect distractors. Keep underlay in appropriate tables and tenants in dedicated routing instances.