Question 540
A remote clinic trace shows EAPOL-Key messages repeating out of sequence, and the help desk incorrectly blames DHCP. Which recurring measurement would best detect the problem returning?
Explanation
Correct Answer
Track failed four-way completion, EAPOL-Key retransmissions, replay-counter anomalies and missing protected data. The reported evidence is: A remote clinic trace shows EAPOL-Key messages repeating out of sequence, and the help desk incorrectly blames DHCP.
Incorrect Answers
Trend discovery-to-authentication gap, incomplete join sequences and repeated scan attempts at failing client locations. In the reported case: A remote clinic trace shows EAPOL-Key messages repeating out of sequence, and the help desk incorrectly blames DHCP. The decisive distinction is: Track failed four-way completion, EAPOL-Key retransmissions, replay-counter anomalies and missing protected data.
Track missed DTIM wakeups, TIM-indicated backlog, multicast loss and client power-save listen behavior. The observed condition is: A remote clinic trace shows EAPOL-Key messages repeating out of sequence, and the help desk incorrectly blames DHCP. The decisive distinction is: Track failed four-way completion, EAPOL-Key retransmissions, replay-counter anomalies and missing protected data.
The option would address: Track group-key retransmissions, multicast loss during GTK updates and client acknowledgements of rotation events. The scenario instead reports: A remote clinic trace shows EAPOL-Key messages repeating out of sequence, and the help desk incorrectly blames DHCP. The decisive distinction is: Track failed four-way completion, EAPOL-Key retransmissions, replay-counter anomalies and missing protected data.