Free Access to Fortinet.NSE5_FCT-7.0.v2024-08-20.q48 with Valid Practice Test (Page 8)

Question 31

Which component or device shares ZTNA tag information through Security Fabric integration?

A.FortiGate
B.FortiGate Access Proxy
C.FortiClient

Correct Answer: A

Explanation
FortiClient EMS is the component that shares ZTNA tag information through Security Fabric integration.
ZTNA tags are synchronized from FortiClient EMS as inputs for the FortiGate application gateway. They can be used in ZTNA policies as security posture checks to ensure certain security criteria are met. FortiClient EMS can share ZTNA tags across multiple devices in the Fabric, such as FortiGate, FortiManager, and FortiAnalyzer. FortiClient EMS can also share ZTNA tags across multiple VDOMs on the same FortiGate device. FortiClient EMS can be configured to control the ZTNA tag sharing behavior in the Fabric Devices settings1.
FortiGate is the device that enforces ZTNA policies using ZTNA tags. FortiGate can receive ZTNA tags from FortiClient EMS via Fabric Connector. FortiGate can also publish ZTNA services through the ZTNA portal, which allows users to access applications without installing FortiClient. FortiGate can also provide ZTNA inline CASB for SaaS application access control2.
FortiGate Access Proxy is a feature that enables FortiGate to act as a proxy for ZTNA traffic. FortiGate Access Proxy can be deployed in front of the application servers to provide ZTNA protection. FortiGate Access Proxy can also be deployed behind the application servers to provide ZTNA visibility. FortiGate Access Proxy can use ZTNA tags to identify and authenticate users and devices2.
FortiClient is the endpoint software that connects to ZTNA services. FortiClient can register ZTNA tags with FortiClient EMS based on the endpoint security posture. FortiClient can also use ZTNA tags to access ZTNA services published by FortiGate. FortiClient can also use ZTNA tags to access SaaS applications with ZTNA inline CASB2.
References :=
Technical Tip: Behavior of ZTNA Tags shared across multiple vdoms or multiple FortiGate firewalls in the Security Fabric connected to the same FortiClient EMS Server Synchronizing FortiClient ZTNA tags Zero Trust Network Access (ZTNA) to Control Application Access

Question 32

Which two benefits are benefits of using multi-tenancy mode on FortiClient EMS? (Choose two.)

A.The fabric connector must use an IP address to connect to FortiClient EMS
B.It provides granular access and segmentation.
C.Licenses are shared among sites.
D.Separate host servers manage each site.

Question 33

Why does FortiGate need the root CA certificate of FortiClient EMS?

A.To trust certificates issued by FortiClient EMS
B.To update FortiClient client certificates
C.To revoke FortiClient client certificates
D.To sign FortiClient CSR requests

Question 34

Refer to the exhibits.

Based on the FortiGate Security Fabric settings shown in the exhibits, what must an administrator do on the EMS server to successfully quarantine an endpoint. when it is detected as a compromised host (loC)?

A.The administrator must enable SSH access to EMS.
B.The administrator must enable remote HTTPS access to EMS.
C.The administrator must enable FQDN on EMS.
D.The administrator must authorize FortiGate on FortiAnalyzer.

Question 35

Refer to the exhibit.

Based on the logs shown in the exhibit, why did FortiClient EMS fail to install FortiClient on the endpoint?

A.The FortiClient antivirus service is not running
B.The Windows installer service is not running
C.The task scheduler service is not running.
D.The remote registry service is not running

Question 31

Question 32

Question 33

Question 34

Question 35

Download PDF File