NSE7 Enterprise Firewall and VDOMs Practice Question
In FortiManager, what is an automation stitch?
⚠ Common exam trap
Candidates often confuse automation stitches with simple scheduled scripts (Option B), but the key distinction is that stitches are event-driven and can include multiple conditional actions, not just time-based execution.
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
✓
A sequence of automated actions triggered by a specific event
An automation stitch in FortiManager is a sequence of automated actions (such as running scripts, sending alerts, or executing CLI commands) that are triggered by a specific event (e.g., a log message, a SNMP trap, or a schedule). This allows administrators to automate incident response and policy changes without manual intervention, directly within the FortiManager fabric.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A feature to stitch multiple ADOMs together
Why it's wrong here
Automation stitches coordinate trigger-and-action pairs within FortiManager, not administrative domains; ADOMs are separate management partitions and are not joined by stitches. It is tempting because stitches do link multiple components, and would be correct if the goal were consolidating device management across domains rather than automating responses.
- ✗
A set of scripts that run on a schedule
Why it's wrong here
Automation stitches trigger actions in response to FortiGate event log entries, not on a time schedule; scheduled execution is handled by separate automation settings. It is tempting because stitches do run scripts automatically, and would be correct if the requirement were recurring maintenance tasks rather than event-driven responses.
- ✗
A method to combine multiple policy packages
Why it's wrong here
Automation stitches define event triggers and resulting actions, not policy package consolidation; combining packages is done through installation targets and policy assignment. It is tempting because stitches do combine multiple elements into one workflow, and would be correct for orchestrating scripted responses rather than merging firewall policies.
- ✓
A sequence of automated actions triggered by a specific event
Why this is correct
An automation stitch pairs a trigger event with one or more automated actions, such as running a CLI script or sending an alert when that event fires. It is not a static policy or a scheduled report; execution depends on the triggering event occurring.
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 →
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.