Question 360
A stadium trace contains RTS and CTS exchanges with duration values, yet the reviewer treats both as application data frames. What trend should the WLAN team monitor after the correction?
Explanation
Correct Answer
Trend RTS success, CTS response rate, NAV reservation patterns and retries under changing contention. The reported evidence is: A stadium trace contains RTS and CTS exchanges with duration values, yet the reviewer treats both as application data frames.
Incorrect Answers
Trend negotiated AKM choices, security downgrades, RSN mismatches and association rejections by client class. In the reported case: A stadium trace contains RTS and CTS exchanges with duration values, yet the reviewer treats both as application data frames. The decisive distinction is: Trend RTS success, CTS response rate, NAV reservation patterns and retries under changing contention.
Track unanswered triggers, user-allocation mismatches and multiuser uplink decode failures. The observed condition is: A stadium trace contains RTS and CTS exchanges with duration values, yet the reviewer treats both as application data frames. The decisive distinction is: Trend RTS success, CTS response rate, NAV reservation patterns and retries under changing contention.
The option would address: Monitor address-role decoding anomalies, bridge-frame assumptions and incorrect source-destination attribution in incident reports. The scenario instead reports: A stadium trace contains RTS and CTS exchanges with duration values, yet the reviewer treats both as application data frames. The decisive distinction is: Trend RTS success, CTS response rate, NAV reservation patterns and retries under changing contention.