A customer wants FSR and certificate-based authentication. The solution must be simple to deploy. Which method should be used to meet the requirements?

EAP-TLS requires client-side certificates, significantly complicating deployment and management for large-scale environments.

PEAP-MSCHAPv2 primarily uses username and password credentials for client authentication, not certificate-based authentication for the client.

EAP-FAST supports Protected Access Credentials (PACs) for efficient session resumption (FSR) and can be configured for server-side certificate authentication without requiring client-side certificates, which simplifies its deployment compared to methods like EAP-TLS.

PEAP-MSCHAPv2 machine authentication uses machine account credentials, which is still not certificate-based authentication for the client and does not inherently offer FSR.