A transit agency’s Windows-heavy fleet will authenticate to staff Wi-Fi with usernames and passwords protected inside a TLS tunnel, typically using MSCHAPv2. Which EAP method is that common pattern?
Select an answer to reveal the explanation.
Short Explanation
PEAP is the familiar ‘password in a TLS envelope’ path many Windows shops use—often MSCHAPv2 inside. It’s not the same as forcing client certs (EAP-TLS), and it’s not a shared PSK or a MAC allow-list.
Full Explanation
PEAP is widely deployed for enterprise WLAN with Windows clients: the server authenticates via certificate, a TLS tunnel protects the inner method, and MSCHAPv2 is a common inner authentication. That differs from EAP-TLS client certificates, Personal PSK designs, and MAC-only admission. Candidates should know PEAP protects the inner exchange in the tunnel but still depends on password hygiene and proper server-cert validation.