Question 190
The deployment team is preparing a sign-off for: A newly hired employee receives a FortiClient installation link but no onboarding code and cannot register the endpoint with FortiSASE. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that installing FortiClient alone does not always establish enrollment with the correct FortiSASE service. The case concerns a newly hired employee receives a FortiClient installation link but no onboarding code and cannot register the endpoint with FortiSASE. The safer path is to inspect the invitation email, installer type, tenant invitation code, and assigned endpoint profile and then, after verification, to send a valid invitation or use the approved preconfigured installer with correct FortiSASE code. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
An LDAP login that succeeds may still lack the group information required for fine-grained policy. The check concerns an LDAP login that succeeds may still lack the group information required for fine-grained policy, not confirming that installing FortiClient alone does not always establish enrollment with the correct FortiSASE service.
Invitation codes are provisioning material and should not be treated as interchangeable across tenants. This assesses invitation codes are provisioning material and should not be treated as interchangeable across tenants; it does not determine the reported condition—a newly hired employee receives a FortiClient installation link but no onboarding code and cannot register the endpoint with FortiSASE.
Endpoint compliance alone is not sufficient evidence of user authorization to every resource. The case-specific requirement is confirming that installing FortiClient alone does not always establish enrollment with the correct FortiSASE service, which that option does not establish.