Question 560
At fictional Cedar Health Devices, a Wi-Fi specialist is investigating Wi-Fi for wireless nurse-call readiness in a campus service zone. The source issue is: A client stays associated with a distant AP despite a nearer option, and the incident report calls it an AP-forced roam failure. Stakeholders require a decision grounded in documented RF, 802.11 frame and authorized capture evidence. Which ongoing WLAN-analysis or troubleshooting safeguard best prevents recurrence of this problem?
Explanation
Writer-proposed answer: D (UNVERIFIED)
Preliminary per-option explanations — NOT independently validated
Correct Answer
Roaming selection is substantially client-driven, subject to network steering features and policy. The timeline confirms continued association choices without assuming the AP directly controls every client roam.
Incorrect Answers
Dhcp separated from wi-fi join is not sufficient. Roaming selection is substantially client-driven, subject to network steering features and policy.
Qos null trigger delivery is not the controlling issue in this scenario. Roaming selection is substantially client-driven, subject to network steering features and policy.
802.11k neighbor report effect alone does not resolve the issue. Roaming selection is substantially client-driven, subject to network steering features and policy.