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 2 Question 24 Discussion

Actual exam question for Fortinet's NSE6_FML-7.2 exam
Question #: 24
Topic #: 2
[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:

Lindsey
4 months ago
Too much of a good thing, am I right? B and C are the way to go, unless you want your system to grind to a halt.
upvoted 0 times
Vivan
4 months ago
C) More false positives could be detected.
upvoted 0 times
...
Merilyn
4 months ago
B) It is more resource intensive
upvoted 0 times
...
Jose
4 months ago
A) High aggressiveness scan settings do not support executable file types.
upvoted 0 times
...
...
Hobert
4 months ago
I bet the developers at Fortinet were having a laugh when they came up with these options. B and C all the way, my friend.
upvoted 0 times
Alfreda
3 months ago
We should find a balance to avoid these disadvantages.
upvoted 0 times
...
Stefany
3 months ago
Definitely not worth the extra disk space and potential issues.
upvoted 0 times
...
Veronika
3 months ago
Yeah, and it can also lead to more false positives being flagged.
upvoted 0 times
...
Truman
4 months ago
I agree, setting the aggressiveness too high can really drain resources.
upvoted 0 times
...
...
Maxima
5 months ago
High aggressiveness, huh? Sounds like a recipe for a lot of false alarms. B and C are my picks.
upvoted 0 times
Sylvia
3 months ago
It's important to find the right balance to avoid those issues.
upvoted 0 times
...
Kenda
3 months ago
I agree, it can be resource intensive as well.
upvoted 0 times
...
Meghann
4 months ago
Yeah, setting it too high can definitely lead to more false positives.
upvoted 0 times
...
Amie
4 months ago
So, B and C are the two disadvantages we should watch out for.
upvoted 0 times
...
Blondell
4 months ago
Definitely, it can be resource intensive as well.
upvoted 0 times
...
Hortencia
4 months ago
I agree, high aggressiveness can lead to more false positives.
upvoted 0 times
...
...
Christa
5 months ago
Hmm, I'm thinking B and D would be the way to go. Don't want my FortiMail using up all my storage, you know?
upvoted 0 times
Victor
4 months ago
D) FortiMail requires more disk space for the additional rules.
upvoted 0 times
...
Norah
4 months ago
B) It is more resource intensive
upvoted 0 times
...
...
Tamera
5 months ago
Whoa, too much aggressiveness can really bog down the system. I'd go with B and C for sure.
upvoted 0 times
Ailene
4 months ago
Definitely, it's all about finding the right settings for your system.
upvoted 0 times
...
Millie
4 months ago
Yeah, it's important to find a balance to avoid those problems.
upvoted 0 times
...
Stephaine
4 months ago
I think more false positives would be a big issue too.
upvoted 0 times
...
Wilda
4 months ago
Agreed, high aggressiveness can definitely slow things down.
upvoted 0 times
...
...
Bette
5 months ago
But wouldn't configuring the aggressiveness too high also require more disk space for additional rules?
upvoted 0 times
...
Dominga
5 months ago
I agree with that. Another disadvantage could be that it is more resource intensive.
upvoted 0 times
...
Hester
6 months ago
I think one disadvantage is that it could lead to more false positives being detected.
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