A vendor asked the library for a unique physical QoS queue on every ToR for each civic application. How does software-defined networking reduce that hardware-queue sprawl?
Select an answer to reveal the explanation.
Short Explanation
A unique ToR queue per library app is like a reserved checkout lane for every book title. Software policy classifies and treats those apps without carving a hardware lane on every switch. Horizon protocol profiles and per-vNIC queues just grow the sprawl.
Full Explanation
Traditional designs often treat a unique physical queue or VLAN as the only way to mark or isolate each application. Software-defined networking applies policy to logical objects so civic apps do not each require a dedicated ToR queue. Creating a hardware queue per vNIC, mapping apps to Horizon desktop profiles, or disabling encapsulation so ToRs classify inner MACs increases physical sprawl instead of reducing it.