Courseiva
Network Infrastructure and ConnectivityhardMultiple ChoiceObjective-mapped

CCNA Network Infrastructure and Connectivity Practice Question

An administrator deploys a new WLAN on a Cisco 9800 WLC using WPA3-Personal (SAE) with AES encryption. A single 802.11ax laptop running Windows 10 fails to connect, displaying an authentication timeout despite entering the correct passphrase. Other clients, including legacy 802.11ac devices, connect without issue.

⚠ Common exam trap

Cisco often tests the mandatory dependency of Protected Management Frames (802.11w) for WPA3-Personal, leading candidates to incorrectly attribute the failure to channel width or OFDMA incompatibility.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The laptop’s wireless adapter does not support Protected Management Frames, which are mandatory for WPA3-Personal.

WPA3-Personal (SAE) mandates the use of Protected Management Frames (PMF) as defined in IEEE 802.11w. If the laptop's wireless adapter or driver does not support PMF, it cannot complete the SAE handshake, resulting in an authentication timeout. Legacy 802.11ac clients can connect because they are using WPA2, which does not require PMF.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The WLC’s WLAN is misconfigured for WPA3-Enterprise, and the laptop lacks a supplicant for 802.1X authentication.

    Why it's wrong here

    This option contradicts the scenario, which explicitly states the WLAN is configured for WPA3-Personal using the SAE protocol with a pre-shared key. WPA3-Personal does not use 802.1X/EAP or RADIUS at all, so a missing 802.1X supplicant would be irrelevant. Even if the network were WPA3-Enterprise, authentication failure would manifest as EAPOL timeouts during the 802.1X phase, not as a failure to establish PMF during association.

  • The laptop’s wireless adapter does not support Protected Management Frames, which are mandatory for WPA3-Personal.

    Why this is correct

    For WPA3-Personal, the client and access point must negotiate Protected Management Frames (PMF) as part of the RSN information element during association; PMF is not optional but mandatory in WPA3. If the laptop's wireless adapter does not advertise or enable the Management Frame Protection Capable bit, the WLC cannot complete the handshake, causing SAE authentication to time out. This explains why only this 802.11ax-capable device fails while others succeed—it reflects a client-side capability gap, not a network-wide configuration error.

  • The WLC has disabled 802.11ax OFDMA on the 5 GHz band, preventing the 802.11ax laptop from associating.

    Why it's wrong here

    OFDMA is a 802.11ax data-plane feature that schedules subchannel resource units for more efficient transmissions after a client has successfully associated and authenticated. Disabling 802.11ax OFDMA on the 5 GHz band would not prevent a station from sending association requests or completing WPA3 authentication; it may degrade throughput or multi-user efficiency, but association itself remains unaffected. Therefore, this setting cannot explain why the laptop fails to associate, making the option incorrect.

  • The laptop’s driver is configured for 160 MHz channel width, which is incompatible with the WLC’s channel plan, causing authentication to fail.

    Why it's wrong here

    Channel width support is negotiated during the association process, but a mismatch does not prevent the initial authentication frames from being exchanged. If the laptop is configured for 160 MHz while the WLC uses a channel plan that does not permit that width, the client will typically fall back to a smaller supported width, such as 80 MHz or 40 MHz, based on the AP's beacons and the negotiated capabilities. This may reduce performance or cause channel switching, but it will not cause an authentication failure, so this option is not a valid cause of the problem.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.

The laptop’s wireless adapter does not support Protected Management Frames, which are mandatory for WPA3-Personal.Correct answer

Why this is correct

For WPA3-Personal, the client and access point must negotiate Protected Management Frames (PMF) as part of the RSN information element during association; PMF is not optional but mandatory in WPA3. If the laptop's wireless adapter does not advertise or enable the Management Frame Protection Capable bit, the WLC cannot complete the handshake, causing SAE authentication to time out. This explains why only this 802.11ax-capable device fails while others succeed—it reflects a client-side capability gap, not a network-wide configuration error.

The WLC’s WLAN is misconfigured for WPA3-Enterprise, and the laptop lacks a supplicant for 802.1X authentication.Wrong answer — click to see why

Why this is wrong here

Misidentifying the WLAN security type: WPA3-Personal does not require an enterprise supplicant, so this is not the cause.

The WLC has disabled 802.11ax OFDMA on the 5 GHz band, preventing the 802.11ax laptop from associating.Wrong answer — click to see why

Why this is wrong here

Confusing radio resource management with connection establishment: OFDMA settings do not block initial association, only data transmission efficiency.

The laptop’s driver is configured for 160 MHz channel width, which is incompatible with the WLC’s channel plan, causing authentication to fail.Wrong answer — click to see why

Why this is wrong here

Misattributing connection failures to channel bandwidth settings; these are negotiated after successful association and do not impact the 802.11 authentication and association phases.

Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

Symmetric Encryption Algorithm Comparison

AlgorithmKey SizeBlock SizeStatusNotes
AES-128128-bit128-bitCurrent standardNIST approved; WPA3, TLS
AES-256256-bit128-bitCurrent standardPreferred for sensitive / govt data
3DES112-bit effective64-bitDeprecated (2023)Replaced by AES
DES56-bit64-bitBrokenCracked in < 24 h; never deploy
ChaCha20256-bitStream cipherCurrentTLS 1.3, WireGuard

About these practice questions

One of 1,389 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.