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 NSE6_FML-7.2 Topic 1 Question 26 Discussion

Actual exam question for Fortinet's NSE6_FML-7.2 exam
Question #: 26
Topic #: 1
[All NSE6_FML-7.2 Questions]

What are two disadvantages of configuring the dictionary and DLP scan rule aggressiveness too high? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Contribute your Thoughts:

Ronna
4 months ago
I'll take 'Things that make your IT team cry' for $500, Alex. B and C are the obvious choices here. Don't want to be that guy who crashes the whole system with overzealous DLP settings.
upvoted 0 times
...
Malcom
4 months ago
Haha, option A made me chuckle. Who configures DLP to not support executable files? That's just asking for trouble. B and C are the way to go.
upvoted 0 times
Kanisha
2 months ago
That's true, we have to consider the trade-offs when configuring DLP rules.
upvoted 0 times
...
Johanna
2 months ago
High aggressiveness can be risky, but it's all about finding the right balance.
upvoted 0 times
...
Truman
2 months ago
Definitely, we need to prioritize resource usage and avoid false positives.
upvoted 0 times
...
Refugia
3 months ago
I agree, option A is a bit funny. Executable files are important to scan.
upvoted 0 times
...
...
Thersa
4 months ago
Option D is just plain silly. Since when does FortiMail need more disk space for DLP rules? B and C are the clear winners here.
upvoted 0 times
Renea
3 months ago
High resource usage and more false positives are definitely not ideal.
upvoted 0 times
...
Telma
3 months ago
I think B and C are definitely the main disadvantages of high aggressiveness settings.
upvoted 0 times
...
Fausto
4 months ago
Yeah, it doesn't make sense for FortiMail to need more disk space for DLP rules.
upvoted 0 times
...
Galen
4 months ago
I agree, option D does seem strange.
upvoted 0 times
...
...
Rene
4 months ago
That's true, but it could also lead to legitimate files being flagged incorrectly.
upvoted 0 times
...
Nikita
5 months ago
Definitely B and C for me. You don't want your system bogged down and getting bombarded with false alerts. Gotta find that sweet spot of security and efficiency.
upvoted 0 times
...
Sherita
5 months ago
But wouldn't having high aggressiveness settings help catch more threats?
upvoted 0 times
...
Rose
5 months ago
I agree with Rene. Another disadvantage is that it is more resource intensive.
upvoted 0 times
...
Rene
5 months ago
I think one disadvantage is that it could lead to more false positives being detected.
upvoted 0 times
...
Hobert
5 months ago
I agree with options B and C. Too much aggressiveness can definitely strain system resources and lead to an increase in false positives. Not a fan of that at all.
upvoted 0 times
Walton
4 months ago
Definitely, we need to find a balance to avoid those issues.
upvoted 0 times
...
Eden
4 months ago
Yeah, it's not worth it if it's going to cause more false positives.
upvoted 0 times
...
Willis
4 months ago
I think high aggressiveness can really slow things down.
upvoted 0 times
...
Rebeca
4 months ago
More false positives can be a headache to deal with.
upvoted 0 times
...
Timothy
4 months ago
Yeah, high aggressiveness can really strain resources.
upvoted 0 times
...
Rolland
4 months ago
I agree with options B and C.
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