Question 50
At a financial services branch, a test team is validating a change after this incident: An administrator grants every helpdesk analyst full policy-change rights because some staff need to view remote user connection status. What evidence most directly verifies the intended outcome?
Explanation
Correct Answer
Helpdesk accounts can inspect authorized status while policy edits require designated administrators. This evidence directly tests the intended corrective action: Use scoped role-based access privileges that allow monitoring without unrestricted security configuration changes. It confirms the failure mechanism—Administrative viewing and policy modification should not require the same privileges.—has been addressed in the actual affected flow.
Incorrect Answers
Pilot users retain required business access and the security categories enforce the intended controls. This would verify resolution of a different case: An operator applies a new global URL Filtering profile during business hours without a pilot, interrupting legitimate applications across the tenant. It does not show that the reported issue was fixed or that its intended action—Use scoped role-based access privileges that allow monitoring without unrestricted security configuration changes.—worked.
A compliance review confirms the chosen service region and processing arrangements meet approved data-location obligations. This would verify resolution of a different case: An enterprise with a strict data-residency requirement selects a FortiSASE region solely for lower latency without assessing where relevant security logs and data are processed. It does not show that the reported issue was fixed or that its intended action—Use scoped role-based access privileges that allow monitoring without unrestricted security configuration changes.—worked.
The active service policy revision reflects the approved change and generates expected events. This would verify resolution of a different case: A security change is saved in FortiSASE management but not deployed or activated through the required service workflow, so remote users still see old behavior. It does not show that the reported issue was fixed or that its intended action—Use scoped role-based access privileges that allow monitoring without unrestricted security configuration changes.—worked.