The answer is that a FortiManager automation stitch may fail to trigger due to a mismatch between the stitch’s defined event type and the actual event generated by the FortiGate, such as selecting 'event-log' when the device sends a 'traffic-log' entry. This is a fundamental condition for stitch execution because the automation engine on FortiManager compares the incoming event’s type against the trigger criteria; if they do not align, the stitch simply ignores the event. On the Fortinet NSE 7 Advanced Security NSE7 exam, this concept tests your understanding of how automation stitches rely on precise event matching, often appearing in troubleshooting scenarios where a stitch appears correctly configured but never fires. A common trap is assuming any log entry will trigger the stitch, when in fact the event type must be explicitly set to match the FortiGate’s log category. Remember the memory tip: “Match the type, or the stitch is ripe for a strike.”
NSE7 Enterprise Firewall and VDOMs Practice Question
This NSE7 practice question tests your understanding of enterprise firewall and vdoms. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 security analyst notices that an automation stitch in FortiManager did not trigger when a specific event occurred on a managed FortiGate. Which three possible reasons could explain why the stitch did not fire? (Choose three.)
The trigger event type does not match the actual event
If the trigger is set for a different event type, it will not fire.
B
The FortiGate has reached its license limit for automation stitches
Why wrong: License limits affect the number of stitches, not whether they trigger.
C
The automation stitch was configured with a condition that was not met
Why wrong: While a condition could prevent triggering, the question asks for reasons why it did not fire; all three preceding are valid and conditions are part of normal operation.
D
The automation stitch is disabled
A disabled stitch will not trigger.
E
The FortiManager had a temporary network connectivity issue with the FortiGate
If connectivity is lost, the stitch cannot be triggered from FortiManager.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The trigger event type does not match the actual event
Option A is correct because an automation stitch in FortiManager triggers only when the event type defined in the stitch matches the actual event generated by the FortiGate. If the event type (e.g., 'event-log' vs. 'traffic-log') does not match, the stitch will not fire. This is a fundamental condition for stitch execution.
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.
✓
The trigger event type does not match the actual event
Why this is correct
If the trigger is set for a different event type, it will not fire.
Related concept
Read the scenario before looking for a memorised answer.
✗
The FortiGate has reached its license limit for automation stitches
Why it's wrong here
License limits affect the number of stitches, not whether they trigger.
✗
The automation stitch was configured with a condition that was not met
Why it's wrong here
While a condition could prevent triggering, the question asks for reasons why it did not fire; all three preceding are valid and conditions are part of normal operation.
✓
The automation stitch is disabled
Why this is correct
A disabled stitch will not trigger.
Related concept
Read the scenario before looking for a memorised answer.
✓
The FortiManager had a temporary network connectivity issue with the FortiGate
Why this is correct
If connectivity is lost, the stitch cannot be triggered from FortiManager.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing a condition (which is checked after the trigger fires) with the trigger itself, leading candidates to incorrectly select Option C as a reason the stitch did not fire at all.
Detailed technical explanation
How to think about this question
Automation stitches in FortiManager use a trigger-action-condition model. The trigger defines the event (e.g., a specific log ID or SNMP trap) that must occur on the managed FortiGate. If the trigger event type does not match, the stitch is never evaluated. Additionally, the FortiManager must maintain an active management tunnel (port 541/TCP) to receive event notifications; a network issue would prevent the event from reaching FortiManager, causing the stitch not to fire.
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 practitioner preparing for the NSE7 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
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.
Enterprise Firewall and VDOMs — This question tests Enterprise Firewall and VDOMs — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The trigger event type does not match the actual event — Option A is correct because an automation stitch in FortiManager triggers only when the event type defined in the stitch matches the actual event generated by the FortiGate. If the event type (e.g., 'event-log' vs. 'traffic-log') does not match, the stitch will not fire. This is a fundamental condition for stitch execution.
What should I do if I get this NSE7 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 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.
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.