Question 270
During follow-up testing at a corporate headquarters, the original fault was: An admin selects a PoP for remote users based only on geographic distance even though upstream ISP routing gives that location poor responsiveness. Which measured result demonstrates recovery rather than an unrelated improvement?
Explanation
Correct Answer
Test users connect through a reachable PoP with response measurements meeting the approved target. This evidence directly tests the intended corrective action: Evaluate actual user-to-PoP latency and supported service-selection options before final assignment. It confirms the failure mechanism—Geographical proximity does not prove low operational round-trip latency.—has been addressed in the actual affected flow.
Incorrect Answers
Migrated test users retain permitted access and previous policy is recoverable if needed. This would verify resolution of a different case: An operations team prepares to migrate an existing group to a new FortiSASE subscription while leaving policy ownership and rollback undefined. It does not show that the reported issue was fixed or that its intended action—Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.—worked.
Named admins sign in with appropriate privilege while unauthorized use of the shared credential is blocked. This would verify resolution of a different case: A newly deployed FortiSASE tenant trusts a broad default administrative account even after named administrators receive individual credentials. It does not show that the reported issue was fixed or that its intended action—Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.—worked.
Helpdesk accounts can inspect authorized status while policy edits require designated administrators. This would verify resolution of a different case: An administrator grants every helpdesk analyst full policy-change rights because some staff need to view remote user connection status. It does not show that the reported issue was fixed or that its intended action—Evaluate actual user-to-PoP latency and supported service-selection options before final assignment.—worked.