Courseiva

CCNA Nse4 Auth Vpn Questions

73 of 148 questions · Page 2/2 · Nse4 Auth Vpn topic · Answers revealed

76
Multi-Selectmedium

An administrator is configuring an IPsec VPN between two FortiGates using IKEv1. The tunnel must use main mode and support multiple subnets behind each gate. Which Phase2 settings are required to allow multiple subnets? (Choose two.)

Select 2 answers
A.Set the Phase2 keylife to a higher value
B.Set the Phase2 proposal to include multiple encryption algorithms
C.Create multiple Phase2 selectors, each with different local and remote subnets
D.Enable NAT traversal on the Phase2
E.Use address objects that contain multiple subnets in the Phase2 definition
AnswersC, E

Each Phase2 selector defines exactly one local subnet and one remote subnet pair for a given security association. Creating multiple Phase2 entries under the same Phase1 lets you assign different subnet pairs to the same tunnel, allowing the FortiGate to pick the matching SA for each traffic flow. This is the standard, granular method for supporting multiple subnets across a single IPsec tunnel.

Why this answer

IKEv1 main mode requires that each pair of local and remote subnets be defined in its own Phase2 selector. This allows the VPN to establish separate security associations (SAs) for each subnet pair, enabling multiple subnets behind each FortiGate. Option E is also correct because using address objects that contain multiple subnets (e.g., a subnet group or address range) in a single Phase2 definition is a supported method to negotiate a single SA covering all those subnets, reducing the number of Phase2 selectors needed.

Exam trap

The trap here is that candidates often confuse Phase2 settings (like encryption algorithms or keylife) with the mechanism for defining multiple subnets, leading them to select options that affect security or performance rather than subnet selection.

77
MCQmedium

A network administrator is troubleshooting an IPsec VPN tunnel between two FortiGates. Phase 1 is up, but Phase 2 fails to establish. The debug command 'diagnose vpn ike log' shows: 'no suitable proposal found'. What is the most likely cause?

A.Phase 2 encryption or authentication algorithms do not match on both sides.
B.The firewall policy allowing IPsec traffic is missing.
C.The remote gateway IP address is unreachable.
D.The pre-shared key is incorrect.
AnswerA

Phase 2 (Quick Mode) negotiates the IPsec SA parameters, including the encryption algorithm (e.g., AES-256, 3DES) and authentication algorithm (e.g., SHA-1, SHA-256) for the ESP/AH protocol. If the local and remote firewalls do not offer a common proposal for these algorithms and the Diffie-Hellman group, the Phase 2 negotiation will fail with an error such as 'no proposal chosen.' Since Phase 1 has already formed a secure IKE SA, the problem isolates specifically to a Phase 2 proposal mismatch, preventing the tunnel from establishing even though both gateways are reachable and authenticated.

Why this answer

The 'no suitable proposal found' error in Phase 2 of an IPsec VPN tunnel indicates that the Phase 2 parameters (encryption algorithm, authentication algorithm, or PFS settings) do not match between the two FortiGate peers. Since Phase 1 is up, the IKE SA is established, meaning pre-shared keys, remote gateway reachability, and basic firewall policies for IKE traffic are correct. The mismatch specifically occurs in the Phase 2 proposal negotiation, where each side sends its supported transforms and the responder cannot find a common set.

Exam trap

The trap here is that candidates often confuse Phase 1 and Phase 2 proposal errors, assuming any 'no suitable proposal found' message relates to Phase 1, but the context of Phase 1 being up explicitly isolates the issue to Phase 2 parameter mismatch.

How to eliminate wrong answers

Option B is wrong because a missing firewall policy for IPsec traffic would prevent Phase 1 from establishing, as IKE packets (UDP 500/4500) would be dropped; Phase 1 being up confirms the firewall policy is in place. Option C is wrong because if the remote gateway IP address were unreachable, Phase 1 would fail to initiate or complete, as IKE negotiation requires bidirectional reachability. Option D is wrong because an incorrect pre-shared key would cause Phase 1 authentication to fail, resulting in a 'no suitable proposal found' error at Phase 1, not Phase 2; Phase 1 being up confirms the pre-shared key is correct.

78
MCQmedium

An administrator runs 'diagnose vpn ike config' and sees the output includes 'P2 proposals: aes128-sha256, aes256-sha1'. What does this indicate?

A.The Diffie-Hellman groups for Phase 2
B.The Phase 1 encryption settings
C.The Phase 2 encryption and authentication algorithms
D.The lifetime settings for the VPN tunnel
AnswerC

The 'diagnose vpn ike config' command in FortiOS prints the Phase 2 proposal, which lists the exact ESP (Encapsulating Security Payload) transforms: the encryption algorithm (e.g., AES-GCM, AES-CBC) and the authentication/integrity algorithm (e.g., SHA-256, SHA-1). This is precisely what the administrator sees in the output, making it the correct answer. It reflects the algorithms that will be used for the actual IPsec data tunnel.

Why this answer

The output 'P2 proposals: aes128-sha256, aes256-sha1' from the 'diagnose vpn ike config' command specifically lists the Phase 2 (IPsec) proposals, which define the encryption and authentication algorithms used for protecting data traffic. Option C is correct because these are the Phase 2 encryption (aes128, aes256) and authentication (sha256, sha1) algorithms, not Phase 1 settings or other parameters.

Exam trap

The trap here is that candidates often confuse Phase 1 and Phase 2 parameters, assuming 'P2 proposals' includes Diffie-Hellman groups or lifetimes, when in fact it only specifies the encryption and authentication algorithms for the IPsec SA.

How to eliminate wrong answers

Option A is wrong because Diffie-Hellman groups for Phase 2 are not listed in this output; DH groups are typically configured in Phase 1 (IKE) and optionally in Phase 2 for PFS, but the output shows only encryption and authentication algorithms, not DH group identifiers. Option B is wrong because Phase 1 encryption settings are shown under 'P1 proposals' or similar fields in the command output, not under 'P2 proposals', which is explicitly for Phase 2. Option D is wrong because lifetime settings for the VPN tunnel (e.g., 3600 seconds or 100 MB) are displayed separately in the output, often under 'P2 lifetime' or 'IPsec SA lifetime', not in the 'P2 proposals' line.

79
MCQeasy

In Fortinet ZTNA, what is the primary purpose of the ZTNA access proxy component?

A.To act as a forward proxy for web traffic
B.To provide load balancing for multiple FortiGates
C.To proxy connections to internal applications after authentication and device verification
D.To terminate IPsec VPN tunnels
AnswerC

This is the correct function: the ZTNA access proxy acts as a reverse proxy that terminates client requests to internal applications, enforcing authentication (often via SAML/OIDC) and device verification (via FortiClient EMS) before proxying the connection to the actual application server. This creates a zero-trust access model where access is granted per application, per user, and per device, rather than allowing broad network-level connectivity.

Why this answer

The ZTNA access proxy is the core component that mediates user access to internal applications. It intercepts client requests, enforces authentication and device posture checks (via FortiClient telemetry), and then proxies the connection to the protected application. This ensures no direct network access is granted; all traffic must pass through the proxy, which validates trust before forwarding.

Exam trap

The trap here is that candidates confuse the ZTNA access proxy with a forward proxy or VPN concentrator, but Fortinet specifically designed it as a reverse proxy for internal application access, not for general web proxying or tunnel termination.

How to eliminate wrong answers

Option A is wrong because the ZTNA access proxy is a reverse proxy that protects internal applications, not a forward proxy that handles outbound web traffic from clients to the internet. Option B is wrong because load balancing between FortiGates is handled by FortiGate's built-in SD-WAN or external load balancers, not by the ZTNA access proxy component. Option D is wrong because IPsec VPN termination is a separate function of the FortiGate's VPN module, unrelated to the ZTNA access proxy's role in proxying application-layer connections.

80
MCQhard

An administrator configures a dial-up IPsec VPN with IKEv1 main mode. Remote clients can connect successfully, but the administrator notices that the Phase 1 negotiation takes a long time. Which change would most improve the negotiation speed without compromising security?

A.Switch from main mode to aggressive mode
B.Reduce the IKE SA lifetime
C.Increase the number of Phase 1 proposals
D.Enable IKEv2 instead of IKEv1
AnswerD

IKEv2 replaces the 6-message main mode exchange with a compact 4-message exchange by combining SA negotiation and key derivation, and then performing authentication with the same two messages. This halves the round-trip time in the common no-NAT case and also reduces the number of packets that must be processed in parallel. Additionally, IKEv2 supports built-in NAT traversal, and is more resilient to errors because each pair of messages is cryptographically tied together, providing a faster and more robust negotiation than IKEv1 main mode.

Why this answer

IKEv2 reduces Phase 1 negotiation time by using a single exchange of two messages (request/response) instead of IKEv1 main mode's six messages. This eliminates the extra round trips required for identity protection and SA negotiation, speeding up the process without reducing security. The question specifies IKEv1 main mode, so switching to IKEv2 directly addresses the slow negotiation while maintaining strong cryptographic protections.

Exam trap

The trap here is that candidates often choose aggressive mode (Option A) because it reduces round trips, but they overlook that it sends the peer identity in cleartext, which violates the security requirement in the question.

How to eliminate wrong answers

Option A is wrong because aggressive mode reduces round trips but sends the peer's identity in cleartext before the tunnel is established, compromising security by exposing the identity to eavesdroppers. Option B is wrong because reducing the IKE SA lifetime does not speed up initial Phase 1 negotiation; it only causes more frequent rekeying, which can actually increase overall negotiation overhead. Option C is wrong because increasing the number of Phase 1 proposals forces the initiator to attempt more combinations during negotiation, which can slow down the process rather than speed it up.

81
MCQmedium

A network admin configures an IPsec VPN between two FortiGates using IKEv2. Phase 1 completes successfully, but Phase 2 fails to establish. The admin runs 'diagnose vpn ike log' and sees the error 'proposal mismatch'. What is the most likely cause?

A.The IKE version is not compatible
B.The Phase 2 selectors (local and remote subnets) are misconfigured
C.The Phase 2 encryption and authentication algorithms do not match
D.The pre-shared keys do not match
AnswerC

The correct interpretation of the 'proposal mismatch' error is that the Phase 2 encryption and authentication algorithms, or other transform parameters like the PFS Diffie-Hellman group, differ between the two FortiGates. During IKE Phase 2, the initiator sends a list of SA proposals containing encryption algorithms (e.g., AES128/256), integrity algorithms (e.g., SHA1/256), and optionally DH groups for PFS. If none of the responder's configured Phase 2 proposals match any of the initiator's proposals, the responder sends the 'no proposal chosen' or 'proposal mismatch' notification. To resolve this, the Phase 2 transform sets (encryption, authentication, and PFS) must be aligned on both endpoints.

Why this answer

The error 'proposal mismatch' in the 'diagnose vpn ike log' output specifically indicates that the Phase 2 parameters (encryption, authentication, or DH group) do not match between the two FortiGate peers. Since Phase 1 completed successfully, the IKE version (IKEv2) and pre-shared keys are already validated, leaving only the Phase 2 proposal as the cause. Option C correctly identifies that the encryption and authentication algorithms are mismatched, which is the most common reason for this error.

Exam trap

The trap here is that candidates often confuse 'proposal mismatch' with Phase 1 issues or selector mismatches, but the error is specific to cryptographic algorithm negotiation in Phase 2, not to network-layer subnet definitions or authentication credentials.

How to eliminate wrong answers

Option A is wrong because Phase 1 completed successfully, which confirms that both peers are using a compatible IKE version (IKEv2 in this scenario). Option B is wrong because a 'proposal mismatch' error is related to cryptographic parameters, not to the local/remote subnet selectors; a misconfiguration of selectors would typically result in a 'no matching selector' or 'traffic selector mismatch' error, not 'proposal mismatch'. Option D is wrong because pre-shared keys are negotiated during Phase 1 authentication; since Phase 1 succeeded, the PSKs must match, so a PSK mismatch would have prevented Phase 1 from completing.

82
MCQmedium

What is the primary advantage of using IKEv2 over IKEv1 for IPsec VPN?

A.IKEv2 has built-in support for NAT traversal and MOBIKE
B.IKEv2 supports only main mode
C.IKEv2 requires aggressive mode
D.IKEv2 is only for route-based VPN
AnswerA

IKEv2 natively integrates NAT traversal and MOBIKE, letting a tunnel survive IP address changes when a device roams between networks. IKEv1 requires separate NAT-T negotiation and lacks MOBIKE entirely, so sessions break on address change. This directly satisfies the stem's demand for IKEv2's primary advantage over IKEv1.

Why this answer

IKEv2 offers built-in NAT traversal (NAT-T) and MOBIKE (RFC 4555) as core features, not optional extensions. This eliminates the need for separate RFC 3947 NAT-T configuration and allows seamless IP address changes during a VPN session, making it far more robust for mobile users and dynamic environments compared to IKEv1.

Exam trap

The trap here is that candidates often confuse IKEv2's single exchange with 'main mode only' or think it requires aggressive mode, when in fact IKEv2 eliminates both modes and uses a more efficient, secure handshake.

How to eliminate wrong answers

Option B is wrong because IKEv2 does not support only main mode; it uses a single, streamlined exchange (two pairs of messages) that replaces both main and aggressive modes from IKEv1. Option C is wrong because IKEv2 does not require aggressive mode; aggressive mode is an IKEv1 concept that IKEv2 eliminates entirely for security reasons. Option D is wrong because IKEv2 is not limited to route-based VPNs; it supports both policy-based and route-based IPsec VPN configurations in FortiOS.

83
Multi-Selecthard

A company sets up a hub-and-spoke IPsec VPN where all spokes must communicate through the hub. The hub uses policy-based IPsec. Which THREE configurations are required on the hub to allow spoke-to-spoke traffic? (Select three.)

Select 3 answers
A.Configure IKEv2 instead of IKEv1
B.Separate phase2 selectors defining traffic between each pair of spokes
C.Static routes for each spoke's subnet pointing to the respective VPN interface
D.Firewall policies allowing traffic from each spoke's interface to the other spoke's interface
E.Enable NAT on the hub for spoke-to-spoke traffic
AnswersB, C, D

A policy-based IPsec VPN relies on phase2 selectors (proxy IDs) to define exactly which source and destination subnet pairs are protected by a given SA. When the hub receives traffic from Spoke A destined for Spoke B, the hub performs a route lookup and then matches the traffic against its phase2 selectors to determine which IPsec tunnel and SA to use. Without a selector covering the Spoke-A-to-Spoke-B pair—or a broad selector like 0.0.0.0/0 for all subnets—the hub has no matching SA and will drop the traffic or send it unencrypted, depending on the firewall policy. This is the root requirement for hub-and-spoke spoke-to-spoke connectivity.

Why this answer

In a hub-and-spoke policy-based IPsec VPN, the hub must have separate phase2 selectors for each spoke-to-spoke traffic flow because policy-based VPNs define encryption domains per pair of subnets. Without these selectors, the hub cannot match spoke-to-spoke traffic to a specific IPsec SA, and the traffic will be dropped or sent unencrypted.

Exam trap

The trap here is that candidates often think enabling NAT or changing IKE version will solve the routing or encryption issue, but the core requirement is the phase2 selectors and proper routing/firewall policies to allow the hub to forward and encrypt inter-spoke traffic.

84
Multi-Selectmedium

A FortiGate administrator is troubleshooting an SSL VPN issue where remote users cannot access internal resources after successful authentication. Which TWO steps should the admin take to resolve the issue? (Select two.)

Select 2 answers
A.Verify that a firewall policy exists allowing traffic from the SSL VPN interface to the internal network
B.Increase the authentication timeout
C.Check the routing table on the FortiGate to ensure return routes are present
D.Restart the FortiGate
E.Disable the SSL VPN portal
AnswersA, C

In FortiOS, SSL VPN traffic is de-encapsulated onto the ssl.root virtual interface, and a firewall policy must explicitly permit traffic from that interface to the internal network with the correct source address (derived from the tunnel IP pool), destination, and service. Without such a policy, even if the tunnel is established and authentication succeeds, packets will be silently dropped by the FortiGate's security engine. Therefore, verifying the existence and correctness of that policy is the first logical step in troubleshooting connectivity.

Why this answer

After successful SSL VPN authentication, traffic from the remote user must be permitted by a firewall policy that allows traffic from the SSL VPN interface (e.g., ssl.root) to the destination internal network interface. Without this policy, packets are dropped even if authentication succeeds. Option C is correct because the FortiGate must have a route back to the SSL VPN client IP pool (or the client's virtual IP) in its routing table; if the return route is missing, the FortiGate cannot forward reply traffic to the remote user, causing asymmetric routing and connectivity failure.

Exam trap

The trap here is that candidates often assume authentication success guarantees full connectivity, overlooking the mandatory firewall policy and routing requirements that are separate from the authentication process.

85
MCQmedium

An administrator is troubleshooting an IPsec VPN that uses aggressive mode. The VPN establishes successfully, but the administrator is concerned about security. Which statement is true regarding aggressive mode?

A.Aggressive mode is more secure than main mode
B.Aggressive mode transmits the identification in clear text
C.Aggressive mode provides perfect forward secrecy (PFS) by default
D.Aggressive mode uses six messages instead of three
AnswerB

In aggressive mode, the initiator sends its identification (IDi) along with the Diffie-Hellman values in the first packet, and the responder returns its identification (IDr) in the second packet. Because the shared secret is not yet computed when these packets are exchanged, no encryption keys exist, so the ID payloads are transmitted in plaintext. A passive attacker on the network path can capture these packets and directly read the identities of the VPN peers. This is the primary reason aggressive mode is considered insecure for identity protection.

Why this answer

In aggressive mode, the IKE phase 1 exchange uses three messages instead of six, and the peer's identity (such as the IP address or FQDN) is transmitted in cleartext during the second message before the secure tunnel is established. This exposes the identity to eavesdropping, making it less secure than main mode, which encrypts the identity after the tunnel is set up. The administrator's concern is valid because aggressive mode sacrifices identity protection for faster negotiation.

Exam trap

The trap here is that candidates often confuse aggressive mode's faster negotiation with better security, or mistakenly think the number of messages (three vs. six) implies stronger encryption, when in fact the cleartext identity transmission is the critical security weakness tested on the NSE4 exam.

How to eliminate wrong answers

Option A is wrong because aggressive mode is actually less secure than main mode due to cleartext identity transmission and weaker protection against brute-force attacks. Option C is wrong because perfect forward secrecy (PFS) is not enabled by default in aggressive mode; PFS is a separate configuration option in IKE phase 2 (IPsec SA) and must be explicitly enabled. Option D is wrong because aggressive mode uses three messages (two exchanges) instead of six; main mode uses six messages (three exchanges).

86
MCQmedium

An administrator configures a route-based IPsec VPN between two FortiGates. The Phase 1 and Phase 2 are up. The administrator adds a static route on each FortiGate pointing to the remote subnet via the virtual tunnel interface (e.g., 'to_remote'). Traffic between the subnets fails. What is the MOST likely missing configuration?

A.NAT must be disabled on the tunnel interface
B.The tunnel interface must be added to a zone
C.The Phase 2 proposal must include the correct local and remote subnets
D.A firewall policy is required to permit traffic between the interfaces
AnswerD

FortiGate processes traffic through firewall policies, not merely routing. Although the static route directs packets to the tunnel interface, no policy permits the subnet-to-subnet flow, so traffic is dropped. Adding a policy allowing the local and remote subnets across the tunnel interfaces satisfies this requirement.

Why this answer

In a route-based IPsec VPN, even when Phase 1 and Phase 2 are up and a static route exists via the virtual tunnel interface, traffic will still be dropped unless a firewall policy explicitly permits it. FortiGate uses a stateful firewall, so a policy must allow traffic from the local interface to the tunnel interface (or vice versa) to forward packets. Without this policy, the FortiGate will not forward traffic between the subnets, even though the tunnel is established.

Exam trap

The trap here is that candidates assume a static route and an established IPsec tunnel are sufficient for traffic flow, overlooking the mandatory firewall policy that FortiGate requires to permit inter-subnet traffic in a route-based VPN.

How to eliminate wrong answers

Option A is wrong because NAT is not required to be disabled on the tunnel interface for route-based VPNs; NAT is typically disabled automatically for IPsec traffic, and disabling it manually is not the missing configuration. Option B is wrong because adding the tunnel interface to a zone is optional and used for grouping interfaces for policy application, but it is not a prerequisite for traffic flow; a firewall policy can be applied directly to the interface without a zone. Option C is wrong because the Phase 2 proposal includes the correct local and remote subnets (0.0.0.0/0 for route-based VPNs), and the question states Phase 2 is up, indicating the proposal is correctly configured; the issue is not with Phase 2 parameters.

87
MCQmedium

A FortiGate is configured with FSSO (Fortinet Single Sign-On) to authenticate users from Active Directory. Users are logging in to their domain-joined computers, but the FortiGate does not see the user sessions. The polling connector is configured correctly. What is the MOST likely reason?

A.The FSSO agent is not installed on the Domain Controller
B.The user group filter is too restrictive
C.The FortiGate is not in the same subnet as the users
D.DNS resolution for the Domain Controller is failing
AnswerD

DNS resolution for the Domain Controller is failing. In FSSO polling mode, the FortiGate or collector agent must resolve the Domain Controller's fully qualified domain name to an IP address so it can query the DC's security event logs for user logon events. If DNS resolution fails, the polling connection cannot be established, the FortiGate receives no logon information, and thus no FSSO user sessions are generated in the firewall's session table or user list.

Why this answer

The polling connector relies on the FortiGate communicating with the Domain Controller (DC) to retrieve user logon events. If DNS resolution for the DC fails, the FortiGate cannot resolve the DC's hostname to an IP address, preventing the polling connector from establishing the necessary LDAP or NetAPI connections to collect user session data. This is the most likely cause because the polling connector is configured correctly, but network-level name resolution is a prerequisite for any communication.

Exam trap

The trap here is that candidates often assume FSSO requires an agent on the DC (Option A) or that subnet adjacency is mandatory (Option C), overlooking the fundamental dependency on DNS resolution for the polling connector to function.

How to eliminate wrong answers

Option A is wrong because the FSSO agent does not need to be installed on the Domain Controller when using the polling connector; the polling connector collects logon events directly from the DC's security event log without requiring an agent. Option B is wrong because a restrictive user group filter would only limit which users are recognized after successful polling, not prevent the FortiGate from seeing user sessions entirely. Option C is wrong because the FortiGate does not need to be in the same subnet as the users; FSSO polling works across routed networks as long as the FortiGate can reach the DC via IP and DNS.

88
Multi-Selectmedium

An administrator is troubleshooting an SSL VPN connection. Users can connect but cannot access internal resources. Which TWO commands would help diagnose the issue?

Select 2 answers
A.get router info routing-table
B.diagnose vpn ssl list
C.diagnose vpn ike status
D.execute ping 8.8.8.8
E.diagnose debug application dnsproxy
AnswersA, B

This command displays the kernel routing table, including the route dynamically inserted for the SSL VPN tunnel interface. By checking it, an administrator can verify that the expected destination routes (or the default route) are present and bound to the SSL-VPN interface, which is essential for diagnosing why client traffic may not be forwarded after a successful SSL VPN handshake.

Why this answer

The 'get router info routing-table' command displays the FortiGate's routing table, which is essential for verifying that the FortiGate has a route to the internal resources the SSL VPN users are trying to access. If the route is missing or incorrect, traffic from the SSL VPN tunnel will not be forwarded to the internal network. Option B is correct because 'diagnose vpn ssl list' shows active SSL VPN sessions, including the assigned virtual IP (VIP) and tunnel interface, which helps confirm that the user is properly connected and has received an IP address from the correct address pool.

Exam trap

The trap here is that candidates often confuse IPsec and SSL VPN troubleshooting commands, selecting 'diagnose vpn ike status' because they associate 'vpn' with IPsec, not realizing SSL VPN uses a completely different set of diagnostic tools.

89
Multi-Selectmedium

A FortiGate administrator is configuring a dial-up IPsec VPN for remote users. The users will connect from various locations with dynamic public IP addresses. The administrator wants to ensure that the VPN is secure and that only authorized users can connect. Which two Phase 1 configuration settings are required to support this scenario? (Choose two.)

Select 2 answers
A.Set the 'Remote Gateway' to 'Dialup User'.
B.Set the 'Remote Gateway' to the specific IP address of each user.
C.Enable 'XAUTH' for extended authentication.
D.Configure 'Aggressive' mode for Phase 1.
E.Enable 'NAT Traversal' in Phase 1 settings.
AnswersA, C

Setting the remote gateway to 'Dialup User' allows the FortiGate to accept connections from any IP address, which is necessary for users with dynamic public IPs. This mode is designed for dial-up VPNs where the remote peer's IP is not known in advance. Without this, the FortiGate would only accept connections from a specific IP.

Why this answer

For a dial-up IPsec VPN with dynamic user IPs, the remote gateway must be set to 'Dialup User' to accept connections from any IP. To authenticate individual users, XAUTH must be enabled, which prompts for username and password after the tunnel is established. These two settings ensure that the VPN can handle dynamic IPs and enforce user authentication.

Other settings like Aggressive mode or NAT Traversal may be used but are not required for all scenarios.

Exam trap

The trap here is assuming that Aggressive mode or NAT Traversal are mandatory for dial-up VPNs, when the essential requirements are Dialup User and XAUTH for dynamic IPs and user authentication.

90
Multi-Selecthard

A FortiGate administrator is configuring ZTNA for a web application. Which TWO components are required for a ZTNA configuration to function?

Select 2 answers
C.ZTNA rules
D.ZTNA tags
E.Firewall policy
AnswersC, D

ZTNA rules are the central policy object in FortiOS that define which users and devices—identified by ZTNA tags—may access a specific protected application, and what action to take. When a client makes an HTTPS request through the ZTNA access proxy, the proxy evaluates matching ZTNA rules to allow or deny the session, making this the correct answer. These rules replace traditional firewall policies for application-level access control, not SSL VPN or IPsec.

Why this answer

ZTNA rules are the core policy mechanism that defines access control for ZTNA applications, specifying which users and devices can access which resources based on identity and device posture. Without ZTNA rules, the FortiGate cannot enforce the granular, identity-based access decisions that ZTNA requires.

Exam trap

The trap here is that candidates often confuse ZTNA with traditional VPN technologies (SSL VPN or IPsec VPN) or assume a standard firewall policy is mandatory, when in fact ZTNA operates as a separate, identity-centric access control layer that requires ZTNA rules and tags as its fundamental building blocks.

91
MCQmedium

An admin needs to configure an SSL VPN for remote users that only provides access to specific internal applications, not full network access. What feature should be configured?

A.Full tunneling
B.Client certificate authentication
C.Split tunneling
D.Web mode portal
AnswerC

Split tunneling is correct because it enables the administrator to define specific destination subnets that are routed through the SSL VPN tunnel, while all other traffic goes directly to the client's local network or Internet. This allows remote users to reach only the intended internal applications without exposing the entire corporate network. Split tunneling is configured via destination-based routing on the FortiGate, making it the precise access-control method for this scenario.

Why this answer

Split tunneling (Option C) is the correct feature because it allows the SSL VPN to route only traffic destined for specific internal applications through the encrypted tunnel, while all other traffic goes directly to the internet. This meets the requirement of providing access to specific internal applications without granting full network access, as split tunneling uses routing policies to selectively forward traffic based on destination IP addresses or application ports.

Exam trap

The trap here is that candidates often confuse 'web mode portal' (Option D) with application-specific access, but web mode only provides a browser-based gateway and does not inherently restrict network-layer access without additional split tunneling or firewall policies.

How to eliminate wrong answers

Option A is wrong because full tunneling routes all client traffic through the VPN tunnel, including internet-bound traffic, which would provide full network access and is the opposite of the requirement to limit access to specific internal applications. Option B is wrong because client certificate authentication is an authentication method that verifies the user's identity, not a mechanism to control which applications or network resources are accessible after authentication. Option D is wrong because a web mode portal provides a browser-based interface for accessing specific web applications, but it does not inherently restrict network-level access; it still requires split tunneling or other routing controls to prevent full network access.

92
MCQhard

You run 'diagnose debug application ike -1' and see the following output: 'Initiator: no acceptable proposal'. What is the MOST likely cause of this error?

A.The pre-shared key is incorrect
B.The Phase 1 encryption or hash algorithm is mismatched
C.The remote gateway is not reachable
D.The firewall policy is blocking UDP port 500
AnswerB

A mismatched Phase 1 encryption or hash algorithm directly causes the exact error seen in the ike debug. When the initiator sends a proposal list and the responder cannot find an identical SA transform (same encryption, hash, DH group, lifetime), the responder returns a NO_PROPOSAL_CHOSEN notify and the debug prints something like "no acceptable proposal" or "proposal mismatched". Correcting the FortiGate's Phase 1 algorithm set to match the peer resolves this.

Why this answer

The error 'no acceptable proposal' indicates that the IKE Phase 1 negotiation failed because the two VPN peers could not agree on a common set of security parameters. This is most commonly caused by a mismatch in the encryption algorithm (e.g., AES128 vs AES256) or the hash algorithm (e.g., SHA1 vs SHA256) configured on the FortiGate versus the remote peer. The pre-shared key is not checked until after Phase 1 completes, so it would not cause this specific error.

Exam trap

The trap here is that candidates often confuse Phase 1 proposal mismatches with pre-shared key errors, but the PSK is only checked after the proposal is accepted, so the 'no acceptable proposal' error points exclusively to encryption/hash/DH group mismatches.

How to eliminate wrong answers

Option A is wrong because the pre-shared key is verified during Phase 1 authentication, after the proposal is accepted; an incorrect PSK would result in a different error such as 'no suitable proposal found' or authentication failure. Option C is wrong because if the remote gateway were unreachable, the debug output would show 'no response' or 'timeout', not 'no acceptable proposal'. Option D is wrong because if UDP port 500 were blocked, the IKE packets would never reach the peer, resulting in a timeout or 'no response' error, not a proposal mismatch.

93
MCQmedium

A FortiGate is configured with FSSO for firewall authentication. Users report they are prompted for credentials every time they access the internet, even though they are logged into the domain. What is the most likely cause?

A.The users are not members of the FSSO group.
B.The firewall policy uses 'All Users' instead of a specific group.
C.The FSSO collector agent service is not running.
D.The FortiGate's LDAP server is unreachable.
AnswerC

The FSSO collector agent is the critical component that gathers logon events from Active Directory (either through NetAPI polling or by reading Windows security event logs) and forwards them to the FortiGate. If the collector agent service is stopped or not running, the FortiGate has no source of domain user logon information, so it treats all traffic as unauthenticated and triggers local firewall authentication prompts. This is the most direct cause of the symptom described, because the entire FSSO identity pipeline is broken.

Why this answer

If the FSSO collector agent service is not running, the FortiGate cannot receive the logon events from the domain controllers. Without these events, the FortiGate has no way to know which users are authenticated, so it falls back to prompting for credentials on every new session, even though users are already logged into the domain.

Exam trap

The trap here is that candidates often confuse FSSO with LDAP authentication, assuming an LDAP connectivity issue is the cause, when in fact FSSO relies on a separate collector agent and domain controller event polling, not direct LDAP queries.

How to eliminate wrong answers

Option A is wrong because users not being members of the FSSO group would cause them to be denied access or not matched to the policy, not repeatedly prompted for credentials. Option B is wrong because using 'All Users' in the firewall policy would actually bypass FSSO authentication entirely, allowing traffic without any credential prompt. Option D is wrong because the FortiGate's LDAP server being unreachable affects LDAP-based authentication or directory lookups, not the FSSO polling mechanism which relies on the collector agent and domain controller events, not direct LDAP queries.

94
MCQeasy

An administrator wants to use Active Directory credentials to authenticate firewall administrators. Which authentication server type should be configured on the FortiGate?

B.FSSO
C.LDAP
AnswerC

LDAP is the directory protocol Microsoft Entra ID and Active Directory expose for credential queries. Configuring an LDAP server on the FortiGate lets administrator logins be validated against Active Directory, satisfying the requirement to reuse those credentials.

Why this answer

LDAP (Lightweight Directory Access Protocol) is the correct choice because it directly integrates with Microsoft Active Directory to authenticate firewall administrators using their existing AD credentials. FortiGate can bind to an LDAP server to verify username and password pairs, making it the native protocol for AD authentication without requiring additional services or translation layers.

Exam trap

The trap here is that candidates often confuse FSSO (used for transparent network authentication) with direct admin authentication, or assume RADIUS is the only way to integrate with AD, but FortiGate's native LDAP support is the simplest and most direct method for admin authentication against Active Directory.

How to eliminate wrong answers

Option A is wrong because TACACS+ is a Cisco-proprietary protocol that separates authentication, authorization, and accounting (AAA) and is not natively used by Active Directory; it requires a separate TACACS+ server to bridge to AD. Option B is wrong because FSSO (Fortinet Single Sign-On) is designed for transparent user identification on the network, not for authenticating firewall administrators; it polls AD for login events but does not perform direct password validation. Option D is wrong because RADIUS is a generic AAA protocol that can authenticate against AD only if a RADIUS server (like NPS) is configured as an intermediary; it is not a direct AD authentication method and adds unnecessary complexity for admin authentication.

95
MCQhard

You run the command 'diagnose vpn ike log filter name vpn1' and then 'diagnose vpn ike log filter type phase1'. The log shows: 'IKEv1 exchange:f4470f07:00000000: responder: main mode: received IKE_SA_INIT (aggressive mode not allowed)'. What is the problem?

A.The initiator is using IKEv2 while the responder uses IKEv1
B.The responder is configured for main mode only, but the initiator is sending aggressive mode
C.The pre-shared key is wrong
D.The phase1 proposal is incompatible
AnswerB

In IKEv1, an aggressive-mode initiator sends its SA proposal, key-exchange material, nonce, and identity in a single packet, while a main-mode-only responder expects the two-round-trip Main Mode sequence (SA exchange first, then KE/nonce). When the responder's phase 1 configuration is set to 'main mode only,' it immediately discards the incoming aggressive-mode packet and logs a mode mismatch such as 'aggressive mode is not supported.' This rejection occurs before any proposal comparison or PSK authentication, so the log indicates a configuration mismatch rather than a cryptographic or proposal failure.

Why this answer

The log message 'aggressive mode not allowed' indicates the responder (FortiGate) is configured to accept only main mode IKE phase1 negotiations, but the initiator sent an aggressive mode request. This mismatch causes the responder to reject the IKE_SA_INIT message, as aggressive mode is disabled by default or explicitly set to main mode only in the phase1 configuration.

Exam trap

The trap here is that candidates may confuse the 'aggressive mode not allowed' message with a proposal mismatch or authentication failure, but the log explicitly states the mode is the issue, not the cryptographic parameters or keys.

How to eliminate wrong answers

Option A is wrong because the log explicitly shows 'IKEv1 exchange', so both sides are using IKEv1, not IKEv2. Option C is wrong because a pre-shared key mismatch would cause a different error, such as 'invalid payload' or 'authentication failed', not a mode rejection message. Option D is wrong because an incompatible phase1 proposal would generate a 'no acceptable proposal' or 'proposal mismatch' error, not a message about aggressive mode not being allowed.

96
Multi-Selectmedium

A FortiGate administrator is configuring FSSO to authenticate users transparently. The FSSO collector agent is installed on a Windows server in the domain. Which TWO requirements must be met for FSSO to work correctly?

Select 2 answers
A.The FortiGate must be a member of the Active Directory domain
B.The users must authenticate via captive portal at least once
C.The FortiGate must be able to reach the FSSO collector agent on TCP port 8000 (or the configured port)
D.The firewall policies must use FSSO groups directly without any user objects
E.The FSSO collector agent must have network access to the Active Directory domain controllers
AnswersC, E

The FortiGate must be able to reach the FSSO collector agent on TCP port 8000 (or the port specified under FSSO settings). This is the connection over which the collector agent sends login and logout events; if the port is firewalled, the FortiGate will not receive authentication updates and FSSO policies will fail to match. The default port is 8000, but it must match exactly on both the agent and the FortiGate.

Why this answer

The FortiGate must communicate with the FSSO collector agent over TCP port 8000 (or a custom port) to receive real-time user login/logoff events. This connection is essential for the FortiGate to map IP addresses to authenticated domain users and enforce identity-based firewall policies. Without this reachability, the FortiGate cannot obtain the necessary user-to-IP mappings from the collector agent.

Exam trap

The trap here is that candidates assume the FortiGate must join the Active Directory domain (Option A), but FSSO only requires network connectivity to the collector agent, not domain membership.

97
MCQhard

A FortiGate is configured with IPsec VPN using IKEv2 and a policy-based tunnel. The remote subnet is 10.0.2.0/24, and the local subnet is 192.168.1.0/24. The tunnel is up, but traffic from 192.168.1.0/24 to 10.0.2.0/24 fails. The administrator checks the firewall policy and sees a policy allowing traffic from the local interface (port1) to the remote interface (virtual ipsec interface) with the action set to IPSEC. What is the most likely missing configuration?

A.IKEv2 does not support policy-based VPNs
B.The tunnel interface is not assigned to the correct VDOM
C.The Phase 2 proposal does not match the remote subnet
D.The firewall policy's source or destination addresses are not correctly set to the local and remote subnets
AnswerD

In a policy-based IPsec VPN, the firewall policy itself defines the local and remote subnets through its source and destination address objects, effectively acting as the Phase 2 proxy-IDs. If those address objects do not exactly match the subnets to be protected, the tunnel remains up but traffic is not matched by the policy, so the FortiGate drops or fails to forward it. Additionally, using only 'all' as the destination may send a proxy-ID of 0.0.0.0/0, which many remote peers reject, causing a negotiation mismatch even though the policy itself is permissive.

Why this answer

In a policy-based IPsec VPN on FortiGate, the firewall policy must explicitly specify the local and remote subnets as the source and destination addresses. Even if the tunnel is up, traffic will fail if the policy's source/destination address objects do not match the actual subnets (192.168.1.0/24 and 10.0.2.0/24). The action set to IPSEC only enables VPN encapsulation; it does not override incorrect address matching.

Exam trap

The trap here is that candidates assume a tunnel being up means all traffic will pass, but FortiGate policy-based VPNs require the firewall policy's address objects to precisely match the protected subnets, not just the tunnel interface.

How to eliminate wrong answers

Option A is wrong because IKEv2 fully supports policy-based VPNs on FortiGate; the issue is not protocol version compatibility. Option B is wrong because VDOM assignment affects interface visibility, but the tunnel is up and the policy references the virtual IPsec interface, indicating correct VDOM placement. Option C is wrong because a Phase 2 proposal mismatch would prevent the tunnel from establishing or cause it to fail during negotiation, but the tunnel is already up, so the Phase 2 selectors must match the remote subnet.

98
Multi-Selectmedium

A site-to-site IPsec VPN is configured with IKEv2. The tunnel establishes but traffic does not pass. Which two troubleshooting steps should the administrator perform first?

Select 2 answers
A.Check the Phase 2 selectors.
B.Verify that the Phase 1 proposal matches.
C.Check the firewall policies allowing traffic through the tunnel.
D.Check the routing table for routes pointing to the remote networks.
AnswersC, D

In Fortinet's policy-based VPN model, firewall policies are the gatekeepers that decide which traffic is allowed to traverse the tunnel interface. Even with Phase 1 and Phase 2 both up, packets are dropped unless there is an explicit policy permitting traffic between the local and remote zones (e.g., from 'internal' to 'tunnel'). This is a frequent point of failure because the tunnel status itself is independent of the policy configuration.

Why this answer

Even if the IPsec tunnel is established, traffic will not pass unless firewall policies explicitly permit it. In FortiGate, a Phase 2 tunnel being up does not imply that traffic is allowed; you must have a policy that matches the source/destination and enables the action to forward traffic through the tunnel interface.

Exam trap

The trap here is that candidates assume a 'tunnel up' status guarantees traffic flow, but FortiGate separates tunnel negotiation from firewall policy enforcement, so both a policy and a route are required for traffic to pass.

99
MCQhard

A FortiGate administrator runs 'diagnose vpn tunnel list' and sees the following output for an IPsec tunnel: 'status: up', 'incoming: 0 packets', 'outgoing: 100 packets'. Phase 1 and Phase 2 both show state 'up'. What is the MOST likely cause of zero incoming packets?

A.The remote gateway is using aggressive mode
B.The FortiGate has a static route pointing to the VPN interface
C.The VPN is configured in policy-based mode
D.The Phase 2 proposal includes a mismatched proxy ID
AnswerD

During Phase 2 negotiation, both peers exchange proxy IDs (traffic selectors) that define which source and destination subnets are encrypted. If the local proxy ID does not exactly match the remote peer's expected subnets, the IPsec SA is established with mismatched selectors. The remote gateway may then drop incoming packets that fall outside its configured selectors, or it may not respond at all, causing the tunnel to appear up but traffic to fail in one or both directions.

Why this answer

The output shows the VPN tunnel is up with outgoing packets but zero incoming packets. This indicates a Phase 2 mismatch, most commonly due to mismatched proxy IDs (local/remote subnets). When proxy IDs do not match between peers, the tunnel establishes but traffic is not correctly matched, causing the remote gateway to drop or not send traffic to the FortiGate, resulting in zero incoming packets.

Exam trap

The trap here is that candidates see 'status: up' and assume the tunnel is fully functional, overlooking that Phase 2 proxy ID mismatches can leave the tunnel up but unable to pass traffic in one direction.

How to eliminate wrong answers

Option A is wrong because aggressive mode affects Phase 1 authentication (using fewer exchanges and sending the ID in plaintext) but does not cause zero incoming packets once the tunnel is up; it would prevent Phase 1 from completing if mismatched. Option B is wrong because a static route pointing to the VPN interface is necessary for routing traffic into the tunnel; its presence would not cause zero incoming packets—it would actually help traffic flow. Option C is wrong because policy-based mode (vs. route-based) does not inherently cause zero incoming packets; both modes can work correctly if proxy IDs match.

The issue is specifically a Phase 2 proxy ID mismatch, which prevents the remote peer from associating incoming traffic with the correct SA.

100
MCQeasy

A FortiGate administrator wants to authenticate VPN users against an existing LDAP server. The administrator creates an LDAP user group on the FortiGate. What additional configuration is REQUIRED to use this group for IPsec VPN authentication?

A.In the IPsec Phase 1 configuration, set the peer type to 'dialup' and specify the user group under authentication
B.Enable LDAP over TLS (LDAPS) on the FortiGate
C.Assign the LDAP user group to a firewall policy
D.Configure a RADIUS server as an intermediate proxy between FortiGate and LDAP
AnswerA

Dialup peer type makes the FortiGate accept multiple dynamic peers rather than one fixed remote gateway, and the authentication setting binds the LDAP user group to Phase 1. Without both, the group cannot authenticate VPN users, so this satisfies the requirement to use the LDAP group for IPsec authentication.

Why this answer

For IPsec VPN authentication, the FortiGate must know which users are allowed to connect. Setting the peer type to 'dialup' in Phase 1 enables the FortiGate to accept connections from remote users rather than another gateway. Specifying the LDAP user group under authentication tells the FortiGate to validate the VPN user's credentials against that group's members, which are resolved via the LDAP server.

Without this configuration, the FortiGate has no way to associate the LDAP group with the VPN tunnel.

Exam trap

The trap here is that candidates often confuse the authentication configuration (Phase 1) with the authorization configuration (firewall policies), leading them to select Option C, thinking that assigning the group to a policy is sufficient for VPN authentication.

How to eliminate wrong answers

Option B is wrong because LDAPS (LDAP over TLS) is a transport security measure for the LDAP connection, but it is not required for IPsec VPN authentication; the FortiGate can authenticate using plain LDAP or LDAPS, and the question asks for what is required. Option C is wrong because firewall policies control traffic flow after authentication, not the authentication process itself; assigning the LDAP user group to a firewall policy is needed for authorization and access control, but it does not enable the VPN to authenticate users. Option D is wrong because a RADIUS server is not required; the FortiGate can directly query the LDAP server for authentication without an intermediate proxy, and using RADIUS would be an additional, optional configuration.

101
MCQeasy

Which of the following is a characteristic of route-based IPsec VPN compared to policy-based IPsec VPN?

A.Route-based VPN is only supported in IKEv1
B.Route-based VPN requires Phase 2 selectors to match both local and remote subnets
C.Route-based VPN can use dynamic routing protocols like OSPF
D.Route-based VPN uses firewall policies with IPsec action
AnswerC

Because route-based VPNs present the IPsec tunnel as a virtual interface, that interface can participate in dynamic routing protocols such as OSPF, BGP, or RIP. This allows the VPN to exchange routing information automatically, so remote subnets are learned dynamically rather than requiring static routes for each destination. This is a major operational advantage over policy-based VPNs, which cannot run routing protocols across the tunnel in a straightforward manner.

Why this answer

Route-based IPsec VPNs create a virtual tunnel interface (e.g., ipsec0 or tunnel) that acts as a logical routing point, allowing dynamic routing protocols such as OSPF to exchange routes over the encrypted tunnel. This is a key advantage over policy-based VPNs, which rely on static security policies and cannot support dynamic routing.

Exam trap

The trap here is that candidates often confuse route-based VPNs with policy-based VPNs, assuming both require Phase 2 selectors to match subnets, but route-based VPNs use a tunnel interface with any-to-any selectors and rely on routing instead.

How to eliminate wrong answers

Option A is wrong because route-based VPNs are supported in both IKEv1 and IKEv2; IKEv2 is actually more common for route-based deployments. Option B is wrong because route-based VPNs do not require Phase 2 selectors to match subnets; the tunnel interface handles all traffic, and selectors are typically set to 0.0.0.0/0 to allow any traffic. Option D is wrong because route-based VPNs use the tunnel interface directly, not firewall policies with an IPsec action; policy-based VPNs are the ones that require firewall policies with an IPsec action to trigger encryption.

102
MCQeasy

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?

A.Two-factor authentication with FortiToken
B.RADIUS authentication
C.PKI authentication
D.LDAP authentication
AnswerA

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.

Why this answer

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.

Exam trap

The trap here is that candidates often 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.

How to eliminate wrong answers

Option B (RADIUS authentication) is wrong because RADIUS is an external authentication protocol that can be used for 2FA, but it does not directly enable FortiToken support; FortiToken is a Fortinet-specific token that requires the built-in two-factor method. Option C (PKI authentication) is wrong because PKI uses digital certificates for authentication, not token-based OTPs, and is typically used for client certificate authentication rather than two-factor with FortiToken. Option D (LDAP authentication) is wrong because LDAP is a directory service protocol for retrieving user credentials, but it does not natively support FortiToken OTPs; FortiToken requires the FortiGate's internal two-factor mechanism to validate the token.

103
Drag & Dropmedium

Drag and drop the steps to upgrade FortiGate firmware via the web interface into the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Firmware upgrade requires uploading the image and confirming; the device reboots automatically.

104
MCQeasy

An administrator wants to restrict SSL VPN access to only users who have a valid client certificate issued by the company's internal CA. Which setting should be configured?

A.Configure a firewall policy with identity-based authentication
B.Enable 'certificate-based authentication' in the user group
C.Enable 'require client certificate' in the SSL VPN settings
D.Import the users' public keys into the FortiGate
AnswerC

Setting 'Require Client Certificate' in the SSL VPN settings makes the FortiGate demand a client certificate during the SSL/TLS handshake, and only a certificate signed by a configured trusted CA will be accepted. This ensures that every SSL VPN session is cryptographically tied to a credential that is bound to a specific US user, so users without a valid certificate cannot even initiate the handshake. This is the direct control that physically enforces certificate-based access.

Why this answer

The 'require client certificate' setting in the SSL VPN portal or interface configuration enforces mutual TLS (mTLS), where the FortiGate requests and validates a client certificate against the configured CA. This ensures that only users presenting a valid certificate issued by the company's internal CA can establish the SSL VPN tunnel, regardless of their authentication credentials.

Exam trap

The trap here is that candidates confuse 'certificate-based authentication' with a user group setting, when in fact the enforcement point is the SSL VPN portal or interface configuration, not the user group definition.

How to eliminate wrong answers

Option A is wrong because identity-based firewall policies control access based on user/group authentication (e.g., LDAP or local users), not client certificate validation; they do not enforce certificate-based client identity at the SSL VPN tunnel level. Option B is wrong because 'certificate-based authentication' in a user group is not a valid FortiGate setting; user groups support authentication methods like LDAP, RADIUS, or PKI, but the group itself does not have a toggle for certificate-based authentication—this must be configured in the SSL VPN settings. Option D is wrong because importing users' public keys into the FortiGate is not a standard method for client certificate validation; the FortiGate validates client certificates by trusting the issuing CA's certificate, not by importing individual user public keys.

105
MCQeasy

A FortiGate administrator wants to configure a captive portal to authenticate users before granting network access. Which authentication method is used by the captive portal?

A.Form-based authentication
B.IPsec pre-shared key authentication
C.X.509 certificate authentication
D.NTLM authentication
AnswerA

Form-based authentication is the standard method for a FortiGate captive portal. When a user without an existing authenticated session attempts to access a web resource, the FortiGate redirects the browser to a login page containing an HTML form. The user submits a username and password, which the FortiGate then validates against a configured authentication server (e.g., LDAP, RADIUS, or local user database). Upon successful validation, the FortiGate creates an authentication session and permits the traffic, making this the correct interactive method for captive portal.

Why this answer

FortiGate captive portals use form-based authentication by default, presenting a web page where users enter credentials (username/password) that are verified against a configured authentication server (e.g., LDAP, RADIUS, or local user database). This method is designed for HTTP/HTTPS interception and does not rely on network-layer or certificate-based mechanisms.

Exam trap

The trap here is that candidates may confuse captive portal authentication with other FortiGate authentication methods like NTLM or certificate-based authentication, assuming the portal can use any of them, but the default and primary method is form-based authentication.

How to eliminate wrong answers

Option B is wrong because IPsec pre-shared key authentication is used for VPN tunnel establishment, not for web-based captive portal user login. Option C is wrong because X.509 certificate authentication is typically used for client certificate validation in SSL VPN or 802.1X, not for the form-based login page of a captive portal. Option D is wrong because NTLM authentication is a Windows-specific challenge-response protocol used for integrated Windows authentication (e.g., in Active Directory environments), not the default or primary method for FortiGate captive portals.

106
MCQeasy

Which of the following FortiGate features allows users to authenticate using a one-time password generated by a mobile app?

A.FSSO
B.LDAP
C.FortiToken
D.Captive portal
AnswerC

FortiToken generates time-based one-time passwords (TOTP) in a mobile app, satisfying the stem's requirement for app-generated OTP authentication on FortiGate. Unlike SMS or email tokens, FortiToken Mobile runs locally on the device, producing rolling codes that FortiGate validates against its shared secret during firewall or SSL VPN login.

Why this answer

FortiToken is Fortinet's two-factor authentication solution that generates one-time passwords (OTPs) via a mobile app (FortiToken Mobile) or hardware token. When a user authenticates, they must provide both their regular password and the current OTP from the FortiToken app, which is validated by the FortiGate against the token's seed record. This directly matches the question's requirement for OTP generation by a mobile app.

Exam trap

The trap here is that candidates often confuse FortiToken with FSSO or LDAP because all three involve authentication, but only FortiToken specifically generates and validates one-time passwords via a mobile app.

How to eliminate wrong answers

Option A (FSSO) is wrong because FSSO (Fortinet Single Sign-On) collects user login events from domain controllers to map users to IP addresses for policy enforcement, but it does not generate or validate one-time passwords. Option B (LDAP) is wrong because LDAP is a directory service protocol used for storing and retrieving user credentials and attributes; it does not generate OTPs or provide two-factor authentication. Option D (Captive portal) is wrong because a captive portal is a web-based authentication interface that redirects users to a login page, but it does not generate OTPs; it can be used with external authentication methods but is not itself an OTP generator.

107
Multi-Selectmedium

A FortiGate administrator is configuring RADIUS authentication for firewall users. Which THREE steps are required to complete the configuration? (Select THREE.)

Select 3 answers
A.Import the RADIUS server certificate into FortiGate
B.Configure a firewall policy with the user group set in 'users/groups'
C.Define the RADIUS server under 'config user radius'
D.Create a user group that uses the RADIUS server as the authentication source
E.Enable 'set auth-type radius' on the interface
AnswersB, C, D

This is the enforcement point of RADIUS-based user authentication. In a firewall policy you set the source to a specific user or user group in the 'users/groups' field, which instructs FortiGate to authenticate any matching traffic against that group's authentication source. Without this policy, the RADIUS server and group are configured but no traffic is ever challenged for credentials, so the authentication is never actually applied.

Why this answer

A firewall policy must reference the user group that uses the RADIUS server as its authentication source. Without this policy configuration, RADIUS-authenticated users cannot match the policy and will be denied access. The 'users/groups' field in the firewall policy is where the user group object is specified to enforce authentication-based access control.

Exam trap

The trap here is that candidates may think importing a server certificate is required for RADIUS (confusing it with LDAPS or EAP), or that an interface-level authentication type command exists, when in fact RADIUS authentication is configured via the server object and user group, not on the interface.

108
MCQmedium

A network admin configures a site-to-site IPsec VPN between two FortiGates using IKEv1 main mode. The tunnel establishes successfully, but no traffic passes. What is the MOST likely cause?

A.Aggressive mode should be used instead of main mode
B.The pre-shared key is incorrect
C.There is no firewall policy allowing traffic through the VPN tunnel
D.The phase2 proposal does not match between peers
AnswerC

Even when the IPsec tunnel interface is up and phase 1/phase 2 SAs are active, FortiGate will not forward any user traffic through the tunnel unless an explicit firewall policy permits it. The policy must be configured with the source address, destination address, and service, and its outgoing interface must be set to the VPN tunnel interface (or the virtual IPsec interface). Without such a policy, packets are dropped at the firewall policy check even though the encrypted tunnel exists and is healthy. This is the classic root cause when the VPN shows connected but users cannot reach remote resources, and the fix is to create the appropriate ACCEPT policy from the local zone to the VPN zone.

Why this answer

The tunnel establishes successfully, meaning IKE phase 1 and phase 2 negotiations completed correctly, which rules out mismatched proposals or incorrect pre-shared keys. However, even with a functional IPsec tunnel, traffic cannot flow unless a firewall policy explicitly permits it between the source and destination zones using the VPN interface. In FortiGate, the VPN tunnel is treated as an interface, and without a policy allowing traffic from the internal network to the VPN interface (or vice versa), packets are dropped by the firewall engine.

Exam trap

The trap here is that candidates assume a successful IPsec tunnel automatically allows traffic, but FortiGate requires an explicit firewall policy to permit traffic through the VPN interface, unlike some other vendors where the tunnel itself implies a permit.

How to eliminate wrong answers

Option A is wrong because aggressive mode is used for faster negotiation with less security (e.g., when peer IP is dynamic), but main mode is fully valid and not the cause of traffic failure after tunnel establishment. Option B is wrong because if the pre-shared key were incorrect, IKE phase 1 authentication would fail and the tunnel would never establish. Option D is wrong because a phase 2 proposal mismatch would cause the IPsec SA negotiation to fail, preventing the tunnel from establishing; since the tunnel is up, the proposals must match.

109
MCQeasy

Which IPsec VPN mode uses IP addresses and ports to define interesting traffic, and requires a separate security policy for each tunnel?

A.Hub-and-spoke VPN
B.Policy-based VPN
C.Dial-up VPN
D.Route-based VPN
AnswerB

Policy-based VPN is the correct IPsec mode because it uses firewall policies to define interesting traffic by matching source/destination IP addresses, protocols, and ports, and then applies action 'IPsec' to encrypt that traffic. In FortiGate, the policy also references the IPsec phase1/phase2 VPN tunnel and security profiles, making the policy the single point of traffic selection. This is exactly how addresses and ports determine which traffic goes over the VPN.

Why this answer

Policy-based VPN (B) is correct because it defines interesting traffic using source/destination IP addresses and ports, and each tunnel requires a separate security policy to specify which traffic should be encrypted. This contrasts with route-based VPNs, which use virtual interfaces and routing tables to determine traffic, allowing a single policy to handle multiple tunnels.

Exam trap

The trap here is that candidates often confuse 'policy-based VPN' with 'route-based VPN', mistakenly thinking that route-based VPNs require separate security policies per tunnel, when in fact route-based VPNs use a single policy tied to the IPsec interface and leverage routing to handle multiple destinations.

How to eliminate wrong answers

Option A is wrong because hub-and-spoke VPN is a topology, not a mode that uses IP addresses and ports to define interesting traffic; it can be implemented with either policy-based or route-based VPNs. Option C is wrong because dial-up VPN is a scenario where remote clients connect to a central gateway, and it typically uses policy-based or route-based modes, but the defining characteristic is dynamic IP assignment, not the use of IP/port-based interesting traffic definitions. Option D is wrong because route-based VPN uses virtual interfaces (e.g., IPsec interfaces) and routing tables to direct traffic into tunnels, not IP addresses and ports in security policies; it does not require a separate security policy per tunnel.

110
MCQeasy

Which of the following is a benefit of using IKEv2 over IKEv1 for IPsec VPN?

A.IKEv2 supports only main mode
B.IKEv2 requires fewer firewall rules
C.IKEv2 uses a single UDP port 500
D.IKEv2 is more robust to network changes and supports MOBIKE
AnswerD

IKEv2 is indeed more robust in mobile and changing network environments, primarily due to MOBIKE (Mobility and Multihoming). MOBIKE allows the VPN peer to update its current IP address to the remote gateway without renegotiating the entire IKE and IPsec SAs, preserving the tunnel across Wi-Fi to cellular handoffs. This feature, specified in RFC 4555 and integrated into RFC 7296, is absent from IKEv1, making IKEv2 superior for dynamic links.

Why this answer

IKEv2 is more robust to network changes because it supports the Mobility and Multihoming (MOBIKE) protocol, which allows an IPsec VPN tunnel to survive IP address changes without re-establishing the entire security association. This is a key advantage over IKEv1, which lacks native support for MOBIKE and requires a full rekey when the endpoint's IP address changes.

Exam trap

The trap here is that candidates often confuse IKEv2's simplified exchange (fewer messages) with requiring fewer firewall rules, but the actual benefit tested is MOBIKE support for network resilience.

How to eliminate wrong answers

Option A is wrong because IKEv2 does not support only main mode; it uses a single exchange (two messages) for initial SA setup, unlike IKEv1 which has main mode and aggressive mode. Option B is wrong because IKEv2 does not inherently require fewer firewall rules; both IKEv1 and IKEv2 typically need UDP ports 500 and 4500 (for NAT traversal) open, so the number of firewall rules is comparable. Option C is wrong because IKEv2 does not use a single UDP port 500; it uses UDP port 500 for initial negotiation and can switch to UDP port 4500 for NAT traversal, similar to IKEv1.

111
MCQhard

An administrator runs 'diagnose vpn ike gateway list' on a FortiGate and sees the following output for a dial-up IPsec VPN: gateway name: 'dialup' version: IKEv1 mode: aggressive local IP: 203.0.113.1 remote IP: 0.0.0.0 state: up peers: 0 What does 'peers: 0' indicate?

A.The remote IP should be set to a specific address
B.The gateway is in a down state
C.No IPsec clients are currently connected
D.The Phase 2 proposals are mismatched
AnswerC

The peers counter shows how many dial-up clients currently have an established IPsec tunnel to this gateway. A value of zero means no clients are connected, even though the gateway itself is up and listening for incoming aggressive-mode connections from remote peers.

Why this answer

In the output of 'diagnose vpn ike gateway list', the 'peers' field shows the number of active IPsec tunnels (Phase 1 SAs) currently established through that gateway. A value of '0' means no remote clients have successfully completed IKE negotiation and are connected. Since the gateway state is 'up', it is ready to accept connections, but no clients are currently associated with it.

Exam trap

The trap here is that candidates see 'state: up' and assume the gateway has active connections, but 'up' only indicates the IKE process is running and listening, not that any peers are actually connected.

How to eliminate wrong answers

Option A is wrong because in a dial-up IPsec VPN, the remote IP is intentionally left as 0.0.0.0 to allow any remote client to initiate a connection; setting a specific address would defeat the purpose of a dial-up configuration. Option B is wrong because the output explicitly shows 'state: up', indicating the IKE gateway process is active and listening, not down. Option D is wrong because Phase 2 proposal mismatches would cause failures during IPsec SA establishment, not affect the Phase 1 peer count; the 'peers' counter specifically tracks Phase 1 SAs, not Phase 2.

112
MCQhard

After upgrading FortiOS, an IPsec VPN tunnel fails to come up. The diagnose output shows 'negotiation failed: no acceptable proposal'. The remote peer is a third-party device. Which step should you take first?

A.Change the IKE version to IKEv2
B.Disable dead peer detection on the FortiGate
C.Reboot the remote peer
D.Check the phase1 and phase2 proposal settings on both ends to ensure they match
AnswerD

The correct first step is to compare the phase1 and phase2 proposal settings on both peers, because after a FortiOS upgrade, default values or accepted algorithms may have changed, causing a mismatch in encryption (e.g., AES128 vs AES256), authentication/hash (e.g., SHA1 vs SHA2), Diffie-Hellman group (e.g., 2 vs 14), or PFS settings. Both IKE security associations (phase1) and IPsec security associations (phase2) require an exact match of all transform sets; if any parameter differs, the tunnel will not come up. Use the "diagnose vpn ike log" or check the FortiGate logs to identify the specific proposal that was rejected, then adjust the FortiGate configuration to match the remote peer's supported algorithms.

Why this answer

The 'no acceptable proposal' error indicates a mismatch in the Internet Key Exchange (IKE) parameters between the FortiGate and the remote peer. Since the remote peer is a third-party device, the most common cause is a misalignment in phase1 (IKE) or phase2 (IPsec) settings such as encryption algorithm, authentication method, Diffie-Hellman group, or lifetime. Option D is correct because verifying and aligning these proposals on both ends is the standard first step to resolve proposal mismatches.

Exam trap

The trap here is that candidates often jump to changing IKE version or disabling DPD, thinking the issue is a protocol incompatibility or a dead peer, when the root cause is almost always a simple proposal mismatch that must be checked first.

How to eliminate wrong answers

Option A is wrong because changing the IKE version (e.g., from IKEv1 to IKEv2) does not fix a proposal mismatch; it only changes the negotiation protocol, and both ends must already support the same version. Option B is wrong because disabling dead peer detection (DPD) does not address proposal negotiation failures; DPD is used to detect peer liveness after the tunnel is established, not during initial IKE negotiation. Option C is wrong because rebooting the remote peer is a disruptive and unnecessary step; it will not correct configuration mismatches and only wastes time when the issue is clearly a proposal mismatch.

113
MCQmedium

An administrator has configured LDAP authentication on a FortiGate. When testing the LDAP connectivity, the test succeeds. However, users cannot authenticate through the captive portal. What is a possible cause?

A.The captive portal is disabled
B.The user group is not configured to use the LDAP server
C.The LDAP server is not reachable from the captive portal interface
D.The LDAP server's SSL certificate is expired
AnswerB

In FortiGate, an LDAP server object alone is not sufficient for authentication; the user group must explicitly reference that LDAP server as its remote authentication source. When a user tries to authenticate via the captive portal, FortiGate checks the user's group membership and looks at the authentication server assigned to that group. If the LDAP server is not configured in the user group settings, FortiGate has no source to bind against, so the LDAP query is never performed. This is the correct root cause because it explains why connectivity to LDAP succeeds but authentication still fails.

Why this answer

The LDAP connectivity test succeeds, confirming the FortiGate can reach and bind to the LDAP server. However, for captive portal authentication to work, the user group must be explicitly configured to reference the LDAP server as its remote authentication source. Without this mapping, the FortiGate does not know to send authentication requests to the LDAP server, even though the LDAP server connection itself is functional.

Exam trap

The trap here is that candidates assume a successful LDAP connectivity test guarantees full authentication functionality, but FortiGate requires an explicit user group binding to use the LDAP server for captive portal authentication.

How to eliminate wrong answers

Option A is wrong because if the captive portal were disabled, users would not even see the captive portal login page, but the question states users cannot authenticate, implying the portal is active. Option C is wrong because the LDAP connectivity test succeeded, proving the LDAP server is reachable from the FortiGate; the captive portal interface uses the same FortiGate to reach the server. Option D is wrong because an expired SSL certificate would cause the LDAP connectivity test to fail (unless LDAP over TLS is not used), and the test succeeded, so certificate expiry is not the issue.

114
MCQhard

You run the following CLI command on a FortiGate: 'diagnose vpn ike config list'. The output includes: 'src 10.0.1.0/24:0 dst 192.168.1.0/24:0'. What does this indicate?

A.The firewall policy is allowing traffic from 10.0.1.0/24 to 192.168.1.0/24
B.The Phase 2 configuration is using 10.0.1.0/24 as local subnet and 192.168.1.0/24 as remote subnet
C.The Phase 1 configuration is using 10.0.1.0/24 as local address
D.The tunnel is in dial-up mode with dynamic remote subnet
AnswerB

This statement correctly interprets the diagnostic output: the phase 2 configuration defines the traffic selectors, specifying which local and remote subnets are allowed to communicate through the VPN. In the output, the local quick mode selector is 10.0.1.0/24 and the remote selector is 192.168.1.0/24, meaning that traffic between these subnets will be encrypted. This is a standard site-to-site VPN setup with explicit proxy IDs.

Why this answer

The 'diagnose vpn ike config list' command displays the Phase 2 configuration for an IPsec VPN tunnel. The output 'src 10.0.1.0/24:0 dst 192.168.1.0/24:0' directly indicates the local and remote subnets defined in the Phase 2 selector, where 'src' is the local subnet and 'dst' is the remote subnet. This confirms that the Phase 2 configuration is using 10.0.1.0/24 as the local subnet and 192.168.1.0/24 as the remote subnet.

Exam trap

The trap here is confusing the 'src' and 'dst' fields in the IKE diagnostic output with firewall policy source/destination, leading candidates to incorrectly select Option A instead of recognizing it as Phase 2 subnet selectors.

How to eliminate wrong answers

Option A is wrong because the 'diagnose vpn ike config list' command shows IKE Phase 2 selectors, not firewall policies; firewall policies are verified with 'diagnose firewall policy list' or 'show firewall policy'. Option C is wrong because Phase 1 configuration uses local and remote IP addresses (not subnets) and is displayed with 'diagnose vpn ike config list' showing 'local' and 'remote' fields, not 'src' and 'dst'. Option D is wrong because the output shows specific subnet masks (/24) for both source and destination, indicating a static, non-dial-up configuration; dial-up mode would show '0.0.0.0/0' for the remote subnet.

115
MCQeasy

An administrator is configuring a FortiGate to use LDAP for firewall authentication. Users are prompted for their credentials when accessing the internet. After successful authentication, users can access the internet. However, the administrator notices that users are prompted again after 30 minutes of inactivity. Which setting should the administrator adjust to extend the authentication timeout?

A.Increase the 'idle-timeout' in the firewall policy.
B.Modify the 'auth-timeout' in the user settings.
C.Adjust the 'session-ttl' in the firewall policy.
D.Change the 'ldap-timeout' in the LDAP server configuration.
AnswerB

The 'auth-timeout' setting under 'config system global' or per-user group controls how long a user's authentication is valid. By default, it is 30 minutes. Increasing this value will extend the time before users are prompted to re-authenticate. This is the correct setting to adjust for extending the authentication period.

Why this answer

The authentication timeout on a FortiGate is controlled by the 'auth-timeout' setting, which can be configured globally or per user group. This setting determines how long a user remains authenticated after providing credentials. The default is 30 minutes.

To extend this period, the administrator should increase the 'auth-timeout' value. Other timeouts, such as idle-timeout or session-ttl, affect session behavior but not the authentication duration.

Exam trap

The trap here is confusing session timeouts with authentication timeouts, but the re-prompting after 30 minutes is specifically governed by the authentication timeout setting.

116
MCQeasy

A FortiGate admin wants to authenticate VPN users against an existing Microsoft Active Directory. Which authentication method should be configured on the FortiGate?

A.LDAP
C.FSSO
AnswerA

LDAP is the standard directory access protocol used by Active Directory for querying and binding user credentials. When a FortiGate authenticates VPN users against an LDAP server, it performs an LDAP bind with the user's username and password to verify the credentials directly against the directory. Optionally, it can also retrieve group memberships to enforce access policies, making LDAP the most native and efficient method for integrating with AD.

Why this answer

(LDAP) is correct because Microsoft Active Directory natively supports LDAP (Lightweight Directory Access Protocol) for authentication and directory lookups. FortiGate can directly bind to AD using LDAP to verify VPN user credentials against the AD database without requiring an additional RADIUS server or agent. This method is efficient for direct user authentication in a Windows domain environment.

Exam trap

The trap here is that candidates often confuse FSSO (which is for transparent network access) with direct authentication, or assume RADIUS is always required for AD integration, when LDAP is the simpler and correct method for direct user authentication in VPN scenarios.

How to eliminate wrong answers

Option B (RADIUS) is wrong because RADIUS is a client-server protocol that requires a separate RADIUS server (e.g., NPS on Windows) to proxy authentication to Active Directory; it adds unnecessary complexity when direct LDAP is available. Option C (FSSO) is wrong because FSSO (Fortinet Single Sign-On) is designed for transparent authentication of users on the network based on domain logon events, not for direct VPN user authentication against AD. Option D (TACACS+) is wrong because TACACS+ is a Cisco-proprietary protocol primarily used for device administration (e.g., router/switch login) and is not designed for VPN user authentication against Active Directory.

117
MCQmedium

A FortiGate administrator is configuring an SSL VPN web mode portal. The administrator wants users to access only a specific internal web application (https://internal-app.company.local) and nothing else. Which SSL VPN setting should be configured to achieve this?

A.In the SSL VPN portal, set the default bookmark to the application URL
B.Configure a firewall policy that allows traffic only to the application's IP address
C.Enable split tunneling under the SSL VPN settings
D.Under the SSL VPN portal, configure 'URL Access' to allow only https://internal-app.company.local
AnswerD

The URL Access feature under the SSL VPN portal provides a per-portal whitelist of web addresses that users are allowed to access through the reverse proxy. When you specify only https://internal-app.company.local, the FortiGate enforces that rule during proxy processing: any request to a URL that does not match the whitelist is denied with an error. This precisely meets the requirement because it is a proxy-level, application-aware access control, rather than a network-layer rule or a UI shortcut. It effectively prevents users from browsing to any other internal or external web host through the portal while allowing the specific internal application.

Why this answer

The 'URL Access' setting in the SSL VPN web mode portal allows the administrator to explicitly define which URLs users can access through the portal. By configuring an allow list with only https://internal-app.company.local, users are restricted to that specific internal web application, and all other URLs are blocked. This provides granular control over web-based resources in the SSL VPN portal without relying on network-layer restrictions.

Exam trap

The trap here is that candidates often confuse network-layer controls (firewall policies or split tunneling) with application-layer controls (URL Access), assuming that blocking traffic at the IP/port level is sufficient to restrict web-based access within an SSL VPN portal.

How to eliminate wrong answers

Option A is wrong because setting a default bookmark only pre-populates the user's portal with a link to the application; it does not restrict access to other URLs, so users could still navigate to other internal or external sites via the portal. Option B is wrong because a firewall policy controls traffic at the network layer (IP/port), not the application-layer URL access within the SSL VPN web mode portal; users could still access other web applications on the same IP or port if not explicitly blocked at the URL level. Option C is wrong because split tunneling controls whether client traffic goes through the VPN tunnel or directly to the internet for tunnel-mode VPNs, not for web mode portals; it does not restrict which URLs users can access within the portal.

118
Multi-Selectmedium

An administrator is troubleshooting an IPsec VPN that is not passing traffic. The Phase 1 and Phase 2 are both up. Which TWO CLI commands can be used to verify the VPN tunnel status and traffic flow? (Choose two.)

Select 2 answers
A.diagnose vpn tunnel list
B.execute ping-options source
C.diagnose vpn ike config
D.diagnose netlink interface list
E.diagnose sys session list
AnswersA, E

diagnose vpn tunnel list is the primary command for checking the live operational state of IPsec tunnels, showing phase 1 and phase 2 status, SPI values, and negotiation successes or failures. It clearly indicates whether the tunnel is established or down, making it the first step when a VPN connection is not working.

Why this answer

'diagnose vpn tunnel list' displays the status of all IPsec VPN tunnels, including Phase 1 and Phase 2 security associations (SAs), their uptime, and the number of packets transmitted and received. This allows the administrator to verify that the tunnel is established and to check for any packet drops or errors that might indicate a traffic flow issue.

Exam trap

The trap here is that candidates assume 'diagnose vpn ike config' (Option C) shows tunnel status because it relates to IKE, but it only displays static configuration, not the dynamic operational state or traffic counters.

119
MCQeasy

What is the primary function of Fortinet Single Sign-On (FSSO) in a FortiGate deployment?

A.To provide two-factor authentication using FortiToken
B.To sync FortiGate configuration with Active Directory
C.To authenticate users against a RADIUS server
D.To collect user login events from Active Directory for user-based policies
AnswerD

FSSO's primary function is to automatically identify users based on their existing Active Directory login events and map those events to the source IP address of the client machine. A collector agent on the network monitors domain controller security logs or uses RPC calls to track successful user logons, then sends this mapping to the FortiGate. This enables the firewall to enforce user-based policies without prompting for credentials, because the user has already been authenticated by AD. The wrong answers describe other security features, but this is the exact mechanism FSSO provides.

Why this answer

Fortinet Single Sign-On (FSSO) is designed to collect user login events from Active Directory (AD) domain controllers. It monitors authentication traffic (e.g., via NetAPI or polling the AD security event log) to map IP addresses to usernames, enabling FortiGate to enforce user-based firewall policies without requiring users to manually authenticate to the firewall.

Exam trap

The trap here is that candidates often confuse FSSO with direct authentication methods (like RADIUS or LDAP) and assume it performs user authentication, when in fact it only collects existing authentication events from Active Directory for policy enforcement.

How to eliminate wrong answers

Option A is wrong because FSSO does not provide two-factor authentication; that is the function of FortiToken, which integrates with FortiGate for 2FA. Option B is wrong because FSSO does not sync FortiGate configuration with Active Directory; configuration synchronization is handled by FortiManager or ADOMs, not FSSO. Option C is wrong because FSSO does not authenticate users against a RADIUS server; RADIUS authentication is a separate method where the FortiGate acts as a RADIUS client, whereas FSSO passively collects AD login events.

120
MCQmedium

A remote user connects via SSL VPN web mode but cannot access internal resources. The SSL VPN portal is configured with the default settings. What is the most likely reason?

A.The user must be authenticated via LDAP
B.The user has not installed the FortiClient VPN plugin
C.Web mode only allows access to specific bookmarks configured in the portal
D.The SSL VPN policy is missing a security profile
AnswerC

In SSL VPN web mode, the user's entire accessible domain is restricted to the bookmarks that the administrator has explicitly defined in the user's assigned portal. Without pre-configured bookmarks to internal URLs, the portal displays no resources, and the user cannot navigate to any internal application. This is exactly the symptom described: a remote user can connect and authenticate, but there are no portal bookmarks, so no access is granted.

Why this answer

In SSL VPN web mode, the FortiGate acts as a proxy, granting access only to pre-configured bookmarks (URLs or applications) defined in the SSL VPN portal. Default portal settings do not include any bookmarks, so even after successful authentication, the user sees an empty portal and cannot reach internal resources. This is by design, as web mode does not provide full network-layer access like tunnel mode does.

Exam trap

The trap here is that candidates often assume SSL VPN always provides full network access or that a missing security profile is the cause, but the NSE4 exam specifically tests the distinction between web mode (bookmark-based) and tunnel mode (full access).

How to eliminate wrong answers

Option A is wrong because authentication via LDAP is not a requirement for SSL VPN web mode; the user can be authenticated using any supported method (local, RADIUS, etc.) and the portal will still function. Option B is wrong because FortiClient VPN plugin is only required for tunnel mode (full network access) or for host-check features; web mode operates entirely through the browser without any client software. Option D is wrong because security profiles (AV, web filter, IPS) are applied to firewall policies, not directly to SSL VPN policies; the SSL VPN policy itself does not require a security profile to allow web-mode access.

121
Multi-Selecthard

A FortiGate is configured with FSSO and Active Directory polling. Users report that they are frequently prompted for authentication even though they are logged into the domain. Which THREE possible causes should the administrator investigate?

Select 3 answers
A.The user's IP address has changed and the FortiGate still has a stale mapping
B.The FortiToken server is overloaded
C.The user's workstation is not sending logon events to the domain controller
D.The captive portal is enabled on the policy
E.The FortiGate is not polling the domain controllers correctly
AnswersA, C, E

In FSSO, the FortiGate associates a username with the source IP address of the workstation at the moment of logon. If the DHCP lease renews or the user moves to a different subnet, the IP changes without a corresponding logoff/logon event, so the FortiGate retains the stale mapping. Traffic from the new IP is therefore not matched to the user's FSSO group policy, causing the user to be treated as unauthenticated.

Why this answer

FSSO with Active Directory polling relies on the FortiGate maintaining a mapping between a user's domain logon and their IP address. If the user's IP address changes (e.g., due to DHCP lease renewal or moving to a different subnet) and the FortiGate still holds the old mapping, the firewall will not recognize the user as authenticated, prompting re-authentication. This is a common issue in dynamic IP environments where the FortiGate's polling interval may not immediately detect the change.

Exam trap

The trap here is that candidates often confuse FSSO polling with captive portal or FortiToken, assuming any authentication prompt must involve those technologies, when in fact the issue is a stale IP-to-user mapping caused by DHCP changes or delayed DC polling.

122
MCQhard

An administrator configures a dial-up IPsec VPN with IKEv2 to allow remote users to connect. The Phase 1 is set to use certificate-based authentication (PKI). Users can establish Phase 1, but Phase 2 fails with 'no proposal chosen'. The administrator checks the Phase 2 proposal: AES256-SHA256, and the remote network is 10.0.0.0/8 (the corporate LAN). What is the MOST likely cause?

A.The remote network in Phase 2 is set to 10.0.0.0/8
B.The remote network in Phase 2 is set to 0.0.0.0/0
C.The Phase 1 encryption algorithm is mismatched
D.The authentication type requires EAP instead of certificate
AnswerA

The remote network in Phase 2 should be 0.0.0.0/0 for dial-up, because the client's real IP is dynamic. Setting it to 10.0.0.0/8 means the FortiGate expects the client's IP to be in that range, which it is not.

Why this answer

The most likely cause is that the remote network (client subnet) in the Phase 2 configuration on the VPN gateway is set to 10.0.0.0/8 instead of the correct value (0.0.0.0/0) for dial-up clients. Since Phase 1 succeeds, authentication and encryption settings are correct. The 'no proposal chosen' error in Phase 2 indicates a traffic selector mismatch: the server expects the client's IP to be within the 10.0.0.0/8 range, but the client's actual IP typically falls outside that subnet.

Therefore, the Phase 2 negotiation fails.

Exam trap

The trap is that candidates often attribute Phase 2 failures to algorithm mismatches, but in IKEv2 dial-up VPNs, 'no proposal chosen' commonly results from an incorrect Phase 2 traffic selector. Specifically, the remote network (client subnet) on the server side must be set to 0.0.0.0/0 for dial-up clients, not the corporate LAN subnet.

How to eliminate wrong answers

Option B is wrong because setting the remote network to 0.0.0.0/0 would create a default route for all traffic, which is not the specific corporate LAN subnet and would still cause a Phase 2 mismatch if the gateway expects 10.0.0.0/8. Option C is wrong because Phase 1 is already established successfully, indicating that the encryption algorithms (including certificate-based authentication) are correctly matched; a Phase 1 mismatch would prevent Phase 1 from completing. Option D is wrong because certificate-based authentication (PKI) is explicitly configured and Phase 1 succeeds, so EAP is not required; EAP is typically used for extended authentication, not for basic IKEv2 Phase 1 with certificates.

123
MCQmedium

A FortiGate administrator is configuring a hub-and-spoke IPsec VPN. The hub has multiple Phase 2 selectors for each spoke. What is the recommended way to simplify configuration on the hub when adding new spokes?

A.Use a single Phase 2 selector with 0.0.0.0/0.0.0.0 for both local and remote
B.Configure each spoke in a separate VDOM
C.Use aggressive mode for Phase 1
D.Use policy-based VPN instead of route-based
AnswerA

Setting both local and remote Phase 2 selectors to 0.0.0.0/0 creates an any-to-any proxy ID, so all traffic routed into the tunnel interface is encrypted without needing a separate selector per subnet or per spoke. In a route-based VPN, the tunnel interface decouples routing from IPsec proxy IDs, so a single Phase 2 definition can be reused across every spoke; new spokes simply reuse the same selector and rely on routing to direct traffic. This is the standard FortiGate recommendation for hub-and-spoke because it avoids negotiation failures caused by mismatched local/remote subnet definitions and eliminates per-spoke Phase 2 configuration at the hub.

Why this answer

Using a single Phase 2 selector with 0.0.0.0/0.0.0.0 for both local and remote simplifies hub configuration because it allows the hub to accept traffic for any subnet from any spoke without needing to define specific selectors per spoke. This is recommended in hub-and-spoke topologies to avoid manual updates when adding new spokes, as the hub's Phase 2 configuration becomes generic and automatically matches all spoke traffic.

Exam trap

The trap here is that candidates often think policy-based VPNs are simpler for hub-and-spoke, but they actually require explicit selector pairs per spoke, making the hub configuration more complex and less scalable.

How to eliminate wrong answers

Option B is wrong because configuring each spoke in a separate VDOM adds unnecessary administrative overhead and complexity, and does not simplify the Phase 2 selector configuration on the hub. Option C is wrong because aggressive mode for Phase 1 is less secure than main mode (it sends identities in plaintext) and is not related to simplifying Phase 2 selectors; it is typically used for remote access with dynamic IPs, not hub-and-spoke simplification. Option D is wrong because policy-based VPNs require explicit firewall policies for each subnet pair, which actually increases configuration effort when adding new spokes, whereas route-based VPNs with a single Phase 2 selector are simpler for hub-and-spoke designs.

124
MCQhard

You are troubleshooting an SSL VPN connection. The user can reach the SSL VPN portal but cannot ping or access any internal resources. The portal shows the user as authenticated. Which configuration is MOST likely missing?

A.There is no firewall policy allowing traffic from ssl.root to the internal network
B.Client certificate authentication is required but not provided
C.Split tunneling is disabled
D.The SSL VPN realm is not configured correctly
AnswerA

In Fortinet's SSL VPN design, the SSL VPN interface (typically ssl.root) is just a virtual interface; after authentication, the tunnel is up but traffic is still subject to normal firewall policy checks. Without a policy that matches source ssl.root and destination internal network with the appropriate action (accept), the FortiGate silently drops the packets. Thus users can authenticate and establish the tunnel, but cannot reach internal resources until an explicit policy is created, often with NAT and security profiles as needed.

Why this answer

The user can authenticate and reach the SSL VPN portal, which indicates that the SSL VPN tunnel itself is established and authentication is successful. However, the inability to ping or access internal resources despite being authenticated points to a missing firewall policy that explicitly permits traffic from the SSL VPN interface (ssl.root) to the internal network. Without this policy, the FortiGate will drop all traffic from the SSL VPN tunnel, even though the user is logged in.

Exam trap

The trap here is that candidates assume authentication success implies full network access, but FortiGate requires an explicit firewall policy for SSL VPN traffic, separate from the authentication and tunnel setup.

How to eliminate wrong answers

Option B is wrong because client certificate authentication is an additional security layer for the authentication phase; if it were required but not provided, the user would not be able to authenticate or reach the portal at all. Option C is wrong because split tunneling controls whether traffic for internal networks is sent through the VPN tunnel or directly to the internet; disabling split tunneling would actually force all traffic through the tunnel, which would not prevent access to internal resources once the tunnel is up. Option D is wrong because the SSL VPN realm configuration affects the portal page and authentication settings; if the realm were misconfigured, the user would likely not see the correct portal or would fail authentication, but the user is already authenticated and on the portal.

125
MCQmedium

An administrator wants to use Fortinet Single Sign-On (FSSO) with Active Directory to transparently authenticate users. Which component is responsible for polling Active Directory for user logon events?

A.Active Directory Domain Controller
B.FortiGate directly with NTLM authentication
C.FortiAuthenticator
D.FSSO Collector Agent
AnswerD

The FSSO Collector Agent is the correct component because it is explicitly designed to poll the Active Directory security event logs for user logon and logoff events. It runs on a Windows server, uses WMI or NetAPI to query DCs, maintains an IP-to-user mapping table, and transmits that data to FortiGate over the FSSO protocol. This passive collection provides transparent SSO for users already authenticated to AD, without requiring re-authentication.

Why this answer

The FSSO Collector Agent is the component that polls Active Directory domain controllers for security event logs (specifically event ID 4624 for logon events). It then maps these events to user IP addresses and forwards the authentication information to the FortiGate, enabling transparent user identification without requiring client-side software.

Exam trap

The trap here is that candidates often confuse the FSSO Collector Agent with FortiAuthenticator, assuming FortiAuthenticator is always required for FSSO, when in fact the Collector Agent is the primary component for polling Active Directory in a standard FSSO deployment.

How to eliminate wrong answers

Option A is wrong because the Active Directory Domain Controller itself does not poll for logon events; it generates security logs but relies on an external agent (like the FSSO Collector Agent) to poll and process those logs. Option B is wrong because FortiGate directly with NTLM authentication is a separate method (NTLM-based FSSO) that uses browser challenges, not polling of Active Directory logs. Option C is wrong because FortiAuthenticator can act as an FSSO collector in some deployments, but the question specifically asks for the component responsible for polling Active Directory; in a standard FSSO setup, the Collector Agent (installed on a Windows server) performs this polling, while FortiAuthenticator is typically used for RADIUS or LDAP-based authentication, not direct polling of AD logon events.

126
MCQeasy

An administrator wants to authenticate VPN users against an external LDAP server. Which authentication method should be configured in the user group for the SSL VPN portal?

B.FSSO
C.Local
D.LDAP
AnswerD

LDAP authentication enables the FortiGate to validate VPN users by performing a direct bind to the LDAP server (such as Active Directory or OpenLDAP) using the user's distinguished name and password. The FortiGate can also retrieve group memberships during the authentication process, allowing LDAP-based groups to be used in firewall policies. This is the most straightforward and correct method when the authentication source is an LDAP server, as it avoids an extra RADIUS or other proxy layer.

Why this answer

To authenticate VPN users against an external LDAP server, the user group for the SSL VPN portal must be configured with the LDAP authentication method. This directs FortiGate to bind directly to the LDAP server (e.g., Active Directory or OpenLDAP) using the configured LDAP server object, performing a simple bind or SASL bind to verify user credentials. Other methods like RADIUS, FSSO, or Local would not leverage the LDAP server directly.

Exam trap

The trap here is that candidates often confuse 'LDAP' as a protocol with 'RADIUS' as a protocol, assuming both are interchangeable for external authentication, but FortiGate requires the LDAP method specifically when the authentication source is an LDAP directory server, not a RADIUS server.

How to eliminate wrong answers

Option A is wrong because RADIUS is a separate authentication protocol that uses a RADIUS server (e.g., FreeRADIUS or NPS) to proxy authentication, not a direct LDAP bind; it adds an intermediary and does not authenticate directly against LDAP. Option B is wrong because FSSO (Fortinet Single Sign-On) is used for transparent authentication based on Windows domain logon events, not for direct credential validation against an LDAP server for VPN access. Option C is wrong because Local authentication uses locally stored user accounts on the FortiGate, which bypasses any external LDAP server entirely.

127
MCQmedium

A FortiGate administrator configures an SSL VPN web mode portal. Users can access internal web applications but cannot access internal file shares via SMB. What is the most likely reason?

A.The SSL VPN policy does not allow SMB traffic
B.The fileserver requires client certificates for authentication
C.The firewall policy for SSL VPN is configured with the wrong interface
D.Web mode does not support the SMB protocol; users must use tunnel mode to access fileshares
AnswerD

Web mode is a clientless browser-based reverse proxy that only supports HTTP, HTTPS, and certain web applications. The SMB protocol, which runs on TCP port 445 and requires native network layer connectivity, cannot be proxied by web mode. To access SMB fileshares, users must connect using SSL VPN tunnel mode, which creates a virtual interface on the client and routes SMB traffic through the FortiGate.

Why this answer

SSL VPN web mode operates as a reverse proxy, translating HTTP/HTTPS traffic only. SMB (Server Message Block) is a non-web protocol that requires direct network-layer connectivity, which web mode cannot provide. Tunnel mode creates a virtual network interface that allows any IP-based protocol, including SMB, to traverse the VPN.

Therefore, the correct solution is to use tunnel mode for file share access.

Exam trap

The trap here is that candidates often assume SSL VPN policies or firewall rules are misconfigured, overlooking the fundamental architectural limitation that web mode only supports web-based applications, not arbitrary TCP/UDP protocols like SMB.

How to eliminate wrong answers

Option A is wrong because the SSL VPN policy controls access at the application level via the portal, not by filtering specific protocols like SMB; the issue is a protocol limitation, not a policy restriction. Option B is wrong because client certificate authentication is unrelated to protocol support; even if the fileserver required certificates, web mode still cannot proxy SMB traffic. Option C is wrong because the firewall policy interface assignment affects routing, not the protocol capabilities of the SSL VPN portal; web mode inherently lacks SMB support regardless of interface configuration.

128
MCQmedium

A FortiGate admin has configured FSSO (Fortinet Single Sign-On) using Active Directory polling. Users authenticate to the domain but when accessing the internet through the FortiGate, they are still prompted for credentials. What is the MOST likely cause?

A.The FortiGate is not polling the AD domain controllers
B.The users are using non-Windows machines
C.The firewall policy does not have FSSO authentication enabled
D.The FortiGate is not joined to the domain
AnswerA

In FSSO polling mode, the FortiGate acts as a collector agent: it periodically connects to Active Directory domain controllers over LDAP, queries for user logon events (e.g., event ID 4624), and builds a mapping between authenticated usernames and their source IP addresses. If polling is not configured (or the service account's credentials are invalid, or the polling interval is mis-set), the FortiGate never receives that mapping. Consequently, the security policy cannot correlate the incoming traffic with any FSSO user group, so the session is treated as unauthenticated and falls through to the default deny/action rather than prompting for credentials.

Why this answer

In FSSO with Active Directory polling, the FortiGate must be configured to poll the domain controllers to retrieve user logon events. If polling is not set up or fails, the FortiGate will not have the user-to-IP mapping, and thus cannot bypass authentication for domain users, causing them to be prompted for credentials when accessing the internet.

Exam trap

The trap here is that candidates often assume the FortiGate must be domain-joined (Option D) or that the policy is misconfigured (Option C), when the real issue is the lack of polling to collect user logon events.

How to eliminate wrong answers

Option B is wrong because FSSO polling works with any OS that authenticates to the domain; non-Windows machines can still be mapped via IP if they log on to AD. Option C is wrong because the firewall policy must have FSSO authentication enabled to use the user mappings, but the prompt indicates the mapping itself is missing, not the policy configuration. Option D is wrong because the FortiGate does not need to be joined to the domain for FSSO polling; it only needs network access to the domain controllers and the correct service account credentials.

129
MCQmedium

A FortiGate administrator wants to configure a dial-up IPsec VPN where remote users connect using VPN clients with pre-shared key authentication. The company has recently experienced a data breach where the PSK was compromised. What is the best method to improve security without changing all clients immediately?

A.Switch to aggressive mode with a complex PSK
B.Enable XAuth with a second authentication factor using FortiToken
C.Increase the PSK length to 64 characters
D.Migrate to certificate-based authentication for Phase 1
AnswerD

Certificate-based Phase 1 authentication replaces the shared PSK with a unique asymmetric key pair per dial-up peer, binding each client's identity to its certificate. During IKE main mode, certificates enable mutual authentication without ever transmitting a shared secret in the clear, and compromised certificates can be individually revoked via a CRL or OCSP without affecting other peers. This eliminates the single-point-of-failure shared secret and is the correct way to harden a dial-up IPsec VPN.

Why this answer

Migrating to certificate-based authentication eliminates reliance on a static pre-shared key (PSK), which is inherently vulnerable to compromise. Certificates provide asymmetric cryptographic proof of identity, ensuring that even if a PSK is leaked, the attacker cannot authenticate without a valid certificate. This is the most robust long-term fix for PSK compromise in IPsec VPNs.

Exam trap

The trap here is that candidates often confuse user authentication (XAuth) with Phase 1 authentication, mistakenly believing that adding a second factor like FortiToken fixes the compromised PSK, when in fact the PSK is still used and vulnerable in the initial IKE exchange.

How to eliminate wrong answers

Option A is wrong because aggressive mode actually reduces security by sending the PSK in cleartext during Phase 1 negotiation, making it easier to capture and exploit. Option B is wrong because XAuth with FortiToken adds a second authentication factor for user identity, but it does not replace or secure the compromised PSK used in Phase 1; the PSK remains the weak link. Option C is wrong because increasing the PSK length to 64 characters only increases brute-force resistance, but does not address the fact that the PSK has already been compromised and is known to an attacker.

130
MCQmedium

A FortiGate admin is troubleshooting an IPsec VPN tunnel that fails to establish. The remote site uses aggressive mode. The local FortiGate is configured for main mode. The admin sees 'no proposal chosen' in the IKE debug. What is the MOST likely cause?

A.The pre-shared key is incorrect
B.The IKE mode (main vs aggressive) does not match between peers
C.The local firewall is blocking UDP port 500
D.The Phase 2 encryption algorithm is not supported
AnswerB

Main mode and Aggressive mode differ in the number of IKE messages and whether the SA proposal is sent in the first packet with the same structure. When one peer is set to Main mode and the other to Aggressive mode, the responder sees a proposal that does not match the expected exchange type and therefore rejects it with a NO_PROPOSAL_CHOSEN notify, because the transforms are not considered valid for the configured mode. This is one of the classic causes of this exact error on FortiGate.

Why this answer

The 'no proposal chosen' error in IKE debug indicates a mismatch in the IKE parameters proposed by the peers. Since the remote site uses aggressive mode and the local FortiGate is configured for main mode, the IKE mode mismatch prevents the peers from agreeing on a proposal. IKE main mode and aggressive mode use different packet formats and exchange sequences, so they cannot negotiate a common proposal even if all other parameters match.

Exam trap

The trap here is that candidates often associate 'no proposal chosen' only with encryption or authentication algorithm mismatches, overlooking that IKE mode mismatch is also a proposal-level failure that triggers the same error in IKE debug.

How to eliminate wrong answers

Option A is wrong because an incorrect pre-shared key would cause an authentication failure (e.g., 'invalid cookie' or 'authentication failed') in IKE debug, not a 'no proposal chosen' error. Option C is wrong because if UDP port 500 were blocked, the FortiGate would not receive any IKE packets at all, leading to a timeout or 'no response' message, not a proposal mismatch. Option D is wrong because Phase 2 encryption algorithm mismatches are detected during Phase 2 negotiation (Quick Mode), not during Phase 1 (IKE) where the 'no proposal chosen' error occurs.

131
MCQmedium

An administrator wants to use ZTNA (Zero Trust Network Access) to secure access to an internal application. Which component is required on the client device to enforce ZTNA policies?

A.FortiManager
B.FortiToken
C.FortiClient
D.FortiAnalyzer
AnswerC

FortiClient is the endpoint agent that performs the critical ZTNA posture assessment, checking for compliance criteria such as updated antivirus definitions, disk encryption, and approved software versions. It communicates this telemetry to a FortiGate or FortiEMS, which then issues a short-lived token only if the endpoint is compliant and the user identity is verified. When the user attempts to access a ZTNA-protected application, FortiClient presents that token, enabling the FortiGate to enforce granular access and maintain a secure connection. This makes FortiClient the mandatory client-side enforcement component that embodies ZTNA's continuous trust verification.

Why this answer

FortiClient is the required endpoint component for ZTNA because it acts as the ZTNA agent on the client device, establishing a secure tunnel (via IPSec or SSL VPN) to the FortiGate and enforcing posture checks (e.g., OS version, antivirus status) before granting access. Without FortiClient, the FortiGate cannot verify the device's trust level or enforce ZTNA access policies at the endpoint.

Exam trap

The trap here is that candidates often confuse FortiClient with FortiToken, assuming that MFA alone is sufficient for ZTNA, but ZTNA requires endpoint posture enforcement via FortiClient, not just authentication factors.

How to eliminate wrong answers

Option A is wrong because FortiManager is a centralized management platform for multiple FortiGate devices, not an endpoint component; it does not reside on the client device or enforce ZTNA policies locally. Option B is wrong because FortiToken is a two-factor authentication (2FA) hardware or software token used for MFA, not for device posture assessment or ZTNA policy enforcement on the client. Option D is wrong because FortiAnalyzer is a logging and analytics appliance that collects logs from FortiGate and other Fortinet devices; it does not run on the client or enforce access policies.

132
MCQmedium

A FortiGate administrator has configured a route-based IPsec VPN. After Phase 2 is up, traffic is not passing. The administrator verifies that the firewall policy allows traffic and the routes are correct. What should the administrator check next?

A.The static route uses the VPN interface as the outgoing interface
B.The remote gateway's IP address is reachable
C.The pre-shared key is correct
D.The Phase 2 proposal includes the correct local and remote subnets
AnswerA

In a route-based VPN, the virtual IPsec interface serves as the tunnel endpoint, and the static route must specify that interface as the outgoing interface for the remote subnet. Without this route, the FortiGate has no entry in its routing table to direct traffic into the IPsec tunnel, even if Phase 1 and Phase 2 SAs are fully established. The route triggers the actual forwarding decision, causing the kernel to encapsulate and encrypt matching traffic over the tunnel.

Why this answer

In a route-based IPsec VPN, traffic is routed to the VPN tunnel interface (e.g., 'to_remote'). Even if firewall policies and static routes exist, the static route must explicitly use the VPN interface as the outgoing interface. If the static route points to a different interface or a next-hop IP instead of the tunnel interface, the kernel will not forward traffic into the IPsec tunnel, causing Phase 2 to be up but no traffic to pass.

This is a common misconfiguration that breaks the route-based VPN model.

Exam trap

The trap here is that candidates assume Phase 2 being up guarantees traffic flow, overlooking that route-based VPNs require the static route to explicitly use the tunnel interface as the outgoing interface, not just any valid next-hop.

How to eliminate wrong answers

Option B is wrong because the remote gateway's IP address being reachable is a prerequisite for Phase 1 (IKE) to establish, not a cause for traffic failure after Phase 2 is up. Option C is wrong because an incorrect pre-shared key would prevent Phase 1 from completing, but the question states Phase 2 is up, meaning Phase 1 and authentication succeeded. Option D is wrong because if the Phase 2 proposal included incorrect local or remote subnets, Phase 2 would not come up; since Phase 2 is up, the proposal is correct, and the issue lies in how traffic is routed to the tunnel.

133
MCQmedium

A FortiGate administrator configures a captive portal on a VDOM to authenticate users connecting to a guest SSID. The authentication method is set to LDAP. Users can reach the captive portal login page, but after entering valid credentials, they receive an authentication failure. The LDAP server is reachable from the FortiGate. What is the MOST likely cause?

A.The user is not a member of the configured user group
B.The captive portal is using HTTP instead of HTTPS
C.The captive portal interface is not in the same VDOM as the LDAP server
D.The LDAP server requires TLS and FortiGate is using plain LDAP
AnswerA

FortiGate uses LDAP for credential validation, but the firewall policy specifies a particular user group that must contain the authenticated account. After the LDAP bind succeeds, FortiGate performs a group lookup against the configured group; if the user is not a member, the captive portal rejects the login even though the password was correct. This is an authorization failure rather than an authentication failure, and it is the classic cause of a captive portal rejecting valid LDAP creds.

Why this answer

The most likely cause is that the user is not a member of the configured user group. In FortiGate, when LDAP authentication is used for a captive portal, the FortiGate first verifies the user's credentials against the LDAP server. Even if the credentials are valid, the FortiGate then checks whether the authenticated user belongs to a specific user group that is permitted to access the captive portal.

If the user is not a member of that group, the authentication fails, even though the LDAP server itself accepts the credentials.

Exam trap

The trap here is that candidates often assume LDAP authentication failure is always due to connectivity or protocol issues (like TLS or HTTP), but FortiGate's group membership enforcement is a distinct step that can cause failure even with valid credentials and a reachable server.

How to eliminate wrong answers

Option B is wrong because using HTTP instead of HTTPS for the captive portal would not cause an authentication failure after valid credentials are entered; it would only expose credentials in transit but not prevent successful authentication. Option C is wrong because the captive portal interface and the LDAP server do not need to be in the same VDOM; the LDAP server is reachable from the FortiGate, and VDOM separation does not affect LDAP authentication as long as routing permits. Option D is wrong because if the LDAP server required TLS and the FortiGate used plain LDAP, the connection would fail entirely, and the user would not even reach the captive portal login page or receive an authentication failure after entering credentials; instead, a timeout or connection error would occur.

134
MCQmedium

An administrator needs to configure two-factor authentication for SSL VPN users using FortiToken. Which configuration is required on the FortiGate?

A.Enable two-factor authentication globally on the FortiGate
B.Enable FortiToken on the user account and configure the authentication scheme to require token
C.Install the FortiToken mobile app on the FortiGate
D.Create a separate firewall policy for token-based authentication
AnswerB

To enforce two-factor, assign a FortiToken to the user account in the user definition (e.g., register the FortiToken Mobile seed) and then set the required authentication method in the authentication scheme to 'FortiToken' or 'Token-based'. The scheme, not the firewall policy, defines how many and which authentication factors are accepted, and this scheme is then referenced by the security policy using identity-based authentication. Without assigning the token and enforcing it in the scheme, merely having the app installed does nothing.

Why this answer

FortiGate requires two-factor authentication to be enabled on the user account itself (via the 'Two-factor Authentication' field set to 'FortiToken') and then an authentication scheme must be configured that includes a 'Token' requirement. This ensures that the user must provide both their password and a one-time token from the FortiToken device or app during SSL VPN login.

Exam trap

The trap here is that candidates assume two-factor authentication is a global setting or that installing the app on the FortiGate is required, when in fact it is a per-user configuration combined with an authentication scheme and rule.

How to eliminate wrong answers

Option A is wrong because FortiGate does not have a global toggle for two-factor authentication; it must be configured per user or per user group. Option C is wrong because the FortiToken mobile app is installed on the user's smartphone, not on the FortiGate itself; the FortiGate only needs the token seed or serial number. Option D is wrong because firewall policies do not control authentication methods; they control traffic flow based on source/destination, and token-based authentication is handled at the authentication profile or scheme level, not in a firewall policy.

135
MCQhard

An administrator needs to implement two-factor authentication for SSL VPN access using FortiToken. Which configuration steps are required?

A.Assign a FortiToken to the user and set the user's authentication method to two-factor
B.Configure the RADIUS server to send FortiToken challenges
C.Enable FortiToken on the firewall policy
D.Enable two-factor authentication on the SSL VPN portal settings
AnswerA

In FortiOS, two-factor authentication is a property of the user object, not the service. You must first assign a FortiToken (hardware or mobile token) to the user, then set the user's 'Two-factor Authentication' to 'FortiToken' (or 'Email' etc). Only then will FortiGate challenge the user with a token code during any authentication flow, including firewall login, SSL VPN, or IPsec. This ensures the token is bound to the user and enforced universally.

Why this answer

To implement two-factor authentication for SSL VPN using FortiToken, you must assign a FortiToken to the user and set the user's authentication method to two-factor. This is done in the user configuration (e.g., under User & Authentication > User Definition) by selecting 'FortiToken' as the second factor and linking the token serial number. This ensures that during SSL VPN login, the user must provide both their password and a one-time password from the FortiToken, which is validated locally by the FortiGate without requiring an external RADIUS server.

Exam trap

The trap here is that candidates often assume two-factor authentication can be enabled globally on the SSL VPN portal or firewall policy, but Fortinet specifically requires the token to be assigned to the individual user object with the authentication method set to two-factor, making option A the only correct step among the choices.

How to eliminate wrong answers

Option B is wrong because configuring the RADIUS server to send FortiToken challenges is not required; FortiToken authentication is handled natively by the FortiGate itself, not via RADIUS challenge-response. Option C is wrong because enabling FortiToken on the firewall policy is not a valid step; firewall policies control traffic flow but do not have a direct setting for FortiToken—two-factor authentication is configured at the user or authentication rule level. Option D is wrong because enabling two-factor authentication on the SSL VPN portal settings is not sufficient; the portal settings control interface behavior (e.g., web mode options) but do not enforce token-based authentication—that requires the user object to have the token assigned and the authentication method set to two-factor.

136
MCQmedium

During an IPsec VPN troubleshooting, you run 'diagnose vpn ike config' and see the output includes 'peer-id: any'. What does this mean?

A.The FortiGate will accept connections from any remote IP address.
B.The FortiGate will use aggressive mode for IKE negotiation.
C.The Phase 2 selectors are configured for any protocol.
D.The FortiGate will accept any peer identity during IKE authentication.
AnswerD

In FortiOS, when the Phase 1 configuration sets peer-id to 'any' (or leaves it unset), the FortiGate does not validate the identity payload sent by the remote gateway during IKE negotiation. Instead, it accepts any peer ID, relying solely on the PSK or certificate for authentication. This is useful when the remote peer uses a dynamic identifier, but it should be used with caution because identity-based verification is disabled. This is the correct behavior.

Why this answer

The 'peer-id: any' output in 'diagnose vpn ike config' indicates that the FortiGate is configured to accept any peer identity during IKE authentication. This means the FortiGate will not validate the identity presented by the remote peer (e.g., IP address, FQDN, or user ID) against a specific value in the Phase 1 configuration. This is common when using pre-shared keys and not requiring strict peer identity validation.

Exam trap

The trap here is that candidates often confuse 'peer-id: any' with allowing any source IP address (Option A), but it specifically controls identity validation during IKE authentication, not the remote gateway IP.

How to eliminate wrong answers

Option A is wrong because 'peer-id: any' refers to the peer identity used during IKE authentication, not the source IP address; the remote IP address is controlled by the 'remote-gw' setting. Option B is wrong because aggressive mode is determined by the 'mode' setting (aggressive vs. main) in the Phase 1 configuration, not by the peer-id value. Option C is wrong because Phase 2 selectors (protocol, port, etc.) are configured separately under the Phase 2 settings, and 'peer-id: any' has no relation to them.

137
Multi-Selectmedium

A FortiGate administrator is configuring a hub-and-spoke IPsec VPN with three spokes. Each spoke has a dial-up connection to the hub. The hub uses a dynamic DNS name. Which THREE settings are necessary on each spoke to establish the VPN?

Select 3 answers
A.A static route on the spoke for the hub's local networks
B.The pre-shared key or certificate for authentication
C.Hub's public IP address or FQDN as remote gateway
D.The Phase 2 proposal (encryption, authentication, etc.)
E.NAT enabled on the spoke tunnel interface
AnswersB, C, D

The pre-shared key or certificate is a mandatory authentication credential for IKE Phase 1, used by both sides to mutually authenticate before any encryption negotiation occurs. Without a matching PSK or a valid trusted certificate on the spoke, the hub will reject the initial IKE request, and no tunnel can be built. FortiGate supports both PSK and certificate-based authentication, but one must be explicitly configured on the spoke.

Why this answer

In a hub-and-spoke IPsec VPN with dial-up spokes, each spoke must authenticate with the hub. The pre-shared key or certificate (Option B) is required for IKE Phase 1 authentication, ensuring the spoke is trusted before the tunnel is established. Without this, the hub will reject the connection attempt.

Exam trap

The trap here is that candidates often think a static route (Option A) is required for VPN establishment, but routes only direct traffic after the tunnel is up, not for the IKE negotiation itself.

138
MCQhard

A FortiGate administrator is troubleshooting a dial-up IPsec VPN where remote users can connect but traffic does not pass. The Phase 1 and Phase 2 status show 'up'. The administrator runs 'diagnose vpn tunnel list' and sees the tunnel is up. However, 'diagnose sys session list' shows no sessions for the remote user's IP. What is the MOST likely cause?

A.The Phase 2 proposal uses AES256 but the remote client only supports AES128
B.The FortiGate's routing table does not have a route to the remote user's subnet
C.There is no firewall policy permitting traffic from the dial-up interface to the destination network
D.The remote user's FortiClient is blocking split tunneling
AnswerC

The FortiGate's implicit deny rule silently discards any traffic that does not match an explicit firewall policy, including traffic arriving from a dial-up IPsec tunnel interface. Even if the Phase 1 and Phase 2 SAs are fully up, the FortiGate will not forward packets from the remote VPN user to the internal destination unless a policy exists allowing that traffic between the VPN interface (e.g., ssl.root or dialup) and the destination zone. Since the session table is empty, the packets are being dropped by the firewall policy lookup, making a missing policy the most direct and common cause.

Why this answer

Even when Phase 1 and Phase 2 are up and the tunnel is established, traffic will not pass through a dial-up IPsec VPN unless a firewall policy explicitly permits traffic from the dial-up interface (often the virtual IPsec interface) to the destination network. The 'diagnose sys session list' showing no sessions for the remote user's IP confirms that the FortiGate is not processing any traffic for that user, which points to a missing or misconfigured firewall policy rather than an encryption or routing issue.

Exam trap

The trap here is that candidates assume an 'up' Phase 1 and Phase 2 guarantee traffic flow, but FortiGate requires a separate firewall policy to permit traffic from the IPsec interface to the destination, and the absence of sessions in 'diagnose sys session list' is the key diagnostic clue for this missing policy.

How to eliminate wrong answers

Option A is wrong because if the Phase 2 proposal used AES256 but the remote client only supported AES128, the Phase 2 would not come up at all; the status would show 'down' or negotiation would fail. Option B is wrong because in a dial-up IPsec VPN, the remote user's IP is dynamically assigned and not a subnet that requires a static route; the FortiGate uses the IPsec interface itself to route traffic back to the remote user. Option D is wrong because split tunneling on FortiClient controls which traffic goes over the VPN versus the local internet, but it does not prevent the FortiGate from seeing sessions; if the tunnel is up and traffic is sent, sessions would appear in 'diagnose sys session list' regardless of split tunneling settings.

139
MCQmedium

A company wants to provide remote access to internal resources for employees using laptops that may connect from untrusted networks. The security team requires that all traffic between the remote users and the corporate network be encrypted, and that users must authenticate using a username/password plus a one-time passcode from a hardware token. Which FortiGate VPN solution best meets these requirements?

A.IPsec VPN with certificate-based authentication
B.SSL VPN with local password authentication
C.SSL VPN with FortiToken two-factor authentication
D.L2TP/IPsec VPN with a pre-shared key and user password
AnswerC

SSL VPN with FortiToken two-factor authentication correctly combines HTTPS-based encrypted remote access with a time-based one-time password (TOTP) generated by FortiToken. This provides two distinct factors: something the user knows (password) and something the user has (FortiToken device or mobile app). FortiGate can enforce this at the firewall policy level, ensuring both factors are verified before tunnel establishment.

Why this answer

SSL VPN with FortiToken two-factor authentication meets the requirement for encrypted remote access with username/password plus a one-time passcode from a hardware token. SSL VPN provides encrypted tunnels over HTTPS, and FortiToken adds the required second factor, ensuring strong authentication even from untrusted networks.

Exam trap

The trap here is that candidates may assume any VPN with encryption (like IPsec or L2TP/IPsec) automatically supports two-factor authentication, but FortiGate requires explicit configuration of a second factor like FortiToken, and SSL VPN is the typical solution for this requirement in the NSE4 exam context.

How to eliminate wrong answers

Option A is wrong because IPsec VPN with certificate-based authentication provides encryption but does not inherently support a one-time passcode from a hardware token; it relies on certificates, not two-factor authentication. Option B is wrong because SSL VPN with local password authentication provides encryption but only uses a single factor (password), failing the requirement for a one-time passcode. Option D is wrong because L2TP/IPsec VPN with a pre-shared key and user password provides encryption but uses only a pre-shared key and password, lacking the required two-factor authentication with a hardware token.

140
MCQmedium

In a hub-and-spoke IPsec VPN topology with FortiGate, the spoke sites cannot communicate directly with each other. What configuration change allows direct spoke-to-spoke communication?

A.Set the 'add-route' option to 'enable' on the spoke Phase 1 settings
B.Configure dynamic routing (BGP) on all sites and enable route exchange
C.Add static routes on the hub pointing to each spoke's subnet via the respective tunnels
D.Create a separate IPsec VPN between each spoke pair
AnswerD

A full mesh of separate IPsec tunnels between every spoke pair gives each site a direct path, bypassing the hub entirely. This satisfies the requirement for direct spoke-to-spoke communication, though it scales poorly as tunnel count grows quadratically.

Why this answer

In a hub-and-spoke IPsec VPN topology, spoke sites cannot communicate directly by default. To enable direct spoke-to-spoke communication, the most straightforward configuration change is to create separate IPsec VPN tunnels between each spoke pair. While ADVPN (Auto Discovery VPN) with dynamic routing is a more efficient method, it is not listed as an option.

Option D directly establishes the required tunnels, allowing traffic to bypass the hub for spoke-to-spoke traffic. Other options are insufficient: Option A only adds routes for the hub, Option B only propagates routes without establishing direct tunnels, and Option C forces traffic through the hub.

Exam trap

The trap is that candidates may think dynamic routing alone enables direct communication, but it only shares routes. Without ADVPN or explicit Phase 2 selectors, traffic still flows through the hub. The only listed option that actually creates a direct tunnel is D.

How to eliminate wrong answers

Option A is wrong because the 'add-route' option on the spoke Phase 1 settings controls whether the FortiGate automatically adds a route to the remote subnet via the IPsec tunnel, but it does not enable direct spoke-to-spoke communication; it only affects routing to the hub. Option C is wrong because adding static routes on the hub pointing to each spoke's subnet via the respective tunnels would only route traffic through the hub, not allow direct spoke-to-spoke communication; the traffic would still be forwarded through the hub, not directly between spokes. Option D is wrong because creating a separate IPsec VPN between each spoke pair would work but is not a configuration change that enables direct communication within the existing hub-and-spoke topology; it is a different topology altogether and defeats the purpose of a hub-and-spoke design.

141
MCQhard

An administrator is troubleshooting an IPsec VPN that fails to establish. The 'diagnose vpn ike log' shows 'initial contact received'. What does this message indicate?

A.The pre-shared key is incorrect
B.The Phase 1 proposal is mismatched
C.The remote peer has restarted and cleared its security associations
D.A network address translation device is altering the IKE packets
AnswerC

When the remote peer restarts (e.g., a firewall reboot or IPsec process restart), it may send an 'Initial Contact' informational message in IKEv2 (or a delete SA notification in IKEv1) to tell the local peer to purge all existing Security Associations for that peer. If the local peer does not process or receive this message, or if the remote peer does not send it, the local peer may still reference a stale SA, causing the tunnel to fail during rekeying or when a new SA is attempted. The 'Initial Contact' mechanism is designed to force the old SAs to be deleted and a new tunnel to be established.

Why this answer

In IPsec IKE (Internet Key Exchange), an 'initial contact' notification is sent by a peer to inform the other side that it has just restarted or cleared its security associations (SAs). This message tells the receiving peer to delete any existing SAs associated with that peer, allowing a fresh IKE negotiation to begin. Therefore, the message indicates the remote peer has restarted and cleared its SAs, not a configuration or NAT issue.

Exam trap

The trap here is that candidates often misinterpret 'initial contact' as a configuration mismatch or authentication error, but it is actually a standard IKE notification indicating a peer restart, not a failure cause.

How to eliminate wrong answers

Option A is wrong because an incorrect pre-shared key would cause an authentication failure during Phase 1, typically shown as 'no proposal chosen' or 'invalid payload' in the logs, not an 'initial contact' message. Option B is wrong because a Phase 1 proposal mismatch results in the peers failing to agree on encryption/hash parameters, leading to 'no proposal chosen' errors, not an 'initial contact' notification. Option D is wrong because a NAT device altering IKE packets would cause issues like 'NAT traversal mismatch' or 'payload length mismatch', not the specific 'initial contact' message, which is a legitimate IKE notification payload (RFC 2408).

142
MCQmedium

A FortiGate administrator is troubleshooting an SSL VPN connection issue. Users can connect but cannot access internal resources. The administrator checks the SSL VPN policy and confirms it allows access to the internal subnet. What should the administrator check next?

A.Verify that the firewall policy between the SSL VPN interface and the internal network allows the traffic
B.Check the routing table on the FortiGate for the internal subnet
C.Ensure the users have the correct client software installed
D.Check the FortiGate's DNS settings
AnswerA

SSL VPN traffic terminates on the FortiGate, then is re-evaluated against firewall policy before reaching the internal subnet. The SSL VPN portal policy alone does not permit forwarding, so a missing or misordered policy from the SSL VPN interface to the internal network silently drops the traffic.

Why this answer

Even if the SSL VPN policy permits access to the internal subnet, traffic must still traverse a firewall policy from the SSL VPN interface (e.g., ssl.root) to the internal network interface. Without an explicit firewall policy allowing the traffic, the FortiGate will drop the packets, preventing resource access. This is a common oversight because the SSL VPN policy only controls tunnel establishment and route injection, not the actual forwarding of traffic between zones.

Exam trap

The trap here is that candidates assume the SSL VPN policy alone governs all access, overlooking the separate firewall policy requirement that actually enforces traffic flow between the SSL VPN interface and the internal network.

How to eliminate wrong answers

Option B is wrong because the routing table on the FortiGate is not the primary issue here; if users can connect to the SSL VPN, the FortiGate typically installs a route for the virtual IP pool, and the internal subnet route is usually present. Option C is wrong because the users are already connected, indicating the client software is functioning correctly for the tunnel; the problem is post-connection traffic forwarding. Option D is wrong because DNS settings affect name resolution, not direct IP-based access to internal resources; if users can connect but cannot access resources by IP, DNS is irrelevant.

143
Multi-Selecteasy

An administrator needs to configure ZTNA (Zero Trust Network Access) on a FortiGate to provide secure remote access to an internal application. Which components are required for a basic ZTNA configuration? (Choose three.)

Select 3 answers
A.IPsec VPN tunnel
B.ZTNA proxy (application gateway)
C.Captive portal
D.ZTNA rule (policy) on the FortiGate
E.Access proxy (or application) configuration
AnswersB, D, E

ZTNA proxy (application gateway): Correct. The ZTNA proxy is the FortiGate's application-layer reverse proxy that terminates the user's HTTPS connection and forwards requests to the internal application server. It validates the user's identity and device posture before proxying any traffic, and it only exposes the specific application port, not the full network. This proxy is the core enforcement point for ZTNA policy.

Why this answer

The ZTNA proxy (application gateway) is the core component that terminates client connections and forwards them to internal applications after verifying device and user identity. It acts as a reverse proxy, enforcing access policies before allowing any traffic to reach the protected resource. Without this gateway, the FortiGate cannot mediate ZTNA connections.

Exam trap

The trap here is that candidates often confuse ZTNA with traditional VPNs and incorrectly assume an IPsec tunnel is mandatory, when in fact ZTNA uses a TLS reverse proxy and does not require any VPN tunnel.

144
MCQmedium

You are troubleshooting an IPsec VPN between two FortiGates. The Phase 1 is up, but Phase 2 is not coming up. You check the Phase 2 configuration on both sides. What is a common cause of this issue?

A.Mismatch in Phase 2 settings such as encryption algorithm, authentication algorithm, or PFS group
B.Firewall policy not allowing ESP traffic
C.Incorrect local or remote gateway IP
D.Mismatch in Phase 1 pre-shared key
AnswerA

Phase 2 negotiation (Quick Mode in IKEv1) is separate from Phase 1 and uses its own proposal set. For a FortiGate-to-FortiGate VPN, the encryption algorithm (e.g., AES128 vs AES256), authentication/HMAC algorithm (e.g., SHA1 vs SHA256), and Perfect Forward Secrecy (PFS) group (e.g., None vs DH14) must match exactly on both peers. If PFS is enabled on one side but not the other, or the DH groups differ, Phase 2 will fail with a proposal or no-proposal-match error even though Phase 1 is healthy.

Why this answer

When Phase 1 is up but Phase 2 fails, the most common cause is a mismatch in Phase 2 parameters. Phase 2 uses IPsec SA proposals that must match exactly on both sides, including encryption algorithm (e.g., AES256), authentication algorithm (e.g., SHA256), and Perfect Forward Secrecy (PFS) group (e.g., DH14). Even a single mismatch, such as one side using PFS and the other not, will prevent Phase 2 from establishing.

Exam trap

The trap here is that candidates often confuse Phase 1 and Phase 2 issues, assuming any mismatch in authentication or encryption must be Phase 1, but FortiGate separates these phases, and Phase 2 mismatches are a distinct and common cause of partial VPN failure.

How to eliminate wrong answers

Option B is wrong because firewall policies not allowing ESP traffic would typically affect Phase 1 or all IPsec traffic, not specifically Phase 2; Phase 1 uses UDP ports 500/4500, and if ESP were blocked, Phase 1 would also fail. Option C is wrong because incorrect local or remote gateway IPs would prevent Phase 1 from coming up, as Phase 1 relies on matching peer IPs and IKE negotiation. Option D is wrong because a mismatch in Phase 1 pre-shared key would cause Phase 1 to fail, not Phase 2; Phase 2 only begins after Phase 1 is successfully established.

145
MCQeasy

What is the primary advantage of using route-based IPsec VPN over policy-based IPsec VPN?

A.Route-based VPN allows the use of dynamic routing protocols over the tunnel
B.Route-based VPN requires fewer firewall policies
C.Route-based VPN is easier to configure for hub-and-spoke
D.Route-based VPN supports higher encryption algorithms
AnswerA

Route-based IPsec VPN creates a virtual tunnel interface, allowing the underlying IPsec connection to participate in dynamic routing protocols such as OSPF, EIGRP, or BGP. This enables automatic route advertisement and convergence, eliminating the need for static proxy-IDs for each destination network, and making large-scale, redundant VPN topologies far more practical to deploy and maintain.

Why this answer

Route-based IPsec VPNs create a virtual tunnel interface (e.g., `tunnel` or `ipsec` interface) that acts as a logical routing endpoint. This allows the tunnel to participate in dynamic routing protocols like OSPF or BGP, enabling automatic route advertisement and failover across the VPN. Policy-based VPNs, in contrast, rely on static security policies that match traffic based on source/destination addresses and ports, which cannot be dynamically updated by routing protocols.

Exam trap

The trap here is that candidates often confuse 'fewer firewall policies' (Option B) as the primary advantage, but the NSE4 exam emphasizes that the key differentiator is the ability to use dynamic routing protocols over the tunnel, which is not possible with policy-based VPNs.

How to eliminate wrong answers

Option B is wrong because route-based VPNs typically require fewer firewall policies only in the sense that traffic is matched via routing rather than per-flow policies, but this is not the primary advantage; the core benefit is dynamic routing. Option C is wrong because while route-based VPNs can simplify hub-and-spoke topologies, this is a consequence of dynamic routing support, not the primary advantage; policy-based VPNs can also be used for hub-and-spoke with manual configuration. Option D is wrong because both route-based and policy-based VPNs support the same encryption algorithms (e.g., AES-256, SHA-256) as defined by the IPsec proposal; the choice of algorithm is independent of the VPN type.

146
MCQmedium

An admin wants users to authenticate once via AD and have their network access controlled without repeated logins. Which feature should be used?

A.Local user authentication
B.FSSO with Active Directory polling
C.Captive portal with LDAP
D.SSL VPN with certificate authentication
AnswerB

FSSO with AD polling provides true single sign-on by having the FortiGate (via the FSSO agent) monitor the domain controller's security event log for successful logons. When a user logs into the domain, the agent maps the user name to the workstation's IP address and updates the FortiGate's user list, enabling firewall policies to be applied without any user prompt. This transparently authenticates the user for network access and exactly matches the 'authenticate once via AD' requirement.

Why this answer

FSSO with Active Directory polling allows users to authenticate once at Windows logon, and FortiGate polls the AD domain controllers to capture authentication events. This enables transparent network access control without repeated logins, as the user's identity and group memberships are mapped to firewall policies automatically.

Exam trap

The trap here is that candidates often confuse FSSO with captive portal or LDAP authentication, thinking any AD integration provides single sign-on, but only FSSO (polling or agent-based) captures the Windows logon event to avoid repeated authentication prompts.

How to eliminate wrong answers

Option A is wrong because local user authentication requires users to manually log in to the FortiGate (e.g., via captive portal or SSL VPN) and does not provide single sign-on from AD. Option C is wrong because captive portal with LDAP still requires users to enter credentials each time they open a browser, and it does not leverage the initial Windows logon for transparent access. Option D is wrong because SSL VPN with certificate authentication is a remote access VPN method, not a solution for controlling network access for on-net users without repeated logins.

147
MCQmedium

A FortiGate is configured with an IPsec VPN to a remote site using IKEv1. The VPN tunnel goes down intermittently. The admin runs 'diagnose vpn ike gateway list' and sees 'state=UP' but no Phase2 selectors. What is the most likely cause?

A.The firewall policy allowing IPsec traffic is misconfigured
B.The remote gateway has a different PSK
C.Mismatched Phase2 parameters between the local and remote gateways
D.Dead Peer Detection (DPD) is disabled
AnswerC

Phase2 negotiation, also known as Quick Mode in IKEv1, is dedicated to agreeing on IPsec SA parameters such as encryption algorithm, integrity algorithm, DH group, PFS, and SA lifetimes. If the local FortiGate proposes a set of algorithms that do not overlap with the remote gateway's configured Phase2 proposal, the negotiation ends in a NO_PROPOSAL_CHOSEN error and no IPsec SA is created. The tunnel may appear to be up (Phase1 complete) but never passes traffic because Phase2 is stuck or continuously re-negotiating. Matching every parameter, including subtle settings like PFS and key lifetime, is mandatory for successful Phase2 establishment.

Why this answer

When 'diagnose vpn ike gateway list' shows the IKE gateway state as UP but no Phase2 selectors are present, it indicates that the IKE Phase1 (main mode or aggressive mode) has completed successfully, but the IPsec Phase2 (quick mode) negotiation has failed. The most common cause for this is a mismatch in Phase2 parameters such as encryption algorithm, authentication algorithm, or proxy IDs (local/remote subnets) between the local and remote gateways. Since the tunnel goes down intermittently, the Phase2 rekey may be failing due to these mismatches, causing the tunnel to drop until a successful renegotiation occurs.

Exam trap

The trap here is that candidates often assume a UP gateway state means the entire VPN tunnel is working, but in IKEv1, Phase1 can be UP while Phase2 is down, leading to intermittent connectivity; the key is to check Phase2 selectors separately.

How to eliminate wrong answers

Option A is wrong because a misconfigured firewall policy allowing IPsec traffic would typically prevent the IKE gateway from reaching the UP state at all, as Phase1 would fail to complete. Option B is wrong because a different PSK would cause Phase1 authentication to fail, resulting in the gateway state being DOWN or NEGO_FAIL, not UP. Option D is wrong because disabling DPD would not cause the gateway to show UP without Phase2 selectors; DPD is used to detect peer liveness and would affect the gateway state if the peer is unreachable, but it does not directly prevent Phase2 negotiation.

148
MCQmedium

An admin is configuring a dial-up IPsec VPN for remote users. The users will connect from various public IP addresses. Which Phase 1 configuration is required for the FortiGate to accept connections from unknown remote gateways?

A.Enable aggressive mode
B.Set the remote gateway to 0.0.0.0
C.Configure a static route to the remote users' subnet
D.Set the remote gateway to a specific IP address
AnswerB

Setting the remote gateway to 0.0.0.0 is the core dialup Phase 1 setting on a FortiGate: it instructs the device to accept incoming IKE connections from any source IP address rather than from one fixed peer. This wildcard is what enables remote users with dynamic public IPs to build a tunnel, because the actual peer address is learned automatically when the client initiates Phase 1 negotiation. Combined with peer type 'one', this makes the FortiGate operate as the dialup VPN server.

Why this answer

For a dial-up IPsec VPN where remote users connect from dynamic public IP addresses, the FortiGate must be configured to accept connections from any remote gateway. Setting the remote gateway to 0.0.0.0 (or 0.0.0.0/0) in Phase 1 tells the FortiGate to accept IKE negotiation from any source IP, which is essential for dial-up scenarios. This is the standard method to allow unknown remote gateways to initiate the VPN tunnel.

Exam trap

The trap here is that candidates often confuse the need for aggressive mode (option A) with the requirement to accept unknown remote gateways, but aggressive mode is about identity protection and faster negotiation, not about allowing any source IP to initiate the tunnel.

How to eliminate wrong answers

Option A is wrong because aggressive mode is not required for dial-up VPNs; it is an optional IKE mode that sends the identity in clear text and is less secure, but the key requirement is the remote gateway wildcard, not the mode. Option C is wrong because a static route to the remote users' subnet is needed for traffic forwarding after the tunnel is established, but it does not affect Phase 1 acceptance of unknown remote gateways. Option D is wrong because setting the remote gateway to a specific IP address would restrict the FortiGate to only accept connections from that single IP, which defeats the purpose of a dial-up VPN for users with dynamic public IPs.

← PreviousPage 2 of 2 · 148 questions total

Ready to test yourself?

Try a timed practice session using only Nse4 Auth Vpn questions.