Fortinet FCSS_SASE_AD-24 Exam Questions - Navigate Your Path to Success

Correct : A, B, C

To meet the requirements of implementing device posture checks for remote endpoints and ensuring that TCP traffic between the endpoints and protected servers is processed by FortiGate, the following three setups are necessary:

Configure ZTNA tags on FortiGate (Option A):

ZTNA (Zero Trust Network Access) tags are used to define access control policies based on the security posture of devices. By configuring ZTNA tags on FortiGate, administrators can enforce granular access controls, ensuring that only compliant devices can access protected resources.

Configure FortiGate as a zero trust network access (ZTNA) access proxy (Option B):

FortiGate can act as a ZTNA access proxy, which allows it to mediate and secure connections between remote endpoints and protected servers. This setup ensures that all TCP traffic passes through FortiGate, enabling inspection and enforcement of security policies.

Configure ZTNA servers and ZTNA policies on FortiGate (Option C):

To enable ZTNA functionality, administrators must define ZTNA servers (the protected resources) and create ZTNA policies on FortiGate. These policies determine how traffic is routed, inspected, and controlled based on device posture and user identity.

Here's why the other options are incorrect:

D . Configure private access policies on FortiSASE with ZTNA: While FortiSASE supports ZTNA, the requirement specifies that TCP traffic must be processed by FortiGate. Configuring private access policies on FortiSASE would route traffic through FortiSASE instead of FortiGate, which does not meet the stated requirements.

E . Sync ZTNA tags from FortiSASE to FortiGate: Synchronizing ZTNA tags is unnecessary in this scenario because the focus is on FortiGate processing the traffic. The tags can be directly configured on FortiGate without involving FortiSASE.

Fortinet FCSS FortiSASE Documentation - Zero Trust Network Access (ZTNA) Deployment

FortiGate Administration Guide - ZTNA Configuration

Correct : B

The FortiSASE inline-CASB (Cloud Access Security Broker) component is designed to provide real-time security and visibility by being placed directly in the traffic path between the endpoint and cloud applications . Inline-CASB inspects traffic as it flows to and from cloud applications, enabling enforcement of security policies, detection of threats, and prevention of unauthorized access. This approach ensures that all interactions with cloud applications are monitored and controlled in real time.

Here's why the other options are incorrect:

A . It provides visibility for unmanaged locations and devices: While inline-CASB enhances visibility, its primary function is to inspect and secure traffic in real time. Visibility for unmanaged locations and devices is typically achieved through other components like endpoint agents or API-based CASB.

C . It uses API to connect to the cloud applications: API-based CASB is a different approach that relies on APIs provided by cloud applications to monitor and manage data. Inline-CASB operates directly in the traffic flow rather than using APIs.

D . It detects data at rest: Detecting data at rest is typically handled by Data Loss Prevention (DLP) tools or API-based CASB solutions. Inline-CASB focuses on inspecting traffic in motion, not data stored in cloud applications.

Fortinet FCSS FortiSASE Documentation - Inline-CASB Overview

FortiSASE Administration Guide - Cloud Application Security