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

Cisco Exam 300-720 Topic 2 Question 88 Discussion

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

The company security policy requires that the finance department have an easy way to apply encryption to their outbound messages that contain sensitive data Users must be able to flag the messages that require encryption versus a Cisco Secure Email Gateway appliance scanning all messages and automatically encrypting via detection Which action enables this capability?

Show Suggested Answer Hide Answer
Suggested Answer: C

According to the [Cisco Secure Email Encryption Service Add-In User Guide], you can create an encryption profile that defines the encryption settings and options for your encrypted messages[2, p. 11]. You can also create an outgoing content filter that applies the encryption profile to the messages that match certain conditions, such as having [SECURE] in the subject header[2, p. 12]. This way, you can allow users to flag the messages that require encryption by adding [SECURE] to the subject line.

The other options are not valid because:

A) Creating an encryption profile with [SECURE] in the Subject setting and enabling encryption on the mail flow policy will not work, as the Subject setting in the encryption profile is used to specify the subject line of the encrypted message envelope, not the original message[2, p. 11].

B) Creating an outgoing content filter with no conditions and with the Encrypt and Deliver Now action configured with [SECURE] in the Subject setting will not work, as this will encrypt all outgoing messages regardless of whether they have [SECURE] in the subject line or not[2, p. 12].

D) Creating a DLP policy manager message action with encryption enabled and applying it to active DLP policies for outgoing mail will not work, as this will encrypt messages based on DLP rules that detect sensitive data in the message content, not based on user flags in the subject line.


Contribute your Thoughts:

Solange
2 months ago
I'm with Kelvin on this one. Option A is just begging to be exploited by any hacker with a high school diploma and a working keyboard. C is the way to go - keep it simple, keep it secure.
upvoted 0 times
Simona
1 months ago
Let's go with option C to keep our messages secure.
upvoted 0 times
...
Terina
1 months ago
Yeah, option C is definitely the safer choice.
upvoted 0 times
...
Carrol
1 months ago
I agree with Kelvin, option A seems risky.
upvoted 0 times
...
...
Beckie
2 months ago
I'm not sure, but I think D could also be a valid option.
upvoted 0 times
...
Kelvin
2 months ago
Option A? Really? Putting 'SECURE' in the subject line? That's about as subtle as a brick to the face. I hope the company's sensitive data is better protected than their email subjects.
upvoted 0 times
...
Earleen
2 months ago
I disagree, I believe the correct answer is A.
upvoted 0 times
...
Jesse
2 months ago
D seems like the most robust option, integrating encryption into the DLP policies. But it might be overkill for a finance department's needs. I'd go with C - it hits the sweet spot of user control and automated encryption.
upvoted 0 times
Rima
25 days ago
Ludivina: Definitely, simplicity is key when it comes to implementing security measures.
upvoted 0 times
...
Lorean
26 days ago
Option D does seem like a strong choice, but it might be too complex for the finance department's needs.
upvoted 0 times
...
Ludivina
27 days ago
Yeah, I think it's important for users to have some control over when encryption is applied.
upvoted 0 times
...
Eleonora
1 months ago
I agree, option C seems like a good balance of user control and automation.
upvoted 0 times
...
...
Tarra
2 months ago
I think the answer is C.
upvoted 0 times
...
Kati
2 months ago
Hmm, option B looks good too. Encrypting everything outbound might be overkill, but at least it's simple to implement. I wonder if the [SECURE] tag in the subject line is really necessary though?
upvoted 0 times
Elvera
1 months ago
User 3: Yeah, having that extra layer of security with the [SECURE] tag could help ensure only the necessary messages get encrypted.
upvoted 0 times
...
Cory
1 months ago
User 2: I agree, encrypting everything might be too much. But having a simple way to flag sensitive messages is important.
upvoted 0 times
...
Willodean
2 months ago
User 1: Option B does seem like a straightforward solution. Maybe the [SECURE] tag is just an extra precaution.
upvoted 0 times
...
Delsie
2 months ago
User 3: I agree. It's important to weigh the pros and cons of each option before making a decision.
upvoted 0 times
...
Shonda
2 months ago
User 2: Yeah, it could be a good way to easily identify which messages need encryption. But I think we should consider all options before deciding.
upvoted 0 times
...
Kristian
2 months ago
User 1: Option B does seem like a simple solution. Maybe the [SECURE] tag is just an extra precaution.
upvoted 0 times
...
...
Jesusa
3 months ago
I think option C is the way to go. It gives users the ability to flag sensitive messages and the content filter takes care of the encryption. Seems like the most straightforward solution.
upvoted 0 times
Robt
2 months ago
Yeah, having the ability to flag messages and automatically encrypt them is definitely the way to go.
upvoted 0 times
...
Kirk
2 months ago
I agree, option C seems like the most efficient choice.
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