The answer is to create an automation stitch that triggers on local-in policy logging and executes a CLI script to block the source IP. This is correct because an automation stitch on FortiGate can directly react to a local-in policy log event—such as a failed administrative login from outside the management network—and run a CLI command like `diagnose user banned-ip add <srcip> 1800` to add the offending IP to the local banned user list for 30 minutes, all without needing FortiAnalyzer or FortiManager. On the Fortinet NSE 4 exam, this scenario tests your understanding of automation stitches as a self-contained, on-box solution for dynamic threat response, often appearing as a trick where candidates mistakenly look for external logging or SDN connectors. A common trap is assuming a local-in policy’s block-session-ttl alone handles automatic blocking, but that only blocks the current session, not future attempts. Memory tip: think “stitch triggers on log, script bans the IP”—the local-in policy logs the fail, the stitch stitches the block.
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 large enterprise is deploying a FortiGate 600F as the perimeter firewall. The security team requires that all administrative access (SSH, HTTPS, and Ping) to the FortiGate must be restricted to a dedicated management network (10.10.10.0/24). Additionally, any failed login attempt from outside the management network should be logged and the source IP should be blocked for 30 minutes. The administrator has configured a local-in policy to deny all administrative access from non-management networks and enabled logging. However, the administrator wants to automatically block the offending IPs. The FortiGate is not connected to any FortiAnalyzer or FortiManager. What should the administrator do to achieve this?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create an automation stitch that triggers on local-in policy logging and adds the source IP to a blocked list via CLI script.
Option A is correct because an automation stitch can directly react to local-in policy log events by executing a CLI script that adds the offending source IP to a local banned user list (e.g., via `diagnose user banned-ip add`). This provides automatic, immediate blocking without requiring external devices like FortiAnalyzer, and the 30-minute duration can be set via the ban-time parameter in the script or the local-in policy's block-session-ttl.
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 an automation stitch that triggers on local-in policy logging and adds the source IP to a blocked list via CLI script.
Why this is correct
Automation stitch can execute a script to block the IP.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a FortiAnalyzer to generate alerts and send to SIEM.
Why it's wrong here
No FortiAnalyzer available.
✗
Configure a firewall policy to block the offending IPs manually based on logs.
Why it's wrong here
Manual process not automated.
✗
Enable 'set block-session-ttl' on the local-in policy.
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse 'block-session-ttl' (which only controls session timeout for already-blocked traffic) with automatic IP banning, or assume external devices like FortiAnalyzer are required when the FortiGate's automation stitch can handle the task locally.
Detailed technical explanation
How to think about this question
Automation stitches in FortiOS allow event-driven responses using triggers like 'event-log' for local-in policy logs. The CLI script can execute `diagnose user banned-ip add <ip> <timeout>` to add the IP to the local banned list, which is stored in memory and persists until the timeout expires. This approach is ideal for environments without FortiAnalyzer, as it leverages the FortiGate's built-in event handling and avoids external dependencies.
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 an automation stitch that triggers on local-in policy logging and adds the source IP to a blocked list via CLI script. — Option A is correct because an automation stitch can directly react to local-in policy log events by executing a CLI script that adds the offending source IP to a local banned user list (e.g., via `diagnose user banned-ip add`). This provides automatic, immediate blocking without requiring external devices like FortiAnalyzer, and the 30-minute duration can be set via the ban-time parameter in the script or the local-in policy's block-session-ttl.
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.