Question 780
Which remediation is best aligned with this environment: An MSSP integrates multiple customer FortiGates with FortiSASE and merges log records without tenant labels?
Explanation
Correct Answer
The corrective step is: Preserve tenant and device identity during FortiSASE and FortiAnalyzer log forwarding. The case turns on this distinction: Cross-product telemetry requires identifiers and separation for tenant attribution. Afterward, confirm: Investigators can identify the correct customer and branch for a sample event.
Incorrect Answers
This is a nearby Fortinet issue, not the current one. It deals with a private application is reachable through a regional FortiGate while all internet browsing is intended to leave through FortiSASE. The correct answer to the stated case is: Preserve tenant and device identity during FortiSASE and FortiAnalyzer log forwarding.
The related but distinct situation is “A logistics firm secures individual users through FortiClient but its warehouse devices cannot run an endpoint agent”. The change needed here is: Deploy a supported FortiGate or edge on-ramp to cloud inspection for warehouse traffic. For the stated problem, “Preserve tenant and device identity during FortiSASE and FortiAnalyzer log forwarding” addresses the central condition.
This shortcut is attractive but misses the underlying condition: Cross-product telemetry requires identifiers and separation for tenant attribution. The case requires the targeted remedy: Preserve tenant and device identity during FortiSASE and FortiAnalyzer log forwarding.