Question 130
A network architect investigates this Fortinet environment: An application team sees traffic logs but no SLA member-change events after an outage. What underlying distinction most directly explains the symptoms?
Explanation
Correct Answer
The condition is explained by the following rule: Different operational events require appropriate SD-WAN logging and FortiAnalyzer ingestion. Address it with this step: Check enabled SD-WAN event logging and the collector's received log types. Check that: A controlled member failure produces an identifiable change event in analytics.
Incorrect Answers
This option serves the scenario “In a Fortinet troubleshooting exercise, A SOC investigator compares a FortiClient event and FortiSASE POP event but the two systems report different timezone offsets”. The best diagnosis is: Time normalization is essential to reconstructing multi-product event order. The present scenario is distinguished by “Different operational events require appropriate SD-WAN logging and FortiAnalyzer ingestion”.
The option would apply to “A dashboard reports normal average internet latency but a few sites experience severe packet-loss spikes”. The decisive technical principle is: Averages can conceal outliers that break application SLAs for individual branches. This question instead requires “Different operational events require appropriate SD-WAN logging and FortiAnalyzer ingestion”.
The related but distinct situation is “In a Fortinet troubleshooting exercise, A security analyst sees an allowed web request in FortiAnalyzer but cannot tell which SD-WAN rule and member carried it”. The best diagnosis is: Application traffic records and member-selection events must be correlated for path attribution. For the stated problem, “Different operational events require appropriate SD-WAN logging and FortiAnalyzer ingestion” addresses the central condition.