Microsoft MS-102 Exam Dumps, Practice Test Questions

The protected keyword list was not updated to include the new alias. would fit a different circumstance involving: An organization wants to identify a short list of confidential project code words in stored content. Here the actual symptom is: The label exists in Purview but is unavailable to document owners.

The regex or supporting match criteria are too broad for the intended sensitive information. is a plausible failure in another case: The custom detector flags arbitrary numbers without the required employee identifier structure. It does not explain the current incident: The label exists in Purview but is unavailable to document owners.

The SharePoint location or sharing restriction was omitted from applicable DLP conditions. would fit a different circumstance involving: Confidential documents uploaded to SharePoint must not be shared to anonymous recipients. Here the actual symptom is: The label exists in Purview but is unavailable to document owners.

Use a sensitive information type with a curated keyword list where appropriate. can be useful when an organization wants to identify a short list of confidential project code words in stored content. However, it does not specifically achieve: The retention calculation begins from the approved date or event.

Create a custom sensitive information type using a supported regular-expression pattern and confidence evidence. addresses another administrative need: Compliance needs to detect a proprietary employee identifier that follows a distinct pattern in documents. This question instead requires the outcome: The retention calculation begins from the approved date or event.

Apply Purview DLP to eligible OneDrive accounts for specific sensitive data patterns. can be useful when employees store sensitive customer files in OneDrive and the organization wants targeted sharing protection. However, it does not specifically achieve: The retention calculation begins from the approved date or event.

Configure the protected keyword list and applicable match conditions in Purview. is directed at a separate task: An organization wants to identify a short list of confidential project code words in stored content. It does not produce the required configuration outcome: The retention calculation begins from the approved date or event.

Define and test the custom sensitive information type in Microsoft Purview with the required regex and evidence. implements a different mechanism for: Compliance needs to detect a proprietary employee identifier that follows a distinct pattern in documents. It does not configure the mechanism needed here: Choose retention-label settings based on the intended retention trigger.

Configure a DLP policy with a supported OneDrive location and required sensitive-content conditions. is directed at a separate task: Employees store sensitive customer files in OneDrive and the organization wants targeted sharing protection. It does not produce the required configuration outcome: The retention calculation begins from the approved date or event.

Documents containing protected code words produce the intended sensitive-information match. would assess a different control. In this case it does not rule out the specific failure: Records expire too early because a creation-based clock was used instead of a legal close event.

Test content matching the intended identifier is detected while unrelated strings are not. is evidence of another system state: Compliance needs to detect a proprietary employee identifier that follows a distinct pattern in documents. The acceptance evidence here instead is: The retention calculation begins from the approved date or event.

An in-scope Teams message with regulated data triggers the expected response. would assess a different control. In this case it does not rule out the specific failure: Records expire too early because a creation-based clock was used instead of a legal close event.

The appropriate Content explorer visibility or permission was not available. would fit a different circumstance involving: A data steward needs to locate repositories containing identified sensitive information types. Here the actual symptom is: Records expire too early because a creation-based clock was used instead of a legal close event.

The protected keyword list was not updated to include the new alias. is a plausible failure in another case: Documents with a new project alias are not classified as sensitive. It does not explain the current incident: Records expire too early because a creation-based clock was used instead of a legal close event.

DLP policy event evidence was not examined for the attempted activity. would fit a different circumstance involving: Compliance officers want to review whether a DLP rule blocked an external transfer yesterday. Here the actual symptom is: Records expire too early because a creation-based clock was used instead of a legal close event.

Configure the supported default label in the user-targeted sensitivity label policy. can be useful when the company needs a default sensitivity label for new Office documents in a controlled department. However, it does not specifically achieve: An attempted user deletion does not defeat the required retention obligation.

Use labeling activity evidence and appropriate audit history in Microsoft Purview. addresses another administrative need: A data protection officer wants to prove that a label was changed by an employee on a certain day. This question instead requires the outcome: An attempted user deletion does not defeat the required retention obligation.

Configure Purview DLP for supported Teams chat and channel messages. can be useful when a company wants DLP to apply to sensitive messages sent through supported Microsoft Teams chats. However, it does not specifically achieve: An attempted user deletion does not defeat the required retention obligation.

Configure the sensitivity label's encryption and content marking settings and publish it. is directed at a separate task: An enterprise wants confidential files to carry encryption and visual marking based on classification. It does not produce the required configuration outcome: An attempted user deletion does not defeat the required retention obligation.

Create or update the sensitivity label policy and scope it to the intended users. implements a different mechanism for: Security wants employees to see an Internal label in Office desktop clients. It does not configure the mechanism needed here: Use an appropriate retention configuration that preserves content throughout the required period.

Open DLP alerts or activity events and filter by policy, time and workload. is directed at a separate task: Compliance officers want to review whether a DLP rule blocked an external transfer yesterday. It does not produce the required configuration outcome: An attempted user deletion does not defeat the required retention obligation.

The report identifies label usage and relevant labeling events. would assess a different control. In this case it does not rule out the specific failure: Required records disappear permanently after a user removes a file.

The event shows the relevant actor, time and labeling action. is evidence of another system state: A data protection officer wants to prove that a label was changed by an employee on a certain day. The acceptance evidence here instead is: An attempted user deletion does not defeat the required retention obligation.

A protected file's external sharing action is restricted when the policy matches. would assess a different control. In this case it does not rule out the specific failure: Required records disappear permanently after a user removes a file.

The protected keyword list was not updated to include the new alias. would fit a different circumstance involving: An organization wants to identify a short list of confidential project code words in stored content. Here the actual symptom is: Required records disappear permanently after a user removes a file.

The published label policy lacks the default label or targets the wrong users. is a plausible failure in another case: New files in the department remain unlabeled despite an approved default policy. It does not explain the current incident: Required records disappear permanently after a user removes a file.

The DLP rule was enforced without a suitable test-mode evaluation. would fit a different circumstance involving: A new DLP policy might disrupt legitimate workflows and must be assessed before enforcement. Here the actual symptom is: Required records disappear permanently after a user removes a file.

Use Microsoft Purview Content explorer for supported sensitive-content visibility. can be useful when a data steward needs to locate repositories containing identified sensitive information types. However, it does not specifically achieve: A labeled document applies the intended access restrictions and visual marking.

Use an appropriate retention configuration that preserves content throughout the required period. addresses another administrative need: A policy requires keeping content for seven years even when users try to delete it. This question instead requires the outcome: A labeled document applies the intended access restrictions and visual marking.

Investigate DLP activity with user, file, destination and rule context. can be useful when a protected endpoint file transfer produces alerts but the SOC must separate a real data leak from a benign test. However, it does not specifically achieve: A labeled document applies the intended access restrictions and visual marking.

Apply the supported Purview retention setting for the content location and duration. is directed at a separate task: A policy requires keeping content for seven years even when users try to delete it. It does not produce the required configuration outcome: A labeled document applies the intended access restrictions and visual marking.

Define and test the custom sensitive information type in Microsoft Purview with the required regex and evidence. implements a different mechanism for: Compliance needs to detect a proprietary employee identifier that follows a distinct pattern in documents. It does not configure the mechanism needed here: Use Microsoft Purview sensitivity labels for file protection where supported.

Create an eligible custom Purview DLP policy selecting the Copilot and Copilot Chat location and supported conditions. is directed at a separate task: An organization enables Copilot but must protect matching sensitive information within supported Microsoft 365 Copilot scenarios. It does not produce the required configuration outcome: A labeled document applies the intended access restrictions and visual marking.