Capacity planning is per VLAN on chassis modules, so a small permitting application still burns a whole VLAN. Which traditional challenge is that?
Select an answer to reveal the explanation.
Short Explanation
Dedicating a whole VLAN and module to a tiny permitting app is using a city bus for two riders. Logical segments are sized to the app, not to the chassis. Overlay capacity is granular; chassis slots are not.
Full Explanation
Traditional capacity is often allocated in coarse units: a VLAN, a blade, or a firewall context, so even a small permitting application still consumes those units. NSX-T overlay segments are logical objects that do not each require a dedicated chassis module or core VLAN. Horizon pools are not a substitute for that network granularity, and NSX segments do not map one-to-one onto hardware modules.