A network engineer at a high-density regional hospital is upgrading the facility's wireless infrastructure to improve security and auditability. The security policy mandates that every medical staff member must authenticate to the corporate SSID using their unique Active Directory credentials, allowing central logging of user sessions via 802.1X RADIUS. During the deployment planning, a technician proposes configuring WPA3-Personal with Simultaneous Authentication of Equals (SAE) and distributing unique static passphrases to staff groups to avoid modifying existing RADIUS server certificate policies. Which of the following best explains why the technician's proposed solution fails to meet the corporate security mandate, and what configuration must be enforced instead?
- WPA3-Personal using SAE relies on pre-shared passphrase authentication rather than centralized 802.1X RADIUS credential validation; WPA3-Enterprise must be deployed to integrate with Active Directory user identities.Answer
- BWPA3-Personal using SAE natively integrates with 802.1X EAP frameworks, but it fails because RADIUS servers require TACACS+ encapsulation to process SAE handshake tokens.
- CWPA3-Personal with SAE satisfies 802.1X RADIUS requirements, but it must be configured with TKIP encryption to support individual user credential tracking.
- DWPA3-Personal provides individual user authentication via SAE, but it is unusable in corporate settings because Protected Management Frames (PMF) are disabled in WPA3 modes.