Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Fortinet Exam NSE5_FCT-7.0 Topic 5 Question 34 Discussion

Actual exam question for Fortinet's NSE5_FCT-7.0 exam
Question #: 34
Topic #: 5
[All NSE5_FCT-7.0 Questions]

In a FortiSandbox integration, what does the remediation option do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Under 'Remediation Options' section, there are only two options (Quarantine infected files, Alert & Notify only). https://docs.fortinet.com/document/forticlient/6.0.0/administration-guide/657996/configuring-submission-access-and-remediation#:~:text=disable%20this%20feature.-,Remediation%20Options,-Quarantine%20infected%20files


Contribute your Thoughts:

Sharmaine
6 months ago
Yes, having a proactive remediation option can enhance security measures.
upvoted 0 times
...
Martha
6 months ago
That makes sense, it's important to have that kind of automatic response.
upvoted 0 times
...
Lucia
6 months ago
I think the remediation option denies access to a file when it sees no results.
upvoted 0 times
...
Sharmaine
6 months ago
That could be a possibility, but I think it might also include alerting and notifying users.
upvoted 0 times
...
Martha
7 months ago
I believe the remediation option excludes specified files.
upvoted 0 times
...
Sharmaine
7 months ago
I think the remediation option waits for FortiSandbox results before allowing files.
upvoted 0 times
...
Keith
7 months ago
I would say the remediation option waits for FortiSandbox results before allowing files to be accessed.
upvoted 0 times
...
Brynn
7 months ago
I believe the remediation option excludes specified files from being analyzed by FortiSandbox.
upvoted 0 times
...
Jonelle
7 months ago
I think the remediation option in a FortiSandbox integration denies access to a file when it sees no results.
upvoted 0 times
...
Marica
8 months ago
You know, I've actually worked with FortiSandbox before, and the remediation option is all about taking action based on the analysis results. I think option A, waiting for the results, is the correct answer here. It's the safest way to ensure potentially malicious files don't slip through.
upvoted 0 times
...
Twila
8 months ago
Haha, this question reminds me of that time I accidentally denied access to a critical file and caused a major outage. Option D sounds a bit too extreme, don't you think? I'm going to go with option B, excluding specified files, as that seems like a more balanced approach.
upvoted 0 times
...
Ashton
8 months ago
I'm not convinced that option A is the right answer. Waiting for FortiSandbox results could potentially cause some delays in file access, which might not be ideal in a production environment. I'm leaning more towards option C, just alerting and notifying users.
upvoted 0 times
...
Justine
8 months ago
Hmm, this question seems a bit tricky. I'm not entirely sure about the remediation option in FortiSandbox integration. I'm inclined to go with option A, waiting for the FortiSandbox results before allowing files. That seems like the safest approach.
upvoted 0 times
Evangelina
7 months ago
I agree with option A, waiting for FortiSandbox results.
upvoted 0 times
...
Susana
7 months ago
I think option D is the best choice to ensure security.
upvoted 0 times
...
Valene
8 months ago
I'm not sure about this one, but option C, alerting and notifying only, seems logical.
upvoted 0 times
...
Shalon
8 months ago
I'm leaning towards option A as well, waiting for the results first.
upvoted 0 times
...
Doug
8 months ago
I believe option B, excluding specified files, is the way to go.
upvoted 0 times
...
Elise
8 months ago
I would go with option D, denying access if there are no results.
upvoted 0 times
...
Katheryn
8 months ago
I think option A sounds like the safest choice.
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