Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-720 Topic 15 Question 92 Discussion

Actual exam question for Cisco's 300-720 exam
Question #: 92
Topic #: 15
[All 300-720 Questions]

An administrator identifies that, over the past week, the Cisco ESA is receiving many emails from certain senders and domains which are being consistently quarantined. The administrator wants to ensure that these senders and domain are unable to send anymore emails.

Which feature on Cisco ESA should be used to achieve this?

Show Suggested Answer Hide Answer
Suggested Answer: B

According to the [Cisco Secure Email User Guide], graymail is a category of email messages that are not spam but may be unwanted by some recipients, such as newsletters, promotions, or social media updates[5, p. 25]. Marketing is one of the subcategories of graymail that includes messages that advertise products or services[5, p. 26].

The other options are not valid because:

A) Malicious is not a category for classifying graymail. It is a category for classifying email messages that contain malicious content such as malware, phishing, or fraud[5, p. 25].

C) Spam is not a category for classifying graymail. It is a category for classifying email messages that are unsolicited, unwanted, or harmful[5, p. 25].

D) Priority is not a category for classifying graymail. It is a category for classifying email messages that are important, urgent, or relevant[5, p. 25].


Contribute your Thoughts:

Caprice
2 months ago
I say we just set up a giant electrified net to catch all those unwanted emails. That'll teach 'em to mess with our Cisco ESA!
upvoted 0 times
...
Linn
2 months ago
D) S/MIME Sending Profile? Really? What is this, an exam for secret agents? I think I'll stick to the more straightforward options, thank you very much.
upvoted 0 times
Katy
9 days ago
C) blocklist
upvoted 0 times
...
Silva
16 days ago
B) safelist
upvoted 0 times
...
Pedro
17 days ago
A) incoming mail policies
upvoted 0 times
...
...
Thea
2 months ago
I'm going with C) blocklist. Easier to manage than messing around with those complicated mail policies. Plus, it's the perfect way to give those spammers a taste of their own medicine!
upvoted 0 times
Marguerita
13 days ago
I prefer C) blocklist as well. It's a quick and easy solution to stop those annoying emails.
upvoted 0 times
...
Lajuana
17 days ago
I think A) incoming mail policies might be more effective in the long run. It allows for more customization.
upvoted 0 times
...
Von
1 months ago
I agree, C) blocklist is the way to go. Those spammers won't know what hit them!
upvoted 0 times
...
...
Ronald
2 months ago
Hmm, I'm not so sure. Wouldn't the incoming mail policies be a better option? That way, we can fine-tune the filtering and control more precisely.
upvoted 0 times
Linsey
21 days ago
C) blocklist
upvoted 0 times
...
Glennis
22 days ago
A) incoming mail policies
upvoted 0 times
...
Cassi
1 months ago
C) blocklist
upvoted 0 times
...
Germaine
1 months ago
A) incoming mail policies
upvoted 0 times
...
...
Tasia
2 months ago
The blocklist feature seems like the obvious choice here. It'll let us effectively block those pesky senders and domains for good.
upvoted 0 times
Daniel
27 days ago
That's right! Using the blocklist feature will help us prevent those senders and domains from sending any more emails.
upvoted 0 times
...
Malcom
28 days ago
C) blocklist
upvoted 0 times
...
Vicki
29 days ago
D) S/MIME Sending Profile
upvoted 0 times
...
Aleshia
1 months ago
C) blocklist
upvoted 0 times
...
Carissa
1 months ago
B) safelist
upvoted 0 times
...
Blondell
1 months ago
A) incoming mail policies
upvoted 0 times
...
...
Jacinta
3 months ago
I'm not sure, but I think safelist could also be an option to allow only certain senders.
upvoted 0 times
...
Yaeko
3 months ago
I agree with Natalya, using blocklist will prevent those senders and domains from sending emails.
upvoted 0 times
...
Natalya
3 months ago
I think the answer is C) blocklist.
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