Question 220
In a production design review, A FortiAnalyzer report aggregates all tenant browsing events and is shared with individual MSSP customers. Which next technical step addresses the actual constraint?
Explanation
Correct Answer
The corrective step is: Create authorized tenant-scoped reports and verify reviewer permissions. The case turns on this distinction: Central visibility must enforce customer-specific data access boundaries. Afterward, confirm: Each customer sees only its own permitted records and metrics.
Incorrect Answers
This choice addresses a different case in the same task group: A service manager tracks monthly security-policy changes but has no record of who approved high-impact FortiSASE exceptions. The present situation is: A FortiAnalyzer report aggregates all tenant browsing events and is shared with individual MSSP customers. Its decisive action is: Create authorized tenant-scoped reports and verify reviewer permissions.
That proposal leaves the central dependency unresolved. The correction is: Create authorized tenant-scoped reports and verify reviewer permissions. The expected acceptance result is: Each customer sees only its own permitted records and metrics.
This alternative addresses the separate case “FortiAnalyzer stores branch SD-WAN logs but FortiSASE cloud events are absent from the security incident dashboard”. The focused remedy is: Configure supported FortiSASE log export and correlate it with FortiGate events. The deciding requirement here is “Create authorized tenant-scoped reports and verify reviewer permissions”.