FortiSASE Secure Private Access can integrate with existing FortiGate SD-WAN infrastructure to provide cloud-delivered security enforcement and connectivity to privately hosted enterprise applications.
Option C is correct because FortiSASE acts as a security enforcement point for traffic entering its cloud infrastructure. Administrators can apply security profiles and traffic policies before permitted sessions are forwarded toward private resources through the established SD-WAN connectivity.
Option D is correct because SD-WAN-integrated SPA provides network-layer connectivity to private applications, supporting both TCP-based and UDP-based protocols. This is valuable for enterprise applications that cannot operate through HTTP-only access proxies.
Option A is incorrect because the SD-WAN integration model does not require FortiClient to establish a direct ZTNA access-proxy tunnel to the on-premises FortiGate. Instead, FortiSASE security points of presence connect to the FortiGate SD-WAN hub through IPsec overlays.
Option B describes an endpoint-posture access-control capability, but posture evaluation is not inherently performed by the SD-WAN hub in this deployment method. FortiSASE and FortiClient can assess endpoint security conditions, while the SD-WAN hub primarily provides network connectivity and local security enforcement.
The principal advantages are protocol-flexible private application connectivity and centralized cloud security inspection, integrated with the existing SD-WAN architecture.
[References: FortiSASE 25 Enterprise Administrator Study Guide, pages 7–11, Fortinet Unified SASE and SPA; FortiSASE Secure Private Access Architecture Guide — SPA Using an Existing FortiGate SD-WAN Hub., ==========, ]
