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

- Free Preparation Discussions

Microsoft Exam SC-400 Topic 4 Question 85 Discussion

Actual exam question for Microsoft's SC-400 exam
Question #: 85
Topic #: 4
[All SC-400 Questions]

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You recently discovered that the developers at your company emailed Azure Storage keys in plain text to third parties.

You need to ensure that when Azure Storage keys are emailed, the emails are encrypted.

Solution: You create a data loss prevention (DLP) policy that has all locations selected.

Does this meet the goal?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Angella
1 months ago
This solution is a step in the right direction, but it doesn't fully address the issue. We need a more targeted approach to encrypt the emails containing the Azure Storage keys.
upvoted 0 times
...
Jules
1 months ago
Haha, reminds me of that time my colleague accidentally emailed our company's secret sauce recipe to the entire office. DLP policies are great, but sometimes you just need common sense.
upvoted 0 times
Shawnee
2 days ago
User 3: I agree, common sense goes a long way in preventing these kinds of mishaps.
upvoted 0 times
...
Earleen
14 days ago
User 2: No
upvoted 0 times
...
Cordell
16 days ago
User 1: Yes
upvoted 0 times
...
...
Wenona
2 months ago
Selecting all locations for the DLP policy is a good start, but it doesn't solve the problem of encrypting the emails. We need to find a way to protect the sensitive information in the emails.
upvoted 0 times
Lizbeth
13 days ago
User 3: Selecting all locations for the DLP policy is a good start, but it doesn't solve the problem of encrypting the emails. We need to find a way to protect the sensitive information in the emails.
upvoted 0 times
...
Wilson
29 days ago
User 2: B) No
upvoted 0 times
...
Ardella
1 months ago
User 1: A) Yes
upvoted 0 times
...
...
Wade
2 months ago
I think option A is the correct answer because having all locations selected will ensure comprehensive protection of the keys.
upvoted 0 times
...
King
2 months ago
I disagree, selecting all locations may not be necessary and could lead to unnecessary restrictions.
upvoted 0 times
...
Cory
2 months ago
Yes, that sounds like a good solution to ensure the keys are encrypted.
upvoted 0 times
...
Arlette
2 months ago
The DLP policy covers all locations, but it doesn't specifically address the issue of encrypting the emails. We need a solution that encrypts the emails containing the storage keys.
upvoted 0 times
Reid
1 months ago
User 2: But it doesn't specifically address encrypting the emails with the storage keys.
upvoted 0 times
...
Jerry
1 months ago
The DLP policy covers all locations, but it doesn't specifically address the issue of encrypting the emails. We need a solution that encrypts the emails containing the storage keys.
upvoted 0 times
...
Shenika
1 months ago
User 1: I think the DLP policy covers all locations, so it should work.
upvoted 0 times
...
Tamekia
1 months ago
B) No
upvoted 0 times
...
Jannette
2 months ago
A) Yes
upvoted 0 times
...
...
Lorrie
2 months ago
No, I think we should also restrict the locations where the keys can be emailed.
upvoted 0 times
...
Galen
3 months ago
I agree with Muriel, it will help prevent exposing Azure Storage keys.
upvoted 0 times
...
Muriel
3 months ago
Yes, encrypting emails with DLP policy is a good solution.
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