Question 170
A security analyst investigates this Fortinet environment: A firm uses an LDAP identity provider for remote FortiSASE access but group-specific rules do not recognize a newly added department. Before changing policy, which diagnostic observation should be collected first?
Explanation
Correct Answer
The first diagnostic step is to check remote server reachability, directory group retrieval, user group mapping, and effective identity claims. The critical symptom is that a firm uses an LDAP identity provider for remote FortiSASE access but group-specific rules do not recognize a newly added department. This narrows the failing policy, inspection or management stage before an administrator changes unrelated settings. Once verified, the appropriate next action is to correct the supported LDAP integration or remote group assignment required for the department; jumping straight to that change without checking the stated evidence increases the chance of a misleading result.
Incorrect Answers
Inspect FortiClient registration state, the SAML redirect response, group mapping, and tunnel authentication logs. The check concerns fortiClient registration state, the SAML redirect response, group mapping, and tunnel authentication logs, not checking remote server reachability, directory group retrieval, user group mapping, and effective identity claims.
Review endpoint group membership, intended profile assignment, and latest applied configuration state. This assesses endpoint group membership, intended profile assignment, and latest applied configuration state; it does not determine the reported condition—a firm uses an LDAP identity provider for remote FortiSASE access but group-specific rules do not recognize a newly added department.
Inspect identity-group synchronization, tunnel session lifecycle, and effective policy match. The case-specific requirement is checking remote server reachability, directory group retrieval, user group mapping, and effective identity claims, which that option does not establish.