NSE7 Advanced VPN and Zero Trust Practice Question
An administrator wants to configure a multi-peer IPsec VPN where one FortiGate (hub) connects to multiple remote FortiGates (spokes) using a single phase 1 interface with dynamic IP addresses. Which configuration is required on the hub?
⚠ Common exam trap
NSE7 often tests the specific FortiGate syntax for dial-up VPNs — candidates confuse aggressive mode (an IKEv1 mode) with the `type dynamic` / `remote-gw 0.0.0.0` configuration that actually enables dynamic peer acceptance.
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
✓
Set type to dynamic and set remote-gw 0.0.0.0
For a hub-and-spoke IPsec VPN where spokes have dynamic IP addresses, the hub's phase 1 must be configured with `set type dynamic` and `set remote-gw 0.0.0.0` so it can accept connections from any peer IP. This allows a single phase 1 interface to serve multiple spokes with dynamic addresses, which is the standard FortiGate dial-up VPN configuration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set psksecret to a group password and enable XAuth
Why it's wrong here
XAuth authenticates individual users after phase 1 and does not let one phase 1 interface accept multiple dynamic spokes; the hub needs a dial-up phase 1 with a wildcard peer. XAuth is tempting because it centralises credential checks, and it would be correct where per-user authentication is required.
- ✗
Set mode to aggressive and use pre-shared keys
Why it's wrong here
Aggressive mode with pre-shared keys still binds phase 1 to one peer identity, so multiple dynamic spokes cannot share the interface; the hub requires a dial-up phase 1 accepting any remote gateway. Aggressive mode is tempting because it suits dynamic-IP peers, but it does not provide the multi-peer wildcard matching needed here.
- ✗
Set type to static and configure each peer's IP in separate phase1
Why it's wrong here
Static type with a separate phase 1 per peer cannot work when spokes have dynamic IP addresses, since their addresses are unknown in advance. It is tempting because separate phase 1 tunnels are the normal approach for a small number of fixed-IP peers, which is precisely the scenario where this configuration would be correct.
- ✓
Set type to dynamic and set remote-gw 0.0.0.0
Why this is correct
A dynamic phase 1 with remote-gw 0.0.0.0 lets the hub accept connections from any spoke IP, satisfying the requirement for multiple spokes with dynamic addresses on a single interface. Static remote-gw would permit only one peer.
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
Courseiva writes every NSE7 question from scratch — 718 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on NSE7
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An administrator needs to configure a site-to-site IPsec VPN with a remote FortiGate that has a dynamic IP address. Which phase1 parameter must be set to support this?
easy- A.Enable Perfect Forward Secrecy (PFS)
- B.Enable NAT traversal
- C.Use certificate-based authentication
- ✓ D.Set mode to aggressive and use a pre-shared key
Why D: When the remote FortiGate has a dynamic IP address, the local FortiGate cannot initiate the VPN because it does not know the remote peer's IP. Setting the phase1 mode to aggressive and using a pre-shared key allows the remote peer to initiate the connection by sending its identity (ID) in the first exchange, enabling the local FortiGate to identify and authenticate the peer without requiring a static IP address for the remote side.
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Fortinet exam blueprint
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.