Question 520
In the following Fortinet incident—FortiManager SD-WAN monitoring shows one path missing but FortiAnalyzer historical reports show it was active yesterday—what concern should the team explicitly mitigate?
Explanation
Correct Answer
This hazard is more relevant than general operational concerns because current state and past logs answer different operational questions and both are required. Apply the limited change: Correlate present member configuration with archived member-state events.
Incorrect Answers
The alternative is useful for a SASE policy change coincides with an increase in denied SaaS requests but reporting omits policy revision identifiers, but it does not resolve the observed condition here: Current state and past logs answer different operational questions and both are required. The answer is: Only reading current status cannot explain when a member stopped being eligible.
This option serves the scenario “A FortiAnalyzer report counts application sessions but a manager interprets that figure as the number of distinct users”. This hazard is more relevant than general operational concerns because session count and unique user count are different analytics measures. The present scenario is distinguished by “Only reading current status cannot explain when a member stopped being eligible”.
This alternative addresses the separate case “An application team sees traffic logs but no SLA member-change events after an outage”. This is the most direct failure mode to prevent. The deciding requirement here is “Only reading current status cannot explain when a member stopped being eligible”.