NSE4 Authentication and VPN Practice Question
An organization wants to use FortiToken for two-factor authentication on SSL VPN logins. Which authentication method must be enabled on the FortiGate to support this?
⚠ Common exam trap
Many candidates confuse the authentication method required for FortiToken with external servers like RADIUS or LDAP, not realizing that FortiToken is a Fortinet-proprietary two-factor solution that must be explicitly enabled as a two-factor method on the FortiGate itself.
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
✓
Two-factor authentication with FortiToken
FortiToken is a hardware or software token that generates one-time passwords (OTPs) for two-factor authentication (2FA). To use FortiToken with SSL VPN logins, the FortiGate must have 'Two-factor authentication with FortiToken' enabled in the user or user group configuration. This setting tells the FortiGate to prompt for both the user's regular password and the current FortiToken OTP during the SSL VPN authentication process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Two-factor authentication with FortiToken
Why this is correct
The 'Two-factor authentication with FortiToken' setting on a FortiGate enables the native token-based OTP mechanism, where users must provide both their primary password and a one-time passcode generated by a FortiToken device or mobile token. This is the correct option because it directly activates the FortiToken two-factor authentication feature within FortiOS, ensuring that the token OTP is validated as part of the authentication process. It is distinct from external protocols or directory services, as it is built-in and specifically designed for FortiToken integration.
- ✗
RADIUS authentication
Why it's wrong here
RADIUS authentication is an external AAA protocol that can be used to offload authentication to a RADIUS server, and while a RADIUS server could be configured to validate OTP tokens from various vendors, it is not the native FortiToken method. Choosing RADIUS would not directly enable FortiToken two-factor authentication on the FortiGate itself; instead, the FortiGate would rely on the RADIUS server to handle the token verification, which is an indirect and non-specific approach. The question asks for the setting that enables FortiToken, so RADIUS is incorrect because it is a protocol for external authentication, not the built-in token-based mechanism.
- ✗
PKI authentication
Why it's wrong here
PKI authentication relies on digital certificates and asymmetric cryptography to verify user identity, requiring a certificate installed on the client or a smartcard, rather than a one-time password from a token. This method does not involve FortiToken at all, as FortiToken generates time-based or event-based OTP codes that are completely different from certificate-based credentials. Therefore, selecting PKI authentication would not enable FortiToken two-factor authentication, making it an incorrect answer because it substitutes a certificate-based mechanism for the OTP-based approach the organization needs.
- ✗
LDAP authentication
Why it's wrong here
LDAP authentication is a directory access protocol used to query and validate user credentials against a central directory server such as Active Directory or OpenLDAP; it does not provide any OTP generation or token verification capabilities. While LDAP can serve as a backend for user accounts, it would only authenticate the password portion and would not invoke FortiToken for a second factor, so it fails to implement two-factor authentication. The correct two-factor behavior requires an OTP source, which LDAP cannot offer, making this option wrong because it is a directory protocol, not a token-based authentication method.
Quick reference
VPN Protocol Comparison
| Protocol | Port | Encryption | Authentication | Use Case |
|---|---|---|---|---|
| IKEv2 / IPsec | UDP 500 / 4500 | AES-256 | Certificates / PSK | Site-to-site & remote access |
| SSL / TLS VPN | TCP 443 | TLS 1.3 | Certificates / MFA | Clientless remote access |
| L2TP / IPsec | UDP 1701 | AES (IPsec) | PSK / Certificates | Legacy remote access |
| WireGuard | UDP 51820 | ChaCha20 | Public keys | Modern high-performance VPN |
| PPTP | TCP 1723 | MPPE (weak) | MS-CHAPv2 | Legacy — avoid in production |
PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.
Go deeper
Related to this question
About these practice questions
One of 773 original NSE4 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE4 practice question is part of Courseiva's free Fortinet 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 NSE4 exam.