Networking
⏱ ~3-min readAceMark GuideWhat this topic is really about
WPA3-Personal uses Pre-Shared Key authentication with Simultaneous Authentication of Equals (SAE) for secure connection.. WPA3-Personal replaces the WPA2 PSK 4-way handshake with SAE (Simultaneous Authentication of Equals) — still a passphrase but resistant to offline dictionary attacks.
A 169.254.x.x address is APIPA (Automatic Private IP Addressing), which Windows self-assigns when no DHCP server responds, allowing only local-subnet communication. A static IP would be whatever the admin set, and APIPA is not a public address.
See the mechanism
WPA3-Personal replaces the WPA2 PSK 4-way handshake with SAE, providing resistance to offline dictionary attacks. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.
An exam-style question, fully explained
A user must connect a Windows 11 PC to a Wi-Fi network that uses WPA3-Personal. Which authentication method is used?
- Identify what the question tests: A user must connect a Windows 11 PC to a Wi-Fi network that uses WPA3-Personal..
- WPA3-Personal replaces the WPA2 PSK 4-way handshake with SAE (Simultaneous Authentication of Equals) — still a passphrase but resistant to offline dictionary attacks.
- PEAP and EAP-TLS are WPA-Enterprise.
- WEP is the deprecated original Wi-Fi crypto.
- Why it matters: WPA3-Personal replaces the WPA2 PSK 4-way handshake with SAE, providing resistance to offline dictionary attacks. This method is specifically designed for personal use, as opposed to enterprise environments which use different authentication protocols like PEAP and EAP-TLS. The use of SAE enhances the security of the pre-shared key, making it more secure than older methods like WEP.
Traps the examiner sets
- Many people incorrectly assume that WPA3-Personal uses the same authentication methods as WPA2 or that it is similar to WPA-Enterprise authentication protocols. Others may confuse it with deprecated security protocols like WEP.
- If IP connectivity works but name resolution fails, DNS is the suspect — wrong DNS server, no DNS reachability, or a corrupted cache (try ipconfig /flushdns).
Test your recall
Answer each from memory — you'll see instantly whether you're right and why.
Run a focused 10-question mini-mock on Networking and see it stick.
Practice more of this topic →