Manage compliance by using Microsoft Purview →easyMultiple ChoiceObjective-mapped

MS-102 Manage compliance by using Microsoft Purview Practice Question

A compliance officer needs to prevent users from sharing emails that contain credit card numbers with external recipients. When a user attempts to send such an email, it should be blocked immediately, and a policy tip should notify the user. Which Microsoft Purview solution should the officer configure?

⚠ Common exam trap

Microsoft often tests the distinction between DLP policies and sensitivity labels, where candidates mistakenly think a sensitivity label alone can block email transmission, but labels require a DLP policy to enforce actions like blocking, while DLP policies can work independently of labels.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Data Loss Prevention (DLP) policy

A Data Loss Prevention (DLP) policy is the correct solution because it is specifically designed to detect sensitive information, such as credit card numbers, in transit (e.g., email) and enforce actions like blocking the message and displaying a policy tip to the user. DLP policies use sensitive information types (e.g., Credit Card Number) and rules to inspect content in Exchange Online, SharePoint, OneDrive, and Teams, allowing real-time blocking with user notification. This directly meets the compliance officer's requirement to prevent external sharing and provide immediate feedback.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Data Loss Prevention (DLP) policy
Why this is correct
A Data Loss Prevention (DLP) policy in Microsoft Purview can inspect outbound email messages in real time for sensitive information types (e.g., credit card numbers, PII) and apply actions such as blocking delivery, redirecting the message, or allowing override with justification. While composing, the policy can display a policy tip to the user, providing immediate feedback that sharing such content is prohibited, which directly enforces the compliance officer's requirement to prevent email sharing.
✗
sensitivity label
Why it's wrong here
Sensitivity labels apply classification and optional encryption/protection to documents and emails based on manual selection or automated detection rules, but they do not perform real-time inspection of message content at the send event to block delivery. A label can mark an email as 'Confidential' and apply permissions, yet it cannot enforce an outbound-only blocking action with a policy tip when a user tries to share emails containing specific data types, so it cannot fulfill the data loss prevention need described.
✗
retention label
Why it's wrong here
Retention labels are designed for information governance: they specify how long content must be retained and what disposition action to take after that period (delete, or start a disposition review). They do not inspect email body or attachments for sensitive data during transmission and do not intercept or block outgoing messages; their scope is lifecycle management of stored items, not real-time prevention of email sharing.
✗
An information barrier policy
Why it's wrong here
Information barrier policies in Microsoft Purview are used to segment users/groups so that certain individuals are prohibited from communicating with each other (e.g., preventing traders from contacting research analysts). They evaluate sender and recipient relationships based on defined segments, not the content of the message itself, so they cannot detect or block emails that contain sensitive data or show a policy tip about sharing that data.

Go deeper

MS-102 Manage compliance by using Microsoft Purview Practice Question

Why each option matters

Option-by-option breakdown

Related to this question