A legacy wireless client, supporting WPA2 security, cannot associate to a guest wireless network. What is the cause?

The correct answer is D. The guest wireless network is configured with Opportunistic Wireless Encryption (OWE) with. OWE replaces the open-security handshake with encryption but requires clients to support the newer OWE and mandatory management-frame protection (802.11w). A legacy WPA2-only client cannot perform the OWE handshake or satisfy required 802.11w, so it fails to associate.

Cisco Meraki Wireless Solutions

Question

Options

AThe guest wireless network is configured with layer 2 LAN isolation.
BThe guest wireless network is configured with Open (no encryption).
CThe guest wireless network is configured with WPA3 transition mode with 802.1w set to "Enabled."
DThe guest wireless network is configured with Opportunistic Wireless Encryption (OWE) with

How the community answered

(22 responses)

A
5% (1)
B
14% (3)
C
9% (2)
D
73% (16)

Explanation

OWE replaces the open-security handshake with encryption but requires clients to support the newer OWE and mandatory management-frame protection (802.11w). A legacy WPA2-only client cannot perform the OWE handshake or satisfy required 802.11w, so it fails to associate.

Topics

#OWE transition mode#WPA3#legacy client compatibility#wireless security

Community Discussion

No community discussion yet for this question.

Full 500-220 Practice