Courseiva
Authentication and VPN →hardMultiple Select

NSE4 Practice Question: A FortiGate administrator is troubleshooting an IPsec VPN between two FortiGates

A FortiGate administrator is troubleshooting an IPsec VPN between two FortiGates. The tunnel is established, but traffic is not passing. The administrator runs 'diagnose vpn ike log' and sees the following output: IKE: phase 2 negotiation completed IKE: IPsec SA up What THREE possible causes should the administrator investigate?

⚠ Common exam trap

Candidates often assume a successful IPsec SA (phase 2 up) guarantees traffic flow, but FortiGate requires separate firewall policies and routing configuration for traffic to traverse the tunnel.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Firewall policies on either FortiGate are not allowing traffic between the local and remote subnets

Even though the IPsec SA is up (phase 2 completed), traffic will not pass unless firewall policies explicitly permit traffic between the local and remote subnets. FortiGate requires a policy that allows the traffic and references the VPN tunnel interface as the outgoing interface.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Firewall policies on either FortiGate are not allowing traffic between the local and remote subnets

    Why this is correct

    Even after an IPsec tunnel reaches Phase 2, traffic is still subject to the firewall policy database on each FortiGate. If no policy with action ACCEPT exists that matches the source/destination subnets and the incoming/outgoing interface (e.g., the IPsec virtual interface), the firewall silently drops the packets. A common misconfiguration is creating a policy for the WAN interface instead of the tunnel interface, or setting the wrong local/remote addresses in the policy.

  • ✗

    The pre-shared key is incorrect

    Why it's wrong here

    The pre-shared key is used during IKE Phase 1 authentication to establish the ISAKMP/IKE SA. If the PSK were incorrect on either side, Phase 1 would fail with an authentication error, and no Phase 2 negotiations would occur. Since the log explicitly shows Phase 2 completed, both peers successfully authenticated, proving the PSK values match and are correct.

  • ✓

    Routing tables on both FortiGates do not have routes pointing to the remote subnets via the VPN interface

    Why this is correct

    For encrypted traffic to flow, each FortiGate must have a route that directs the remote VPN subnet's destination addresses to the IPsec tunnel interface (e.g., a static route with device 'to_remote_vpn'). Without such a route, packets destined for the remote LAN are sent out the default WAN route or dropped, never entering the tunnel interface for encryption. Even if firewall policies allow the traffic, the absence of a route prevents the kernel from selecting the IPsec interface as the next hop.

  • ✗

    The IKE mode is set to aggressive mode on one side and main mode on the other

    Why it's wrong here

    IKE aggressive mode and main mode are Phase 1 exchange modes; they determine how the IKE SA is authenticated and how many packets are exchanged. A mismatch in these modes causes a Phase 1 failure—the two peers cannot agree on the IKE SA parameters, so the tunnel never reaches Phase 2. Because Phase 2 has completed, the Phase 1 negotiation must have succeeded, meaning both sides used a compatible mode (likely main mode).

  • ✓

    NAT is being applied to the VPN traffic before it enters the tunnel, causing IP address mismatch

    Why this is correct

    If a NAT policy (or central NAT) is applied to traffic that should be sent through the IPsec tunnel, the firewall may translate the source IP before encryption. The remote FortiGate then decapsulates the packet and checks the inner IP addresses against the Phase 2 selectors (proxy IDs); a mismatched source address, such as 192.168.1.10 translated to 10.10.10.10, fails this check and is dropped. Additionally, the tunnel's Phase 2 selectors are negotiated based on the original addresses, so any NAT applied to VPN-bound traffic breaks the end-to-end flow even though the SA is up.

Visual reference

192.168.1.0 /24 256 addresses (254 usable) 192.168.1.0 /25 Subnet A 128 addr (126 usable) 192.168.1.128 /25 Subnet B 128 addr (126 usable) Borrowing 1 bit from host portion creates 2 subnets (/25)

Quick reference

VPN Protocol Comparison

ProtocolPortEncryptionAuthenticationUse Case
IKEv2 / IPsecUDP 500 / 4500AES-256Certificates / PSKSite-to-site & remote access
SSL / TLS VPNTCP 443TLS 1.3Certificates / MFAClientless remote access
L2TP / IPsecUDP 1701AES (IPsec)PSK / CertificatesLegacy remote access
WireGuardUDP 51820ChaCha20Public keysModern high-performance VPN
PPTPTCP 1723MPPE (weak)MS-CHAPv2Legacy — avoid in production

PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.

About these practice questions

One of 773 original NSE4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar NSE4 questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

This NSE4 practice question is part of Courseiva's free Fortinet certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the NSE4 exam.