Question 680
A stadium capture shows sounding exchanges yet no proof of multiuser payload scheduling under the test traffic. Which recurring measurement would best detect the problem returning?
Explanation
Correct Answer
Track sounding events, actual multiuser PPDU use, NSS capability differences and decoder uncertainty. The reported evidence is: A stadium capture shows sounding exchanges yet no proof of multiuser payload scheduling under the test traffic.
Incorrect Answers
Trend protection-frame overhead, retries with legacy stations present and unexpected NAV reservation changes. In the reported case: A stadium capture shows sounding exchanges yet no proof of multiuser payload scheduling under the test traffic. The decisive distinction is: Track sounding events, actual multiuser PPDU use, NSS capability differences and decoder uncertainty.
Track cache-hit indications, full-authentication fallback, PMKID mismatches and roaming interruption times. The observed condition is: A stadium capture shows sounding exchanges yet no proof of multiuser payload scheduling under the test traffic. The decisive distinction is: Track sounding events, actual multiuser PPDU use, NSS capability differences and decoder uncertainty.
The option would address: Track negotiated AKM distribution, unexpected PSK fallback and incompatible-client association failures. The scenario instead reports: A stadium capture shows sounding exchanges yet no proof of multiuser payload scheduling under the test traffic. The decisive distinction is: Track sounding events, actual multiuser PPDU use, NSS capability differences and decoder uncertainty.