Question 570
The deployment team is preparing a sign-off for: A remote staff member logs into the company identity provider successfully but FortiClient does not establish the FortiSASE tunnel. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that successful identity-provider authentication is not proof that tunnel provisioning completed. The case concerns a remote staff member logs into the company identity provider successfully but FortiClient does not establish the FortiSASE tunnel. The safer path is to inspect FortiClient registration state, the SAML redirect response, group mapping, and tunnel authentication logs and then, after verification, to repair the supported SAML or tunnel enrollment prerequisite indicated by the failure evidence. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
Endpoint compliance alone is not sufficient evidence of user authorization to every resource. The check concerns endpoint compliance alone is not sufficient evidence of user authorization to every resource, not confirming that successful identity-provider authentication is not proof that tunnel provisioning completed.
An existing session may not instantly reflect every directory group change without reevaluation. This assesses an existing session may not instantly reflect every directory group change without reevaluation; 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.
An LDAP login that succeeds may still lack the group information required for fine-grained policy. The case-specific requirement is confirming that successful identity-provider authentication is not proof that tunnel provisioning completed, which that option does not establish.