Question 100
A home-lab analyst imports a PSK to a trace begun after association and wonders why the analyzer still cannot decode data frames. What repeated capture or telemetry pattern should trigger investigation?
Explanation
Correct Answer
Track missing key handshakes, decrypt failure counts, authorized key-handling logs, and protected capture access exceptions. The reported evidence is: A home-lab analyst imports a PSK to a trace begun after association and wonders why the analyzer still cannot decode data frames.
Incorrect Answers
Monitor capture mode, driver version, missed expected frame types, and adapter reset events during investigations. In the reported case: A home-lab analyst imports a PSK to a trace begun after association and wonders why the analyzer still cannot decode data frames. The decisive distinction is: Track missing key handshakes, decrypt failure counts, authorized key-handling logs, and protected capture access exceptions.
Track capture predicates, expected-versus-seen frame subtypes, missing station addresses, and analyst filter changes. The observed condition is: A home-lab analyst imports a PSK to a trace begun after association and wonders why the analyzer still cannot decode data frames. The decisive distinction is: Track missing key handshakes, decrypt failure counts, authorized key-handling logs, and protected capture access exceptions.
The option would address: Track trace provenance gaps, altered source files, undocumented capture settings and missing reproducibility evidence. The scenario instead reports: A home-lab analyst imports a PSK to a trace begun after association and wonders why the analyzer still cannot decode data frames. The decisive distinction is: Track missing key handshakes, decrypt failure counts, authorized key-handling logs, and protected capture access exceptions.