Question 140
A team proposes to close this Fortinet incident: A FortiManager SD-WAN template is changed for a pilot but accidentally targeted to every region. Which verification should it require?
Explanation
Correct Answer
This is the specific acceptance result for the remediation: Limit the deployment target to the approved pilot devices and verify preflight differences. It tests the underlying dependency: Template scope and installation targets determine the change blast radius.
Incorrect Answers
The option would apply to “After resolving FortiAnalyzer stores branch SD-WAN logs but FortiSASE cloud events are absent from the security incident dashboard”. This observation is aligned with the affected component. This question instead requires “Only pilot branches receive the modified SD-WAN configuration”.
The suggested option corresponds to this separate situation: An enterprise uses FortiManager for SD-WAN templates but engineers edit branch FortiGates locally without reconciling the central policy. It does not address the mechanism present here: Template scope and installation targets determine the change blast radius.
This alternative addresses the separate case “For this FortiSASE or SD-WAN problem, A FortiAnalyzer reporting pipeline fails after a collector address migration but FortiGate logs still show local traffic records”. The principle is: Local event generation and centralized delivery are separate operations. The deciding requirement here is “Only pilot branches receive the modified SD-WAN configuration”.