Question 550
A stadium display client receives unicast traffic but loses group-addressed media following a GTK update event. What follow-up evidence should be trended across deployments?
Explanation
Correct Answer
Track group-key retransmissions, multicast loss during GTK updates and client acknowledgements of rotation events. This addresses the decisive observation: A stadium display client receives unicast traffic but loses group-addressed media following a GTK update event.
Incorrect Answers
The option would address: Track EAP retries, method failures, authorization transitions and missing subsequent four-way exchanges. The scenario instead reports: A stadium display client receives unicast traffic but loses group-addressed media following a GTK update event. The decisive distinction is: Track group-key retransmissions, multicast loss during GTK updates and client acknowledgements of rotation events.
Track RTS/CTS success, collision-related retries, hidden-station activity and throughput cost of protection. In the reported case: A stadium display client receives unicast traffic but loses group-addressed media following a GTK update event. The decisive distinction is: Track group-key retransmissions, multicast loss during GTK updates and client acknowledgements of rotation events.
Track agreement failures, bitmap gaps, selective retry volume and aggregation throughput under load. The observed condition is: A stadium display client receives unicast traffic but loses group-addressed media following a GTK update event. The decisive distinction is: Track group-key retransmissions, multicast loss during GTK updates and client acknowledgements of rotation events.