Fortinet Network Security Expert FCP_FCT_AD-7.4 Exam Questions and Answers PDF

Based on the FortiGate Security Fabric settings shown in the exhibits, to successfully quarantine an endpoint when it is detected as a compromised host (IOC), the following step is required:

Enable Remote HTTPS Access to EMS:This setting allows FortiGate to communicate securely with FortiClient EMS over HTTPS. Remote HTTPS access is essential for the quarantine functionality to operate correctly, enabling the EMS server to receive and act upon the quarantine commands from FortiGate.

Therefore, the administrator must enable remote HTTPS access to EMS to allow the quarantine process to function properly.

References

FortiGate Infrastructure 7.2 Study Guide, Security Fabric and Integration with EMS Sections

Fortinet Documentation on Enabling Remote HTTPS Access to FortiClient EMS

Observation of Web Filter Exclusions:

The exhibit shows a web filter exclusion for "*.facebook.com" with the action set to "Allow."

Evaluating Actions:

This configuration means that FortiClient will allow access to Facebook and its subdomains.

Conclusion:

When users try to access " ," FortiClient will allow the access based on the web filter exclusion settings.

Understanding the Automation Process:

In the Security Fabric, automation processes can include actions such as quarantining an endpoint after an IOC (Indicator of Compromise) detection.

Evaluating Responsibilities:

FortiClient EMS plays a crucial role in endpoint management and can send notifications to quarantine endpoints.

Conclusion:

The correct security fabric component that sends a notification to quarantine an endpoint after IOC detection is FortiClient EMS.

Based on theFortiClient EMS Administrator Study GuideregardingWeb Filtertroubleshooting and the specific log entries provided in the exhibit, the reason the user cannot access the website is due to connectivity issues with FortiGuard.

1. Analysis of the FortiClient Logs:

The Error Message:The logs show multiple [ERROR] entries stating: rating_db:97 Category query failure: failed to UrlRequestSendReceive.

Root Cause Identity:The log explicitly describes the failure: receiveResponse error: FortiGuard server down, task dropped, https bbc.com.

Resulting Action:Because the endpoint could not receive a rating from the FortiGuard servers, the Web Filter module recorded rating: -1 and applied the action WF_ACTION_BLOCK.

2. Why Option C is Correct:

FortiGuard Dependency:FortiClient’s Web Filter module relies on real-time queries to FortiGuard distribution servers to categorize URLs. If the endpoint is behind a firewall blocking FortiGuard ports (typically UDP 53 or 8888, or HTTPS 443) or has no internet path to these servers, it cannot categorize the site.

Fail-Safe Behavior:In many FortiClient configurations, if a rating cannot be obtained (Category query failure), the default security posture is to block the request to ensure no potentially malicious or unrated "Unknown" sites are accessed. The logs confirm this by showing the "FortiGuard server down" message immediately followed by the block action.

3. Why Other Options are Incorrect:

A. The URL is blocked by the web filter endpoint profile:If it were a standard profile block, the log would show a specificCategory ID(e.g., Category 52 for News and Media) being blocked by policy. Instead, it shows arating failure (-1).

B. The endpoint cannot resolve the URL FQDN:The logs show the process correctly identifies host bbc.com. If DNS had failed, the proxy wouldn't even reach the stage of attempting a FortiGuard category query for that specific URL.

D. The application firewall is blocking Google Chrome:While the log mentions /opt/google/chrome/chrome, the error is generated by the rating_db and proxy components of the Web Filter, not the Application Firewall module.