Question 570
An operations review at a service-provider edge has corrected: A team deploys an agentless SWG configuration but omits browser or system proxy settings, causing traffic to connect directly to Internet sites. Which observation specifically confirms success?
Explanation
Correct Answer
Test web access appears in FortiSASE SWG logs and nonproxy direct browsing is appropriately restricted. This evidence directly tests the intended corrective action: Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers. It confirms the failure mechanism—A proxy account alone does not intercept browser traffic without the client directing sessions to it.—has been addressed in the actual affected flow.
Incorrect Answers
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—Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.—worked.
A browser-only test reaches approved web destinations through the intended proxy without a managed VPN agent. This would verify resolution of a different case: A company plans browser-only secure web gateway use for contractors but distributes an agent-based full-tunnel guide requiring managed endpoint enrollment. It does not show that the reported issue was fixed or that its intended action—Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.—worked.
SAML assertions signed by the new key authenticate for pilot users and no unexpected outages occur. This would verify resolution of a different case: An IdP migration removes a FortiSASE SAML signing certificate before the replacement has been accepted by the service provider. It does not show that the reported issue was fixed or that its intended action—Install the approved PAC/manual proxy settings or supported agentless onboarding method for intended browsers.—worked.