FCSS_SASE_AD-25 Sample Questions Answers

Configure a network lockdown policy on the endpoint profiles.

Configure a geography address object as the source for a deny policy.

Configure geofencing to restrict access from the required countries.

Configure source IP anchoring to restrict access from the specified countries.

The logs are deleted from FortiSASE.

The logs are indexed and can be stored in a SQL database.

The logs are backed up on FortiCloud.

The logs are compressed and archived.

By tokenization in log data

By masking log data

By compressing log data

By hashing log data

It offers data center redundancy.

The on-premises FortiGate performs a device posture check.

It is ideal for latency-sensitive applications.

It supports both agentless ZTNA and agent-based ZTNA.

A private access policy has denied the traffic because of failed compliance

The hub is not advertising the required routes.

The hub firewall policy does not include the FortiClient address range.

The server subnet BGP route was not received on FortiSASE.

security posture tags

application inventory

user verification

device identification

a direct access proxy tunnel from FortiClient to the on-premises FortiGate

ZTNA posture check performed by the hub FortiGate

support of both TCP and UDP applications

inline security inspection by FortiSASE

Only endpoints assigned a profile for sandbox detection will be processed by the sandbox feature.

FortiClient quarantines only infected files that FortiSandbox detects as medium level.

All files executed on a USB drive will be sent to FortiSandbox for analysis.

All files will be sent to a on-premises FortiSandbox for inspection.

cloud access security broker (CASB)

SD-WAN

zero trust network access (ZTNA)

thin edge

SSO users can be imported into FortiSASE and added to user groups.

SSO is recommended only for agent-based deployments.

SSO overrides any other previously configured user authentication.

SSO identity providers can be integrated using public and private access types.

FortiSASE runs a ping from the endpoint to calculate the TTL to the SaaS application.

FortiSASE runs SNMP traps to the endpoint using the DEM agent to verify the SaaS application health status.

FortiSASE runs a netstat from the endpoint to the SaaS application to see if ports are open.

FortiSASE runs a trace job on the endpoint using the DEM agent to the Software-as-a-Service (SaaS) application.

FortiSASE connector configured on FortiManager.

FortiSASE central management entitlement applied to FortiManager.

The FortiManager IP address in the FortiSASE central management configuration.

FortiManager and FortiSASE registered under the same FortiCloud account.