Question 80
A FortiSASE operator faces this issue: A digital experience monitoring probe shows high latency but operators immediately blame the endpoint antivirus process. What corrective configuration or investigation is most appropriate?
Explanation
Correct Answer
The corrective step is: Compare DEM path metrics with tunnel, POP and endpoint resource health. The case turns on this distinction: DEM measurements need correlation with endpoint, network and application signals. Afterward, confirm: The affected segment of the user-to-service path is identified from correlated evidence.
Incorrect Answers
This shortcut is attractive but misses the underlying condition: DEM measurements need correlation with endpoint, network and application signals. The case requires the targeted remedy: Compare DEM path metrics with tunnel, POP and endpoint resource health.
This alternative does not match the described failure pattern. It concerns a new endpoint posture policy marks every device compliant if FortiClient can reach the cloud management service; the focused result here is: Compare DEM path metrics with tunnel, POP and endpoint resource health.
This choice addresses a different case in the same task group: A FortiClient endpoint on hotel Wi-Fi connects to SASE but the original hotel captive portal cannot be reached for initial sign-in. The present situation is: A digital experience monitoring probe shows high latency but operators immediately blame the endpoint antivirus process. Its decisive action is: Compare DEM path metrics with tunnel, POP and endpoint resource health.