Question 920
A distributed security deployment has this problem: A SASE user enrollment guide provides the tenant URL but omits the necessary organization and identity prerequisites for third-party contractors. Which explanation is the best starting point?
Explanation
Correct Answer
The relevant distinction is this: Provisioning must combine tenant access, identity scope and supported client or proxy setup. Change the affected component by choosing to precreate the approved contractor group and validate the complete onboarding workflow. Evidence of resolution: A new contractor reaches only their authorized internet services on first enrollment.
Incorrect Answers
This choice addresses a different case in the same task group: An agentless SPA service uses an HTTPS access proxy but clients cannot complete TLS validation because the server presents the wrong certificate. The present situation is: A SASE user enrollment guide provides the tenant URL but omits the necessary organization and identity prerequisites for third-party contractors. Its decisive diagnosis is: Provisioning must combine tenant access, identity scope and supported client or proxy setup.
It would be relevant when a customer configures an agent-based SIA tenant but does not assign any endpoint profile to a new user group, whereas the current case requires: Provisioning must combine tenant access, identity scope and supported client or proxy setup. The actual corrective step is: Precreate the approved contractor group and validate the complete onboarding workflow.
This alternative addresses the separate case “Users receive a proxy auto-config file but browser traffic bypasses FortiSASE because the PAC file is never applied”. This case illustrates that a PAC file must be deployed and selected by the browsing environment to affect proxy decisions. The deciding requirement here is “Provisioning must combine tenant access, identity scope and supported client or proxy setup”.