Question 750
The deployment team is preparing a sign-off for: A branch FortiGate is configured as a secure edge for site-based users, but the office devices are mistakenly required to install individual FortiClient agents. Which limitation or risk should it explicitly consider before approval?
Explanation
Correct Answer
The most relevant caution is that agentless site-based edge and per-endpoint FortiClient enrollment are different deployment models. The case concerns a branch FortiGate is configured as a secure edge for site-based users, but the office devices are mistakenly required to install individual FortiClient agents. The safer path is to review the chosen FortiGate secure-edge architecture, LAN gateway role, and supported service entitlement and then, after verification, to implement the approved site-based secure-edge connection and route LAN traffic through the FortiGate. This is the closest caution because it addresses the failure mechanism instead of a generic issue from another security workflow.
Incorrect Answers
An ordinary FortiGate SD-WAN license should not be presumed sufficient for every secure-edge mode. The check concerns an ordinary FortiGate SD-WAN license should not be presumed sufficient for every secure-edge mode, not confirming that agentless site-based edge and per-endpoint FortiClient enrollment are different deployment models.
Drawing a backup hub in the architecture is not proof that route failover is functional. This assesses drawing a backup hub in the architecture is not proof that route failover is functional; it does not determine the reported condition—a branch FortiGate is configured as a secure edge for site-based users, but the office devices are mistakenly required to install individual FortiClient.
Site-based SASE connectivity should not be treated as automatic authorization for every LAN device. The case-specific requirement is confirming that agentless site-based edge and per-endpoint FortiClient enrollment are different deployment models, which that option does not establish.