This read-write setting selects the queue-scheduling algorithm applied across the switch's priority queues: an 8:4:2:1 weighted round-robin scheme that services queues from highest to lowest in that ratio, or strict priority, where a higher queue is always serviced completely before a lower one is touched. An admin chooses strict priority when latency-sensitive traffic must never wait behind bulk data, accepting the risk that heavy high-priority load could starve lower queues. For example, choosing strictPriority(2) on a network carrying VoIP guarantees voice packets in the top queue are always transmitted first, even if that means best-effort file transfers in the lowest queue occasionally get delayed.