NSE7 Advanced VPN and Zero Trust Practice Question
A company uses SSL VPN with FortiGate for remote access. Users report that after connecting, they can access internal web servers but cannot ping them. Which configuration is most likely missing?
⚠ Common exam trap
It's easy for candidates to assume split tunneling or DNS is the cause, but the real issue is that ICMP is a separate protocol that must be explicitly permitted in the firewall policy, unlike TCP-based web traffic.
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 policy allowing ICMP
SSL VPN tunnels typically allow TCP-based traffic like HTTP/HTTPS to internal web servers, but ICMP (ping) is a separate protocol that requires explicit permission in the firewall policy. Without a firewall policy rule permitting ICMP from the SSL VPN interface to the internal network, the FortiGate will drop the ping requests, even though the tunnel is established and other traffic flows.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Split tunneling settings
Why it's wrong here
Split tunnelling controls which destinations route through the tunnel, not whether ICMP is permitted; web access already works, so routing is functioning. It tempts because split tunnelling shapes reachability, and it would be correct if internal resources were unreachable while internet traffic worked.
- ✗
SSL VPN web portal settings
Why it's wrong here
The SSL VPN web portal serves browser-based access to internal applications, so it has no bearing on ICMP from a tunnel-mode client. It tempts because portal settings govern remote access, and it would be correct if users connected through the portal rather than the tunnel client.
- ✓
Firewall policy allowing ICMP
Why this is correct
SSL VPN tunnel mode permits traffic only through firewall policies referencing the SSL VPN tunnel interface. Web access works because an existing policy allows HTTP/HTTPS, but ICMP echo has no matching policy, so pings are dropped. Adding an ICMP-accepting policy on that interface restores reachability.
- ✗
DNS server configuration
Why it's wrong here
DNS resolution affects name lookups, but the users can already reach internal web servers by name, so name resolution is working and ICMP remains blocked by policy. It tempts because DNS misconfiguration commonly breaks internal access, and it would be correct if hostnames failed to resolve while IP connectivity succeeded.
Quick reference
VPN Protocol Comparison
| Protocol | Port | Encryption | Authentication | Use Case |
|---|---|---|---|---|
| IKEv2 / IPsec | UDP 500 / 4500 | AES-256 | Certificates / PSK | Site-to-site & remote access |
| SSL / TLS VPN | TCP 443 | TLS 1.3 | Certificates / MFA | Clientless remote access |
| L2TP / IPsec | UDP 1701 | AES (IPsec) | PSK / Certificates | Legacy remote access |
| WireGuard | UDP 51820 | ChaCha20 | Public keys | Modern high-performance VPN |
| PPTP | TCP 1723 | MPPE (weak) | MS-CHAPv2 | Legacy — avoid in production |
PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.
Go deeper
Related to this question
About these practice questions
This NSE7 question is part of Courseiva's 718-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This NSE7 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 NSE7 exam.