Question 620
An outpatient clinic handheld swaps between neighboring APs repeatedly while standing still near the border of their cells. What follow-up evidence should be trended across deployments?
Explanation
Correct Answer
Track roam rate, short BSSID dwell times, backtrack transitions and user latency spikes. The reported evidence is: An outpatient clinic handheld swaps between neighboring APs repeatedly while standing still near the border of their cells.
Incorrect Answers
Track EAP retries, method failures, authorization transitions and missing subsequent four-way exchanges. In the reported case: An outpatient clinic handheld swaps between neighboring APs repeatedly while standing still near the border of their cells. The decisive distinction is: Track roam rate, short BSSID dwell times, backtrack transitions and user latency spikes.
Track group-key retransmissions, multicast loss during GTK updates and client acknowledgements of rotation events. The observed condition is: An outpatient clinic handheld swaps between neighboring APs repeatedly while standing still near the border of their cells. The decisive distinction is: Track roam rate, short BSSID dwell times, backtrack transitions and user latency spikes.
The option would address: Track missed DTIM wakeups, TIM-indicated backlog, multicast loss and client power-save listen behavior. The scenario instead reports: An outpatient clinic handheld swaps between neighboring APs repeatedly while standing still near the border of their cells. The decisive distinction is: Track roam rate, short BSSID dwell times, backtrack transitions and user latency spikes.