Question 100
In the following Fortinet incident—The SOC receives FortiSASE alerts but ignores branch routing events that occurred at the same time—what concern should the team explicitly mitigate?
Explanation
Correct Answer
This hazard is more relevant than general operational concerns because cross-layer security investigations require correlating cloud protection with network changes. Apply the limited change: Join FortiSASE and SD-WAN events using device, user and timestamp identifiers.
Incorrect Answers
The option would apply to “A rollout manager compares FortiManager device-online status to FortiSASE web-policy compliance and declares both healthy”. This is the most direct failure mode to prevent. This question instead requires “Siloed evidence can lead investigators to remediate the wrong component”.
The related but distinct situation is “The engineering team is reviewing A FortiAnalyzer reporting pipeline fails after a collector address migration but FortiGate logs still show local traffic records”. This hazard is more relevant than general operational concerns because local event generation and centralized delivery are separate operations. For the stated problem, “Siloed evidence can lead investigators to remediate the wrong component” addresses the central condition.
This alternative addresses the separate case “An enterprise uses FortiManager for SD-WAN templates but engineers edit branch FortiGates locally without reconciling the central policy”. The failure exposure comes from the underlying condition: Centralized management requires a controlled configuration source of truth and policy reconciliation. The deciding requirement here is “Siloed evidence can lead investigators to remediate the wrong component”.