Question 40
A Fortinet architect receives this requirement: A team wants to confirm which SD-WAN member carried a customer transaction last Tuesday. Which change should the team implement first?
Explanation
Correct Answer
The change needed here is: Correlate FortiAnalyzer traffic logs with rule, member and device timestamps. Relevant Fortinet behavior: Historical forwarding evidence depends on retained SD-WAN traffic and event logs. Acceptance evidence should show: The selected member and relevant SLA state can be reconstructed for the incident.
Incorrect Answers
The source problem for this choice is two uplinks appear healthy but a configured performance SLA threshold is stricter than the measured application can reasonably achieve. The reported scenario has a different controlling condition: Historical forwarding evidence depends on retained SD-WAN traffic and event logs.
This option serves the scenario “A team configures passive SLA monitoring on a member carrying almost no application traffic and expects uninterrupted measurement”. The change needed here is: Use an appropriate supported active or passive strategy and verify the sample data source. The present scenario is distinguished by “Correlate FortiAnalyzer traffic logs with rule, member and device timestamps”.
The suggested action is the untested workaround in the scenario. It fails to account for this requirement: Historical forwarding evidence depends on retained SD-WAN traffic and event logs. Use the scoped change: Correlate FortiAnalyzer traffic logs with rule, member and device timestamps.