You need to protect documents that contain credit card numbers from being opened by users outside your company. The solution must ensure that users at your company can open the documents. What should you use?
but why sensitivity label isn't a valid option? you can configure your label to apply encryption and grant permission to view only to members of your organization. if you want to prevent people outside the org to OPEN the file, sensitivity label is valid, if you want to prevent people to SHARE outside the org (which may lead to prevent to be opened of course), DLP is valid.
this question is trickier than people are arguing.
sensitivity labels are encrypting the document but not checking if SIT's are used. The only way is DLP Rule which block's external out of indicators of the SIT's
A sensitivity label can:
Encrypt the document
Restrict access to internal users only
Automatically apply based on sensitive information types like credit card numbers (when configured with auto-labeling)
prevent ... from being opened by users outside your company. If it had said prevent from being shared with external users, I would have picked DLP. This question is focused on the function of each technology. Sensitivity Label is what you use to prevent external users from opening files irrespective of how they got the file.
Correct Answer: B. A sensitivity label
Reasoning:
Sensitivity labels can encrypt documents, control access, and ensure that only internal users are authorized to open sensitive files, such as those containing credit card numbers. This directly addresses the requirement to prevent external users from opening the documents while allowing internal users to do so.
Here the question has mention "You need to protect documents that contain credit card numbers "FROM BEING OPENED" by users outside your company." So, it is not asking to restrict sharing, hence, DLP can't be the answer. This can only be done using a Sensitive label > Add CCN as SIT > Include All users in your org. So, wherever the file resides, or travels, only internal users can access the document. And that's the reason organization applies encryption and access control. So, answer is B.
I would rather go with Sensitivity label, because of opening the file by outsiders. But it requires Auto-labeling and the sensitivity label needs to encrypt the file
The questions says you need to "protect documents that contain credit card numbers from being opened by users outside your company". It does not say that you need to "prevent documents that contain credit card numbers from shared with users outside your company".
Prevention is done with DLP.
Protection is done with sensitivity labels.
The answer is B.
DLP for sure- allows you to define rules that detect sensitive information like credit card numbers and then restrict access or actions based on those rules
why "sensitivity label" isn't an option in this case? if you configure your label to encrypt files and apply permissions to view only to members of your organization it would work, once the question is about to "prevent to be OPENED by people outside your org".
if the file is labeled this way it can't be opened.
This section is not available anymore. Please use the main Exam Page.SC-400 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Browniez
Highly Voted 3 years, 8 months agoAbhishek1610
Highly Voted 2 years, 6 months agofimbulvetrk
2 years, 6 months agoKuteron
8 months agoFlacky_Penguin32
Most Recent 3 months agoTest90
3 months, 2 weeks agoJideakin
3 months, 2 weeks agoHardeWerker433
5 months agoSneakyBD
8 months, 1 week agoBoeroe
8 months, 3 weeks agoIndigoRabbit
10 months, 1 week agoRAJRYB
11 months, 3 weeks agoChrisBaird
1 year agoAmin4799
1 year, 1 month agoBewiseExams
1 year, 3 months agoDavidf
1 year, 10 months agoT3st3r
2 years, 1 month agoxswe
2 years, 2 months agofimbulvetrk
2 years, 6 months agoluissaro
2 years, 2 months ago