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

Trend Exam Deep-Security-Professional Topic 1 Question 54 Discussion

Actual exam question for Trend's Deep-Security-Professional exam
Question #: 54
Topic #: 1
[All Deep-Security-Professional Questions]

Which of the following are valid methods for pre-approving software updates to prevent Ap-plication Control Events from being triggered by the execution of the modified software? Select all that apply.

Show Suggested Answer Hide Answer
Suggested Answer: D

Recommendation Scans can suggest rules for the following Protection Modules:

* Intrusion Prevention

* Integrity Monitoring

* Log Inspection

Explication: Study Guide - page (161)


Contribute your Thoughts:

Becky
3 days ago
B and D for sure. Mucking around in the database file? No thanks, I'll leave that to the experts!
upvoted 0 times
...
Ahmed
6 days ago
Ooh, this is a tricky one. I'm gonna go with B and D - the Trusted Updater and Maintenance Mode options sound like the safest bets.
upvoted 0 times
...
Lezlie
8 days ago
I'm not sure about option D, enabling maintenance mode during updates. Does that really help in preventing triggers?
upvoted 0 times
...
Lonna
10 days ago
I agree with Raymon, editing the inventory database file seems like a good way to prevent Application Control Events.
upvoted 0 times
...
Raymon
12 days ago
I think option C is a valid method for pre-approving software updates.
upvoted 0 times
...
Man
17 days ago
Hmm, I think B and D are the way to go. Manually editing the database file seems like a recipe for disaster!
upvoted 0 times
...
Tyra
18 days ago
B and D seem like the only valid options here. I'm not sure I'd want to manually edit the inventory database file - that sounds risky.
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