Question 290
A voice station marks a QoS data frame with a low TID while a dashboard assumes all traffic from that SSID uses the voice queue. What trend should the WLAN team monitor after the correction?
Explanation
Correct Answer
Trend TID distributions, DSCP-to-user-priority mismatches and voice frames falling into unexpected access categories. This addresses the decisive observation: A voice station marks a QoS data frame with a low TID while a dashboard assumes all traffic from that SSID uses the voice queue.
Incorrect Answers
The option would address: Track beacon timing jitter, apparent missed beacons and power-save wake coordination over repeated capture windows. The scenario instead reports: A voice station marks a QoS data frame with a low TID while a dashboard assumes all traffic from that SSID uses the voice queue. The decisive distinction is: Trend TID distributions, DSCP-to-user-priority mismatches and voice frames falling into unexpected access categories.
Track unacknowledged unicast attempts, ACK visibility at two viewpoints and control-frame decode loss. In the reported case: A voice station marks a QoS data frame with a low TID while a dashboard assumes all traffic from that SSID uses the voice queue. The decisive distinction is: Trend TID distributions, DSCP-to-user-priority mismatches and voice frames falling into unexpected access categories.
Trend partial acknowledgment density, selected MPDU retransmissions and block-ack window stalls. The observed condition is: A voice station marks a QoS data frame with a low TID while a dashboard assumes all traffic from that SSID uses the voice queue. The decisive distinction is: Trend TID distributions, DSCP-to-user-priority mismatches and voice frames falling into unexpected access categories.