Q: 10
You are configuring the prevention policy for endpoints in the CrowdStrike Falcon console. Which of the
following settings is most appropriate for preventing ransomware attacks while minimizing the risk of
false positives?
Options
Discussion
A . Moderate Sensitivity catches ransomware without hammering you with false positives every day, which is what the question is after. Aggressive can be a pain operationally, tbh. If I missed something let me know.
Probably A since "minimize false positives" is the clear hint here. If the environment had tons of sanctioned encryption apps or weird file IO, even Moderate can false trip, but Aggressive (D) is way riskier for business ops. Only real edge case would be a super locked-down kiosk setting where D might make sense, but that's not what this question describes.
A , since Moderate Sensitivity gives you good ransomware blocking without tanking productivity from tons of false positives. Aggressive (D) is too much for most environments unless you can handle a lot of interruptions. Open to other views if I missed something.
Its A, but if this was for ultra high-security environments with zero tolerance for risk, D could make sense. Here the question asks about minimizing false positives too, so Moderate fits best from what I've seen. Anyone disagree?
A is it tbh
Option D, Aggressive Sensitivity catches more stuff, so I think it's better if you really want to lock things down. Might get a few more false positives but at least ransomware won't slip by.
A feels right here since Moderate Sensitivity gives solid ransomware coverage without all the headaches of constant false positives. Going Aggressive (D) can cause legit apps to break while Low (C) might let threats slip through. Pretty sure A is what most orgs would do in real world setups, unless super high risk.
Honestly, CrowdStrike's options always make you pick between blocking too much or letting stuff slip. A
Be respectful. No spam.
Question 10 of 35