Microsoft MS-102 Exam Dumps, Practice Test Questions

Create a DLP policy targeting Exchange Online and appropriate external recipient conditions. is directed at a separate task: A company wants to stop employees emailing files containing regulated identifiers outside the organization. It does not produce the required configuration outcome: A matching sensitive file transfer to removable storage is blocked or audited as required.

Create an eligible custom Purview DLP policy selecting the Copilot and Copilot Chat location and supported conditions. implements a different mechanism for: An organization enables Copilot but must protect matching sensitive information within supported Microsoft 365 Copilot scenarios. It does not configure the mechanism needed here: Use Microsoft Purview Endpoint DLP with supported removable storage restrictions.

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: A matching sensitive file transfer to removable storage is blocked or audited as required.

The affected employee sees the intended policy explanation during a blocked action. would assess a different control. In this case it does not rule out the specific failure: Users copy regulated documents to USB without any endpoint protection event.

The report records the matching policy and enforcement decision for the attempted transfer. is evidence of another system state: Compliance officers want to review whether a DLP rule blocked an external transfer yesterday. The acceptance evidence here instead is: A matching sensitive file transfer to removable storage is blocked or audited as required.

Test content matching the intended identifier is detected while unrelated strings are not. would assess a different control. In this case it does not rule out the specific failure: Users copy regulated documents to USB without any endpoint protection event.

The investigator did not distinguish a policy match from confirmed malicious intent. would fit a different circumstance involving: A protected endpoint file transfer produces alerts but the SOC must separate a real data leak from a benign test. Here the actual symptom is: Users copy regulated documents to USB without any endpoint protection event.

The SharePoint location or sharing restriction was omitted from applicable DLP conditions. is a plausible failure in another case: A protected SharePoint file remains accessible through an anonymous sharing link. It does not explain the current incident: Users copy regulated documents to USB without any endpoint protection event.

The retention label or its publication scope does not enforce the required period. would fit a different circumstance involving: An HR department must retain employee-related records for a designated period to meet its policy. Here the actual symptom is: Users copy regulated documents to USB without any endpoint protection event.

Use the separate supported Microsoft 365 Copilot DLP location in an eligible custom policy rather than combining it with other workload locations. can be useful when an organization enables Copilot but must protect matching sensitive information within supported Microsoft 365 Copilot scenarios. However, it does not specifically achieve: An in-scope Teams message with regulated data triggers the expected response.

Use supported DLP test or simulation mode before turning on blocking actions. addresses another administrative need: A new DLP policy might disrupt legitimate workflows and must be assessed before enforcement. This question instead requires the outcome: An in-scope Teams message with regulated data triggers the expected response.

Choose retention-label settings based on the intended retention trigger. can be useful when a legal group must distinguish a retention period that starts on creation from one based on a later event. However, it does not specifically achieve: An in-scope Teams message with regulated data triggers the expected response.

Review the Endpoint DLP event details and supporting business context before disposition. is directed at a separate task: A protected endpoint file transfer produces alerts but the SOC must separate a real data leak from a benign test. It does not produce the required configuration outcome: An in-scope Teams message with regulated data triggers the expected response.

Deploy the policy in a nonblocking evaluation mode and examine matched events. implements a different mechanism for: A new DLP policy might disrupt legitimate workflows and must be assessed before enforcement. It does not configure the mechanism needed here: Configure Purview DLP for supported Teams chat and channel messages.

Configure the label's retention starting point or supported event-based trigger as required. is directed at a separate task: A legal group must distinguish a retention period that starts on creation from one based on a later event. It does not produce the required configuration outcome: An in-scope Teams message with regulated data triggers the expected response.

The policy reports expected matches without immediately interrupting production actions. would assess a different control. In this case it does not rule out the specific failure: Teams messages bypass a rule applied only to Exchange Online.

The case records a defensible classification and evidence for the transfer attempt. is evidence of another system state: A protected endpoint file transfer produces alerts but the SOC must separate a real data leak from a benign test. The acceptance evidence here instead is: An in-scope Teams message with regulated data triggers the expected response.

The intended retention label appears as a selection for eligible content. would assess a different control. In this case it does not rule out the specific failure: Teams messages bypass a rule applied only to Exchange Online.

End-user policy tip notification settings were not enabled or scoped. would fit a different circumstance involving: A DLP policy detects genuine sensitive material but should inform employees why an action was blocked. Here the actual symptom is: Teams messages bypass a rule applied only to Exchange Online.

Endpoint DLP device onboarding or the removable-media rule is missing. is a plausible failure in another case: Users copy regulated documents to USB without any endpoint protection event. It does not explain the current incident: Teams messages bypass a rule applied only to Exchange Online.

The sensitivity label was not published to the employee's policy scope. would fit a different circumstance involving: Security wants employees to see an Internal label in Office desktop clients. Here the actual symptom is: Teams messages bypass a rule applied only to Exchange Online.

Enable supported DLP policy tips or end-user notifications for the applicable workload. can be useful when a DLP policy detects genuine sensitive material but should inform employees why an action was blocked. However, it does not specifically achieve: A supported Power BI artifact triggers the intended sensitive-data policy alert.

Use supported DLP test or simulation mode before turning on blocking actions. addresses another administrative need: A new DLP policy might disrupt legitimate workflows and must be assessed before enforcement. This question instead requires the outcome: A supported Power BI artifact triggers the intended sensitive-data policy alert.

Use an appropriate retention configuration that preserves content throughout the required period. can be useful when a policy requires keeping content for seven years even when users try to delete it. However, it does not specifically achieve: A supported Power BI artifact triggers the intended sensitive-data policy alert.

Onboard eligible devices and configure an Endpoint DLP rule for copying protected content to USB. is directed at a separate task: A security team must prevent copying regulated files from managed laptops to removable drives. It does not produce the required configuration outcome: A supported Power BI artifact triggers the intended sensitive-data policy alert.

Review the Endpoint DLP event details and supporting business context before disposition. implements a different mechanism for: A protected endpoint file transfer produces alerts but the SOC must separate a real data leak from a benign test. It does not configure the mechanism needed here: Apply supported Microsoft Purview DLP capabilities to the Power BI workload.

Query the relevant Activity explorer labeling event or audit record with identity and time filters. is directed at a separate task: A data protection officer wants to prove that a label was changed by an employee on a certain day. It does not produce the required configuration outcome: A supported Power BI artifact triggers the intended sensitive-data policy alert.

The case records a defensible classification and evidence for the transfer attempt. would assess a different control. In this case it does not rule out the specific failure: The administrator assumes a SharePoint DLP rule automatically governs all Power BI datasets.

An eligible Copilot prompt or response scenario triggers the configured DLP protection. is evidence of another system state: An organization enables Copilot but must protect matching sensitive information within supported Microsoft 365 Copilot scenarios. The acceptance evidence here instead is: A supported Power BI artifact triggers the intended sensitive-data policy alert.

A document can have the planned classification protection and lifecycle obligations. would assess a different control. In this case it does not rule out the specific failure: The administrator assumes a SharePoint DLP rule automatically governs all Power BI datasets.

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: The administrator assumes a SharePoint DLP rule automatically governs all Power BI datasets.

End-user policy tip notification settings were not enabled or scoped. is a plausible failure in another case: Employees experience unexplained DLP restrictions without any configured policy tip. It does not explain the current incident: The administrator assumes a SharePoint DLP rule automatically governs all Power BI datasets.

A sensitivity label was mistakenly treated as a replacement for retention policy. would fit a different circumstance involving: An administrator wants to distinguish file sensitivity labeling from organizational content-retention requirements. Here the actual symptom is: The administrator assumes a SharePoint DLP rule automatically governs all Power BI datasets.