Question 410
An operations review at a manufacturing plant has corrected: A corporate FortiClient enrollment profile specifies an obsolete FortiSASE service endpoint after a regional service migration, and new clients cannot connect. Which observation specifically confirms success?
Explanation
Correct Answer
A clean installation enrolls to the correct tenant and establishes a protected connection. This evidence directly tests the intended corrective action: Update the approved FortiClient registration or connection profile to the current service endpoint. It confirms the failure mechanism—Old registration endpoints can block otherwise valid credentials and client software.—has been addressed in the actual affected flow.
Incorrect Answers
Nonweb and web test cases show explicitly understood protection differences between agent and proxy cohorts. This would verify resolution of a different case: Remote users experience two different security postures because some are agent-based and others use browser-only SWG; an operator assumes both modes inspect nonweb traffic identically. It does not show that the reported issue was fixed or that its intended action—Update the approved FortiClient registration or connection profile to the current service endpoint.—worked.
Members of separate test groups match their intended access restrictions after SSO. This would verify resolution of a different case: A FortiSASE SAML integration accepts users but places everyone into a default policy because role and group assertions are missing from the issued claim. It does not show that the reported issue was fixed or that its intended action—Update the approved FortiClient registration or connection profile to the current service endpoint.—worked.
A deprovisioned test account no longer matches the privileged policy while active users retain access. This would verify resolution of a different case: A remote worker successfully authenticates to FortiSASE but a stale identity group cache keeps applying a former privileged access policy. It does not show that the reported issue was fixed or that its intended action—Update the approved FortiClient registration or connection profile to the current service endpoint.—worked.