Question 600
A healthcare handset tries a first visit to a neighboring controller AP and an analyst assumes cached key state must exist. Which operational metric would most quickly reveal a repeat incident?
Explanation
Correct Answer
Track cache-hit indications, full-authentication fallback, PMKID mismatches and roaming interruption times. The reported evidence is: A healthcare handset tries a first visit to a neighboring controller AP and an analyst assumes cached key state must exist.
Incorrect Answers
Track RTS/CTS success, collision-related retries, hidden-station activity and throughput cost of protection. In the reported case: A healthcare handset tries a first visit to a neighboring controller AP and an analyst assumes cached key state must exist. The decisive distinction is: Track cache-hit indications, full-authentication fallback, PMKID mismatches and roaming interruption times.
Track extended weak-link dwell time, candidate signal advantage, late reassociations and client-specific retry growth. The observed condition is: A healthcare handset tries a first visit to a neighboring controller AP and an analyst assumes cached key state must exist. The decisive distinction is: Track cache-hit indications, full-authentication fallback, PMKID mismatches and roaming interruption times.
The option would address: Track OWE negotiation failures, transition-mode fallback and observed choice of protected versus legacy guest BSS. The scenario instead reports: A healthcare handset tries a first visit to a neighboring controller AP and an analyst assumes cached key state must exist. The decisive distinction is: Track cache-hit indications, full-authentication fallback, PMKID mismatches and roaming interruption times.