Question 630
Following remediation at a regional data center, engineers revisit: FortiClient is installed but its VPN connection uses a direct on-premises FortiGate tunnel instead of the intended FortiSASE service. Which observation would BEST prove the specific issue is resolved?
Explanation
Correct Answer
Connection status shows the FortiSASE service and security traffic enters the expected PoP. This evidence directly tests the intended corrective action: Deploy the correct approved FortiSASE connection profile and remove the obsolete client target. It confirms the failure mechanism—Installing FortiClient does not guarantee it targets the correct security service.—has been addressed in the actual affected flow.
Incorrect Answers
Managed clients validate legitimate inspection certificates without unsafe click-through exceptions. This would verify resolution of a different case: A site lets users bypass required certificate trust warnings by manually accepting an unexpected FortiSASE proxy certificate on every device. It does not show that the reported issue was fixed or that its intended action—Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.—worked.
A test user's RADIUS request succeeds with expected acceptance and group behavior. This would verify resolution of a different case: A FortiSASE tenant uses RADIUS for user authentication but the RADIUS shared secret was changed on FortiAuthenticator only. It does not show that the reported issue was fixed or that its intended action—Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.—worked.
A user in the previously omitted OU is found and permitted according to group rules. This would verify resolution of a different case: A remote user enters a correct password but FortiSASE authentication against a central LDAP directory fails because the configured base DN excludes that organizational unit. It does not show that the reported issue was fixed or that its intended action—Deploy the correct approved FortiSASE connection profile and remove the obsolete client target.—worked.