Question 70
A security analyst investigates this Fortinet environment: A FortiGate secure edge reaches the FortiSASE PoP but untagged local guest traffic should not use the same protected path as corporate traffic. Before changing policy, which diagnostic observation should be collected first?
Explanation
Correct Answer
The first diagnostic step is to inspect LAN VLAN membership, site-based edge forwarding policy, and service profiles. The critical symptom is that a FortiGate secure edge reaches the FortiSASE PoP but untagged local guest traffic should not use the same protected path as corporate traffic. This narrows the failing policy, inspection or management stage before an administrator changes unrelated settings. Once verified, the appropriate next action is to segment authorized site traffic and apply suitable FortiGate-to-FortiSASE forwarding rules; jumping straight to that change without checking the stated evidence increases the chance of a misleading result.
Incorrect Answers
Inspect private prefix steering, IPsec overlay policy, and the intended SPA path from the PoP. The check concerns private prefix steering, IPsec overlay policy, and the intended SPA path from the PoP, not inspecting LAN VLAN membership, site-based edge forwarding policy, and service profiles.
Check supported hub onboarding, authorization state, device registration, and service prerequisites. This assesses supported hub onboarding, authorization state, device registration, and service prerequisites; it does not determine the reported condition—a FortiGate secure edge reaches the FortiSASE PoP but untagged local guest traffic should not use the same protected path as corporate traffic.
Check platform compatibility, minimum FortiOS version, and secure-edge subscription entitlements. The case-specific requirement is inspecting LAN VLAN membership, site-based edge forwarding policy, and service profiles, which that option does not establish.