Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam FCP_FCT_AD-7.2 Topic 4 Question 22 Discussion

Actual exam question for Fortinet's FCP_FCT_AD-7.2 exam
Question #: 22
Topic #: 4
[All FCP_FCT_AD-7.2 Questions]

Refer to the exhibit.

Based on the settings shown in the exhibit, which two actions must the administrator take to make the endpoint compliant? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: C

Requirement Analysis:

The administrator needs to maintain a software vulnerability scan on endpoints without showing the feature on FortiClient.

Evaluating Options:

Disabling the feature in the deployment package or endpoint profile would remove the functionality entirely, which is not desired.

Using the default endpoint profile may not meet the specific requirement of hiding the feature.

Clicking the hide icon on the vulnerability scan profile assigned to the endpoint will keep the feature active but hidden from the user's view.

Conclusion:

The correct action is to click the hide icon on the vulnerability scan profile assigned to the endpoint (C).


FortiClient EMS feature configuration and management documentation from the study guides.

Contribute your Thoughts:

Olene
2 days ago
D) Patching applications with high or above vulnerability seems like the obvious choice here. I'm pretty sure that's the key to making the endpoint compliant.
upvoted 0 times
...
Reed
6 days ago
I believe patching applications with high vulnerabilities is also necessary for compliance.
upvoted 0 times
...
Art
11 days ago
I agree with Lashonda, that's one of the actions needed for compliance.
upvoted 0 times
...
Lashonda
12 days ago
I think the administrator should enable the web filter profile.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77