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

Question

Options

• AHigh aggressiveness scan settings do not support executable file types.
• BIt is more resource intensive
• CMore false positives could be detected.
• DFortiMail requires more disk space for the additional rules.

• A
  10% (5)
• B
  73% (35)
• D
  17% (8)

Explanation

Setting DLP scan rule aggressiveness too high creates real operational costs: B is correct because aggressive scanning requires significantly more CPU and memory cycles to analyze traffic, slowing throughput and potentially degrading performance for legitimate users. C is correct because overly broad pattern matching catches innocent content as suspicious - a common DLP pitfall where legitimate business emails or files get flagged and blocked, creating unnecessary helpdesk tickets and eroding user trust in the system.

A is wrong because file type support is governed by the scan engine and policy configuration, not aggressiveness level - executable scanning is a separate capability toggle. D is wrong because aggressiveness level controls how strictly existing rules are applied (thresholds, sensitivity), not how many rules are stored on disk; disk space is determined by the number and size of rules/dictionaries, not their sensitivity setting.

Memory tip: Think of aggressiveness like a car alarm sensitivity dial - turn it too high and it goes off every time someone walks past (false positives = C), and the constant triggering drains your battery (resource intensive = B). The alarm itself doesn't need more storage or lose the ability to detect certain car models just because it's sensitive.

No community discussion yet for this question.