The correct answer is to create a local-in policy to allow management access only from the trusted host. This is the proper method to restrict FortiGate management access to a specific IP because local-in policies operate at the control plane level, filtering traffic destined to the FortiGate itself before it reaches management daemons like HTTPS or SSH. Unlike firewall policies, which handle traffic passing through the device, local-in policies directly control which sources can reach the FortiGate’s own IP addresses, making them the precise tool for this task. On the Fortinet NSE 4 Network Security Professional exam, this question tests your understanding of control plane protection versus data plane forwarding—a common trap is confusing local-in policies with regular firewall policies or trusted hosts settings in the admin GUI, which only apply to local GUI/SSH sessions, not remote internet access. Remember the memory tip: “Local-in locks the door to the FortiGate itself, while firewall policies only guard the hallway.”
NSE4 System and Network Administration Practice Question
This NSE4 practice question tests your understanding of system and network administration. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A FortiGate administrator needs to allow remote management from the internet only from a specific IP address. Which configuration achieves this?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a local-in policy to allow management access only from the trusted host
A local-in policy is the correct method to restrict remote management access to a FortiGate from the internet because it operates at the control plane level, filtering traffic destined to the FortiGate itself before it reaches the management daemons. By specifying a source IP address in a local-in policy, you can explicitly allow HTTPS or SSH management only from that trusted host, while implicitly denying all other sources. This is more secure than relying on firewall policies, which apply to traffic passing through the FortiGate, not to traffic destined to the FortiGate's own IP addresses.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Create a local-in policy to allow management access only from the trusted host
Why this is correct
Local-in policies control traffic destined to the FortiGate itself, allowing source IP restriction.
Related concept
Read the scenario before looking for a memorised answer.
✗
Change the admin port to a non-standard port
Why it's wrong here
Port obfuscation does not restrict source IP.
✗
Enable HTTPS and restrict admin access via admin host
Why it's wrong here
Admin host sets trusted hosts but is not as granular as local-in policies for source IP.
✗
Use a firewall policy with source address restriction
Why it's wrong here
Firewall policies apply to forwarded traffic, not traffic destined to the FortiGate.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse firewall policies (which control traffic passing through the FortiGate) with local-in policies (which control traffic destined to the FortiGate), leading them to incorrectly select option D, thinking a standard firewall policy can restrict management access from the internet.
Detailed technical explanation
How to think about this question
Local-in policies are processed by the FortiGate's control plane before any management daemon (e.g., HTTPS, SSH, SNMP) processes the packet, making them the most secure method for restricting management access. The 'trusted host' feature (under system admin) is actually implemented as an implicit local-in policy, but it only supports a single source IP or subnet per administrator; a custom local-in policy allows more complex rules, such as multiple source IPs or different services per source. In real-world scenarios, an administrator might combine a local-in policy with a loopback interface to ensure management access is only possible from a specific VPN or jump host, even if the FortiGate's physical interface IP is exposed.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A security administrator must allow nursing staff to reach a patient records server while blocking access from the guest Wi-Fi VLAN. After applying an extended ACL, traffic is still blocked from nursing workstations. The ACL was applied outbound instead of inbound on the wrong interface. Questions like this test ACL direction and placement rules.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
System and Network Administration — This question tests System and Network Administration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a local-in policy to allow management access only from the trusted host — A local-in policy is the correct method to restrict remote management access to a FortiGate from the internet because it operates at the control plane level, filtering traffic destined to the FortiGate itself before it reaches the management daemons. By specifying a source IP address in a local-in policy, you can explicitly allow HTTPS or SSH management only from that trusted host, while implicitly denying all other sources. This is more secure than relying on firewall policies, which apply to traffic passing through the FortiGate, not to traffic destined to the FortiGate's own IP addresses.
What should I do if I get this NSE4 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.