Question 740
A security analyst investigates this Fortinet environment: A remote staff member logs into the company identity provider successfully but FortiClient does not establish the FortiSASE tunnel. Before changing policy, which diagnostic observation should be collected first?
Explanation
Correct Answer
The first diagnostic step is to inspect FortiClient registration state, the SAML redirect response, group mapping, and tunnel authentication logs. The critical symptom is that a remote staff member logs into the company identity provider successfully but FortiClient does not establish the FortiSASE tunnel. This narrows the failing policy, inspection or management stage before an administrator changes unrelated settings. Once verified, the appropriate next action is to repair the supported SAML or tunnel enrollment prerequisite indicated by the failure evidence; jumping straight to that change without checking the stated evidence increases the chance of a misleading result.
Incorrect Answers
Separate device compliance state from user authentication and FortiSASE authorization logs. The alternative concerns separating device compliance state from user authentication and FortiSASE authorization logs, not inspecting FortiClient registration state, the SAML redirect response, group mapping, and tunnel authentication logs.
Inspect identity-group synchronization, tunnel session lifecycle, and effective policy match. This assesses identity-group synchronization, tunnel session lifecycle, and effective policy match; it does not determine the reported condition—a remote staff member logs into the company identity provider successfully but FortiClient does not establish the FortiSASE tunnel.
Check remote server reachability, directory group retrieval, user group mapping, and effective identity claims. The case-specific requirement is inspecting FortiClient registration state, the SAML redirect response, group mapping, and tunnel authentication logs, which that option does not establish.