Question 490
After resolving A FortiSASE deployment sends cloud traffic analytics to FortiAnalyzer but omits link and branch identifiers needed for incident response, which evidence would establish that the requirement was met?
Explanation
Correct Answer
This is the specific acceptance result for the remediation: Normalize endpoint, branch, POP and SD-WAN identifiers in the analytics workflow. It tests the underlying dependency: Cross-system logs need a mapping between user sessions, cloud enforcement and WAN edge paths.
Incorrect Answers
This option serves the scenario “After resolving A security architect designs secure private access through SD-WAN but does not explain”. An effective postchange test must exercise the intended path. The present scenario is distinguished by “Investigators correlate one SASE event to its originating branch and network member”.
The option would apply to “A remote endpoint is allowed to browse SaaS through FortiSASE but company policy requires one SaaS application's API traffic to be audited separately”. The mechanism at issue is: SaaS security controls must be mapped to specific application and action risks. This question instead requires “Investigators correlate one SASE event to its originating branch and network member”.
This choice addresses a different case in the same task group: A remote office has an SD-WAN private hub and cloud SASE connectivity but a migration proposal removes the hub before replacing internal service connectivity. The present situation is: A FortiSASE deployment sends cloud traffic analytics to FortiAnalyzer but omits link and branch identifiers needed for incident response. Its decisive proof is: Investigators correlate one SASE event to its originating branch and network member.