Question 180
A field analyst assumes the radiotap RSSI and channel fields printed before a captured beacon were bytes transmitted by the access point. What follow-up evidence should be trended across deployments?
Explanation
Correct Answer
Monitor inconsistent pseudo-header format, absent receiver channel fields, and decoder assumptions across capture adapters. The reported evidence is: A field analyst assumes the radiotap RSSI and channel fields printed before a captured beacon were bytes transmitted by the access point.
Incorrect Answers
Track missing RU metadata, unsupported HE/EHT PPDU formats and disagreement between trigger indications and decoder output. In the reported case: A field analyst assumes the radiotap RSSI and channel fields printed before a captured beacon were bytes transmitted by the access point. The decisive distinction is: Monitor inconsistent pseudo-header format, absent receiver channel fields, and decoder assumptions across capture adapters.
Trend unsupported PPDU decodes, PHY synchronization failures, training-field visibility and frame-decode fallbacks. The observed condition is: A field analyst assumes the radiotap RSSI and channel fields printed before a captured beacon were bytes transmitted by the access point. The decisive distinction is: Monitor inconsistent pseudo-header format, absent receiver channel fields, and decoder assumptions across capture adapters.
The option would address: Monitor unknown information elements, unrecognized PPDU types and advertised-versus-observed PHY disagreements. The scenario instead reports: A field analyst assumes the radiotap RSSI and channel fields printed before a captured beacon were bytes transmitted by the access point. The decisive distinction is: Monitor inconsistent pseudo-header format, absent receiver channel fields, and decoder assumptions across capture adapters.