SY0-501 · Question #292
Many employees are receiving email messages similar to the one shown below: From IT department To employee Subject email quota exceeded username and password to increase your email quota. Upon…
The correct answer is D. DENY http://*.info/email.php?quota=1Gb. Option D is correct because it precisely targets all three identified common elements of the phishing URLs: the HTTP protocol, the .info TLD (using a wildcard * to catch any subdomain), and the specific URI '/email.php?quota=1Gb'. This specificity ensures the rule blocks the…
Question
Many employees are receiving email messages similar to the one shown below:
From IT department To employee Subject email quota exceeded username and password to increase your email quota. Upon reviewing other similar emails, the security administrator realized that all the phishing URLs have the following common elements; they all use HTTP, they all come from .info domains, and they all contain the same URI. Which of the following should the security administrator configure on the corporate content filter to prevent users from accessing the phishing URL, while at the same time minimizing false positives?
Options
- ABLOCK http://www.*.info/"
- BDROP http://website.info/email.php?"
- CRedirect http://www.*.info/email.php?quota=*TOhttp://company.com/corporate_polict.html
- DDENY http://*.info/email.php?quota=1Gb
How the community answered
(62 responses)- A2% (1)
- B5% (3)
- C11% (7)
- D82% (51)
Explanation
Option D is correct because it precisely targets all three identified common elements of the phishing URLs: the HTTP protocol, the .info TLD (using a wildcard * to catch any subdomain), and the specific URI '/email.php?quota=1Gb'. This specificity ensures the rule blocks the known malicious pattern without broadly blocking legitimate .info domain traffic, thereby minimizing false positives while maximizing protection.
Topics
Community Discussion
No community discussion yet for this question.