This selects the overall queuing discipline the AP uses to service its QoS priority queues: weighted-fair(1) shares bandwidth proportionally across queues, while strict-priority(2) always services the highest-priority queue first. An admin picks strict-priority when a small amount of latency-critical traffic, like voice, must never wait behind bulk data, and weighted-fair when they want a fairer balance across all traffic classes. For example, an admin running mixed voice and data traffic over the same AP might switch qosQueueingMode to strict-priority(2) to guarantee voice frames are never queued behind large file transfers.