Question 650
The deployment team is preparing a sign-off for: An operator enables a new FortiSASE web security profile for one branch but affects remote users company-wide due to global scope. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that a cloud console's top-level configuration view may represent every tenant user rather than one branch. The case concerns an operator enables a new FortiSASE web security profile for one branch but affects remote users company-wide due to global scope. The safer path is to review policy assignment scope, source populations, and inherited default controls and then, after verification, to restrict the change to the correct site or group and preserve global mandatory protections. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
A successful login does not demonstrate that group membership has propagated into policy evaluation. The check concerns a successful login does not demonstrate that group membership has propagated into policy evaluation, not confirming that a cloud console's top-level configuration view may represent every tenant user rather than one branch.
Saving a policy editor form does not always establish that the active enforcement path changed. This assesses saving a policy editor form does not always establish that the active enforcement path changed; it does not determine the reported condition—an operator enables a new FortiSASE web security profile for one branch but affects remote users company-wide due to global scope.
Creating a FortiCloud account alone does not activate every purchased cloud-security service. The case-specific requirement is confirming that a cloud console's top-level configuration view may represent every tenant user rather than one branch, which that option does not establish.