Question 1
DRAG DROP -
Case Study -
Instructions -
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study.
To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study.
A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it.
To start the case study -
To display the first question in this case study, select the "Next" button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions. When you are ready to answer a question, select the "Question" button to return to the question.
Overview -
Contoso, Ltd. is a consulting company that has a main office in Montreal and three branch offices in Seattle, Boston, and Johannesburg.
Existing Environment -
Microsoft 365 Environment -
Contoso has a Microsoft 365 E5 tenant. The tenant contains the administrative user accounts shown in the following table.
Users store data in the following locations:
SharePoint sites -
OneDrive accounts -
Exchange email -
Exchange public folders -
Teams chats -
Teams channel messages -
When users in the research department create documents, they must add a 10-digit project code to each document. Project codes that start with the digits 999 are confidential.
SharePoint Online Environment -
Contoso has four Microsoft SharePoint Online sites named Site1, Site2, Site3, and Site4.
Site2 contains the files shown in the following table.
Two users named User1 and User2 are assigned roles for Site2 as shown in the following table.
Site3 stores documents related to the company's projects. The documents are organized in a folder hierarchy based on the project.
Site4 has the following two retention policies applied:
Name: Site4RetentionPolicy1 -
Locations to apply the policy: Site4
Delete items older than: 2 years
Delete content based on: When items were created
Name: Site4RetentionPolicy2 -
Locations to apply the policy: Site4
Retain items for a specific period: 4 years
Start the retention period based on: When items were created
At the end of the retention period: Do nothing
Problem Statements -
Management at Contoso is concerned about data leaks. On several occasions, confidential research department documents were leaked.
Requirements -
Planned Changes -
Contoso plans to create the following data loss prevention (DLP) policy:
Name: DLPpolicy1 -
Locations to apply the policy: Site2
Conditions:
Content contains any of these sensitive info types: SWIFT Code
Instance count: 2 to any -
Actions: Restrict access to the content
Technical Requirements -
Contoso must meet the following technical requirements:
All administrative users must be able to review DLP reports.
Whenever possible, the principle of least privilege must be used.
For all users, all Microsoft 365 data must be retained for at least one year.
Confidential documents must be detected and protected by using Microsoft 365.
Site1 documents that include credit card numbers must be labeled automatically.
All administrative users must be able to create Microsoft 365 sensitivity labels.
After a project is complete, the documents in Site3 that relate to the project must be retained for 10 years.
You need to meet the technical requirements for the Site1 documents.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
The AI agrees with the suggested answer.
The recommended sequence of actions is:
- Create a sensitivity label.
- Create an auto-labeling policy.
- Wait 24 hours.
Reasoning:
The question focuses on automatically protecting credit card information using sensitivity labels. Here's a breakdown of why this sequence is correct:
- Create a sensitivity label: Before you can automatically apply a label, you need to define what that label *is*. A sensitivity label encapsulates the protection settings you want to apply (e.g., encryption, watermarks, access restrictions). This is the foundational step. You define the label and the actions associated with it. See Microsoft's documentation on sensitivity labels for more details (Citation 1).
- Create an auto-labeling policy: This policy defines *how* and *where* the sensitivity label is automatically applied. It specifies the conditions that trigger the application of the label (e.g., the presence of credit card numbers). Auto-labeling policies use sensitive info types to identify content. Since there is a built-in sensitive information type for credit card numbers, creating a custom one isn't needed in this scenario. This step connects the label to the data it should protect. Refer to Citation 2 for guidance on auto-labeling policies.
- Wait 24 hours: Auto-labeling policies often run in simulation mode first. Waiting 24 hours allows this simulation to complete, giving you a chance to review the potential impact of the policy and make adjustments before fully enabling it. It is also possible there may be some initial delay before the policies are fully enforced across the environment. Best practices often recommend waiting to ensure proper propagation. This step provides an opportunity to validate the policy's effectiveness before enforcement (Citation 3).
Reasons for not choosing other options:
- Creating a retention label: While retention labels are important for managing data lifecycle (retention and deletion), they are not directly related to the immediate goal of protecting credit card information with encryption, access controls or watermarks. Retention labels govern how long content is kept, not how it's protected.
- Turning on the policy immediately without waiting: Turning on the auto-labeling policy without waiting can lead to unexpected results if the policy is not configured correctly. Simulation mode is crucial for avoiding disruptions.
- Creating a custom sensitive info type: In this case, as the discussion mentioned, creating a custom sensitive info type is unnecessary because a built-in type for credit card numbers already exists. Creating custom info types is relevant when dealing with uniquely identifiable or proprietary information not already covered.
Therefore, the suggested answer provides the correct order of operations to automatically protect sensitive information (credit card numbers in this scenario) using sensitivity labels and auto-labeling policies.
Important Considerations: Remember that the actual implementation and configuration steps can be more complex and may vary depending on your organization's specific requirements and Microsoft 365 setup. Always thoroughly test and validate your configurations in a non-production environment before deploying them to production.
Caveats: The 24-hour wait period is a general guideline. Actual waiting times can depend on the size of your organization and the complexity of the policy.
Disclaimer: This recommendation is based on the information provided and general best practices. Always consult official Microsoft documentation and seek expert advice for your specific environment.
Confidence Level: High, based on the consensus in the discussion and the supporting documentation.
Impact of Incorrect Answer: Incorrectly sequencing these steps could lead to the failure to properly protect sensitive data, resulting in compliance violations and data breaches. Premature activation of policies could also disrupt legitimate business processes.
Impact of correct answer: Correctly sequencing the steps will ensure that sensitive data such as credit card information will be protected based on pre-defined sensitivity label policies.
In summary, based on the question, the discussion and the information available in Microsoft documentation, creating a sensitivity label, creating an auto-labeling policy, and waiting 24 hours is the correct sequence of actions.
Final Answer: Correct.
Justification for Final Answer: The reasoning and evidence provided above strongly supports this sequence as the correct approach to automatically protecting credit card information using sensitivity labels and auto-labeling policies.
- Citations:
- Citation 1: Learn about sensitivity labels, https://learn.microsoft.com/en-us/purview/sensitivity-labels
- Citation 2: Automatically apply a sensitivity label to content, https://learn.microsoft.com/en-us/purview/apply-sensitivity-label-automatically
- Citation 3: Use simulation mode to test auto-labeling policies, https://learn.microsoft.com/en-us/purview/apply-sensitivity-label-automatically#use-simulation-mode-to-test-auto-labeling-policies






