The correct answer is D . The FortiSASE study guide explains that SPA allows a FortiSASE POP to act as a spoke and connect to a FortiGate hub. It states that you can use FortiSASE SPA so that a POP connects to either a standalone hub using IPsec or to an existing Fortinet SD-WAN deployment . It also states that the BGP protocol is established through IPsec links for dynamic route exchange, which gives FortiSASE remote users access to private resources. For hub deployments running FortiOS 7.4.5 or later, the guide explains that an easy configuration key can simplify SPA setup on FortiSASE by automatically populating key fields in the FortiGate hub configuration.

The wrong options contradict the guide. Option A is false because FortiSASE does not apply SNAT for remote VPN user and edge device traffic destined for SPA hubs, and FortiSASE spokes support IKEv2, not IKEv1. Option B confuses agentless ZTNA with SD-WAN private access. Option C is wrong because SPA uses IPsec and BGP, and the easy configuration key is for SPA hub setup, not for securing general web traffic.

The correct answers are C and D . FortiSASE SPA supports two private access models. The first model is ZTNA access proxy , where the endpoint connects directly to the FortiGate ZTNA access proxy. The study guide states that ZTNA provides a direct connection to protected resources without establishing a persistent VPN tunnel and that the ZTNA access proxy use case offers the direct shortest path to private resources. This validates option C and invalidates option B, because ZTNA access proxy traffic does not first traverse a FortiSASE POP.

The second model is SD-WAN private access, where FortiSASE acts as a spoke. The guide explains that FortiSASE SPA enables a FortiSASE POP to connect to a FortiGate hub or an existing Fortinet SD-WAN deployment using IPsec and BGP. In that design, endpoint traffic is steered to the FortiSASE POP, and the POP forwards traffic through the SPA tunnel to the FortiGate hub. That validates option D and makes option A incorrect.

The Digital Experience Monitor (DEM) feature in FortiSASE is a specialized monitoring tool integrated into the SASE cloud to ensure optimal application performance and user satisfaction. 2

Purpose and Visibility : DEM is designed to provide end-to-end network visibility by monitoring the health and performance of the connections between the global FortiSASE security Points of Presence (PoPs) and specific SaaS applications (such as Microsoft 365, WebEx, or Dropbox).

Performance Metrics : It identifies and helps troubleshoot issues related to latency, jitter, and packet loss . By leveraging vantage points within the SASE infrastructure, administrators can determine if a performance bottleneck resides within the local network, the SASE backbone, or the SaaS provider ' s environment.

Integration : This feature is often powered by FortiMonitor , allowing for synthetic transaction monitoring (STM) to simulate user interactions and proactively spot performance issues before they impact the hybrid workforce.

Operational Efficiency : By providing comprehensive insights across users and PoPs, DEM reduces the time required to resolve " slowness " complaints, which are common in remote work scenarios.

Comparison of Other Features:

Option A : While FortiSASE monitors PoP health, DEM ' s primary value is the end-to-end path to the application.

Option B : Compliance checks are a function of Endpoint Profiles and ZTNA tagging rules, not the monitoring dashboard.

Option D : Vulnerability management is handled by the Vulnerability Scan feature within the managed FortiClient settings.

FortiSASE brings the following advantages to businesses with multiple branch offices:

Centralized Management for Simplified Administration:

FortiSASE provides a centralized management platform that allows administrators to manage security policies, configurations, and monitoring from a single interface.

This simplifies the administration and reduces the complexity of managing multiple branch offices.

Eliminates the Need for On-Premises Firewalls:

FortiSASE enables secure access to the internet and cloud applications without requiring dedicated on-premises firewalls at each branch office.

This reduces hardware costs and simplifies network architecture, as security functions are handled by the cloud-based FortiSASE solution.

To meet the requirement of inspecting all endpoint internet traffic on FortiSASE while excluding Google Maps traffic from the FortiSASE VPN tunnel and redirecting it to the endpoint ' s physical interface, you should configure split tunneling. Split tunneling allows specific traffic to bypass the VPN tunnel and be routed directly through the endpoint ' s local interface.

Split Tunneling Configuration:

Split tunneling enables selective traffic to be routed outside the VPN tunnel.

By configuring the Google Maps Fully Qualified Domain Name (FQDN) as a split tunneling destination, you ensure that traffic to Google Maps bypasses the VPN tunnel and uses the endpoint ' s local interface instead.

Implementation Steps:

Access the FortiSASE endpoint profile configuration.

Add the Google Maps FQDN to the split tunneling destinations list.

This configuration directs traffic intended for Google Maps to bypass the VPN tunnel and be routed directly through the endpoint ' s physical network interface.

Zero Trust Network Access (ZTNA) is the FortiSASE feature that ensures least-privileged user access to all applications. ZTNA operates on the principle of " never trust, always verify, " providing secure access based on the identity of users and devices, regardless of their location.

Zero Trust Network Access (ZTNA):

ZTNA ensures that only authenticated and authorized users and devices can access applications.

It applies the principle of least privilege by granting access only to the resources required by the user, minimizing the potential for unauthorized access.

Implementation:

ZTNA continuously verifies user and device trustworthiness and enforces granular access control policies.

This approach enhances security by reducing the attack surface and limiting lateral movement within the network.

There are two deployment methods used to connect a FortiExtender as a FortiSASE LAN extension:

Connect FortiExtender to FortiSASE using FortiZTP:

FortiZero Touch Provisioning (FortiZTP) simplifies the deployment process by allowing FortiExtender to automatically connect and configure itself with FortiSASE.

This method requires minimal manual configuration, making it efficient for large-scale deployments.

Enter the FortiSASE domain name in the FortiExtender GUI as a static discovery server:

Manually configuring the FortiSASE domain name in the FortiExtender GUI allows the extender to discover and connect to the FortiSASE infrastructure.

This static discovery method ensures that FortiExtender can establish a connection with FortiSASE using the provided domain name.

FortiSASE uses the following components for application control to act as an inline-CASB (Cloud Access Security Broker):

SSL Deep Inspection:

SSL deep inspection is essential for decrypting and inspecting HTTPS traffic to identify and control applications and data transfers within encrypted traffic.

This allows FortiSASE to enforce security policies on SSL/TLS encrypted traffic, providing visibility and control over cloud applications.

Web Filter with Inline-CASB:

The web filter component integrates with inline-CASB to monitor and control access to cloud applications based on predefined security policies.

This combination provides granular control over cloud application usage, ensuring compliance with security policies and preventing unauthorized data transfers.

The integration of FortiGuard SOCaaS with FortiSASE significantly strengthens an organization ' s security posture by offloading complex security operations to Fortinet ' s expert analysts. 4

Continuous Threat Monitoring (B): FortiGuard SOCaaS provides 24x7x365 threat monitoring for all endpoints connected to the FortiSASE environment. This service eliminates the need for organizations to hire and maintain their own round-the-clock security operations staff while ensuring that threats are detected and verified in as little as 15 minutes.

Centralized Visibility (C): By forwarding FortiSASE logs to the SOCaaS cloud, administrators gain centralized visibility of all security events through a single, user-friendly portal. This portal allows security teams to track threats, review expert-led incident escalations, and communicate directly with Fortinet SOC analysts to streamline the incident response process.

Operational Efficiency: The integration uses AI-driven alert triage and automated correlation to distill data from the Fortinet Security Fabric, focusing on legitimate threats and reducing the alert fatigue often experienced by internal IT teams.

The reason for the ping failures is due to the quick mode selectors restricting the subnet. Quick mode selectors define the IP ranges and protocols that are allowed through the VPN tunnel, and if they are not configured correctly, traffic to certain subnets can be blocked.

Quick Mode Selectors:

Quick mode selectors specify the source and destination subnets that are allowed to communicate through the VPN tunnel.

If the selectors do not include the subnet of the webserver (192.168.10.0/24), then the traffic will be restricted, and the ping will fail.

Diagnostic Output:

The diagnostic output shows the VPN configuration details, but it is important to check the quick mode selectors to ensure that the necessary subnets are included.

If the quick mode selectors are too restrictive, they will prevent traffic to and from the specified subnets.

Configuration Check:

Verify the quick mode selectors on both the FortiSASE and FortiGate hub to ensure they match and include the subnet of the webserver.

Adjust the selectors to allow the necessary subnets for successful communication.