NSE7 Advanced VPN and Zero Trust Practice Question
A company is deploying ZTNA to protect an internal application. They want to ensure that only users with devices that have disk encryption enabled and the latest OS patches can access the application. Which THREE components must be configured to achieve this?
⚠ Common exam trap
NSE7 often tests the division of labor between FortiClient (collector), EMS (policy/tag engine), and FortiGate (enforcer) — candidates who conflate FortiNAC's NAC role with ZTNA posture enforcement pick the FortiNAC distractor.
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
✓
FortiClient on the endpoint device
Option C is correct because FortiClient is the endpoint agent that performs the on-device posture checks (disk encryption status and OS patch level) and reports that information to FortiClient EMS. Option E is correct because FortiClient EMS is where the compliance/ZTNA tagging policies are defined and where tags (such as 'disk-encrypted' and 'patched') are assigned to endpoints based on those posture results. Option D is correct because the FortiGate ZTNA access proxy enforces tag-based rules, only allowing access to the internal application when the endpoint presents the required compliance tags. Option A is not needed since FortiNAC provides network admission control (NAC) for LAN/port-level access, not ZTNA application access control. Option B is not required because ZTNA uses TLS-based access proxy tunnels rather than an IPsec VPN to reach the protected application.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
FortiNAC for network admission control
Why it's wrong here
FortiNAC performs network admission control at the switch or wireless layer, profiling and quarantining devices before they join the network; it does not evaluate disk encryption or OS patch status for application access. FortiNAC fits wired/wireless onboarding and IoT visibility scenarios, not ZTNA per-application posture checks.
- ✗
IPsec VPN to encrypt traffic between client and FortiGate
Why it's wrong here
IPsec VPN encrypts traffic in transit but inspects no endpoint state, so disk encryption and patch level remain unchecked; ZTNA enforces posture through FortiClient EMS tags and access proxy rules. IPsec suits site-to-site or remote-access tunnelling where only confidentiality between gateways is required.
- ✓
FortiClient on the endpoint device
Why this is correct
FortiClient performs the endpoint posture checks for disk encryption and OS patch level, then reports compliance to EMS. These checks generate the tags that the FortiGate evaluates, so FortiClient is essential to enforce the stated conditions.
- ✓
FortiGate ZTNA access proxy with tag-based rules
Why this is correct
FortiGate ZTNA access proxy with tag-based rules enforces access by matching device tags dynamically assigned by FortiClient EMS, which reports disk encryption status and OS patch level. This satisfies the stem's constraint that only compliant devices reach the internal application, since the proxy denies sessions lacking the required tags.
- ✓
FortiClient EMS to define compliance policies and assign tags
Why this is correct
FortiClient EMS defines the compliance rules that evaluate disk encryption and OS patch level, then assigns the resulting tags to managed endpoints. FortiGate ZTNA policies reference these tags, so only tagged compliant devices gain access to the internal application.
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 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.