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 NSE5_FCT-7.0 Topic 5 Question 30 Discussion

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

An administrator installs FortiClient on Windows Server.

What is the default behavior of real-time protection control?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Amina
24 days ago
Haha, I bet the real-time protection is set to update the signature database from FortiSandbox. That's just classic FortiNet, always trying to push their other products.
upvoted 0 times
...
Gladys
25 days ago
I don't know, I feel like option B might be the correct answer here. Sending malicious files to FortiSandbox for analysis seems like a reasonable default behavior for real-time protection.
upvoted 0 times
...
Tamala
26 days ago
Well, let's think this through. Since it's a Windows Server, I'm guessing the real-time protection is probably disabled by default, right? That seems like the most logical option.
upvoted 0 times
...
Lizette
27 days ago
Hmm, this is an interesting one. Honestly, I'm not too sure about the default behavior of real-time protection when FortiClient is installed on a Windows Server. I'd have to do some research to figure that out.
upvoted 0 times
Bette
9 days ago
D) Real-time protection must update the signature database from FortiSandbox
upvoted 0 times
...
Katy
10 days ago
C) Real-time protection is disabled
upvoted 0 times
...
Harris
11 days ago
B) Real-time protection sends malicious files to FortiSandbox when the file is not detected locally
upvoted 0 times
...
Domonique
12 days ago
A) Real-time protection must update AV signature database
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