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.

To configure a Secure Private Access (SPA) solution to share endpoint information between FortiSASE and a corporate FortiGate, you need to take the following steps:
* Add the FortiGate IP address in the secure private access configuration on FortiSASE:
* This step allows FortiSASE to recognize and establish a connection with the corporate FortiGate.
* Use the FortiClient EMS cloud connector on the corporate FortiGate to connect to FortiSASE:
* The EMS (Endpoint Management Server) cloud connector facilitates the integration between FortiClient endpoints and FortiSASE, enabling seamless sharing of endpoint information.
* Register FortiGate and FortiSASE under the same FortiCloud account:
* By registering both FortiGate and FortiSASE under the same FortiCloud account, you ensure centralized management and synchronization of configurations and policies.
References:
FortiOS 7.6 Administration Guide: Provides details on configuring Secure Private Access and integrating with FortiGate.
FortiSASE 23.2 Documentation: Explains how to set up and manage connections between FortiSASE and corporate FortiGate.

Explanation:
1. DLP Data Pattern
2. DLP Dictionary
3. DLP Sensor
4. DLP Profile
The FortiSASE Data Loss Prevention (DLP) framework follows a hierarchical object-oriented structure.
When creating a custom DLP rule using Regular Expressions (Regex), the administrator must build the components from the most granular level upward to the policy level.
* DLP Data Pattern: This is the first step where the actual Regex string is defined. The pattern specifies what specific data string (e.g., a specific credit card format or employee ID) the engine should look for.
* DLP Dictionary: Once the pattern is created, it must be added to a Dictionary. The dictionary acts as a container that groups one or more data patterns together for easier management.
* DLP Sensor: The dictionary is then linked to a DLP Sensor. Within the sensor, you define the "Rule" which specifies the dictionary to use and the action to take (such as block, log, or quarantine) when a match occurs.
* DLP Profile: Finally, the sensor is applied to a DLP Profile. This profile is the high-level object that is ultimately selected within a FortiSASE Security Policy to inspect traffic for sensitive data.

In a FortiSASE environment where always-on VPN is enforced, FortiClient typically establishes a full tunnel to a Security Point of Presence (PoP). By default, a full-tunnel configuration instructs the endpoint to send all traffic-including traffic destined for the local network-through the secure tunnel to FortiSASE for inspection.
* The Local Access Challenge: When a remote user is at home or in a satellite office, they often need to access local resources such as printers, NAS devices, or other computers on the same Layer 2 (L2) broadcast domain. In a standard full-tunnel setup, these local resources become unreachable because the routing table on the endpoint prioritizes the VPN interface for all non-local-gateway traffic.
* Allow Local LAN Access: To resolve this while maintaining the security of the " Always-On " requirement, FortiSASE administrators can enable the Allow Local LAN Access feature within the Endpoint Profile .
* Configuration Logic: This setting modifies the FortiClient configuration (often via an XML update pushed from the FortiSASE EMS) to include an exemption for the endpoint ' s locally connected subnet. Specifically, it ensures that traffic destined for the local L2 network does not enter the IPsec or SSL-VPN tunnel, allowing the user to interact with local peripherals while all other internet and corporate-bound traffic remains secured by FortiSASE.
* Incorrect Options: * Option B and C: Sandbox and Anti-Virus protections are security features for threat detection and do not influence the routing of local network traffic.
* Option D: Network Lockdown actually does the opposite; it restricts network access until a VPN connection is established and typically blocks local LAN access unless specific exemptions are made, making it the incorrect choice for enabling access to local resources.