A technician brings up a new 6 GHz SSID for the company's Wi-Fi 6E laptops and, to match the existing 5 GHz network, configures it for WPA2-Personal. The Wi-Fi 6E laptops can see other 6 GHz networks but never associate with this new SSID. What change should the technician make?
- ARe-enable TKIP alongside AES so older clients can negotiate a cipher.
- BReconfigure the SSID for WPA3, because the 6 GHz band does not permit WPA2. Correct
- CLower the 6 GHz channel width to 20 MHz so the laptops associate.
- DSwitch the 6 GHz SSID to an open network with no passphrase set.
Why A is wrong: A cipher mismatch sounds like a likely cause, but TKIP is prohibited on 6 GHz and would not be used by Wi-Fi 6E clients anyway, so re-enabling it does not fix the association failure.
Why B is correct: The 6 GHz band permits only WPA3-based security such as SAE, WPA3-Enterprise, or Enhanced Open, and prohibits WPA2, WEP, TKIP, and legacy open authentication, so a WPA2-Personal 6 GHz SSID is invalid and Wi-Fi 6E clients will not associate until it is set to WPA3.
Why C is wrong: Channel settings do affect wireless behaviour, which makes this tempting, but channel width does not block association; the actual barrier here is the disallowed security mode, not the width.
Why D is wrong: Removing security may seem to simplify joining, but legacy open authentication is also barred on 6 GHz and it would expose the network, so it neither restores association nor is acceptable.