MS-102 Manage compliance by using Microsoft Purview Practice Question

Answer analysis

Option-by-option breakdown

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

• ✓

  Create a communication compliance policy, select the built-in harassment classifier, specify the users to monitor, and assign reviewers.

  Why this is correct

  Creating a communication compliance policy is the sole configuration required to start detecting harassment. The built-in harassment classifier uses pre-trained machine learning models to flag potentially abusive or threatening language in Exchange, Teams, and Yammer messages. You must specify the users or groups whose messages are monitored, and assigning reviewers ensures the flagged messages are investigated and resolved. No additional components such as retention policies, DLP policies, or sensitivity labels are needed as prerequisites.

• ✗

  Create a retention policy for Teams messages, then create a communication compliance policy with the harassment classifier.

  Why it's wrong here

  Adding a Teams retention policy before creating a communication compliance policy is an unnecessary step because the two services operate independently. Retention policies govern how long messages are preserved for legal or archival purposes, whereas communication compliance captures and analyzes messages in real time based on its own policy conditions. The harassment classifier does not rely on retained copies to detect abusive language, so skipping the retention policy has no effect on detection. In fact, configuring retention could interfere with user expectations without any benefit to compliance monitoring.

• ✗

  Create a DLP policy that blocks harassment, then configure communication compliance to review DLP alerts.

  Why it's wrong here

  DLP policies are designed to prevent the sharing of sensitive information such as credit card numbers or personal data and rely on sensitive information types, not pre-trained content classifiers like the harassment classifier. DLP cannot 'block harassment' because it lacks the semantic understanding of abusive language that communication compliance's built-in classifiers provide. Routing DLP alerts into communication compliance for review would add a complex, unsupported workflow rather than simply enabling direct monitoring. Therefore, this option conflates two distinct Purview capabilities and is not a valid way to meet the requirement.

• ✗

  Apply a sensitivity label to all Teams messages, then create a communication compliance policy that scans for the label.

  Why it's wrong here

  Sensitivity labels are metadata tools that mark content with tags for encryption, permission, or visual marking; they do not influence how communication compliance classifiers analyze message text. Applying a sensitivity label to every Teams message is impractical because users must apply labels manually or via auto-labeling policies, and no automatic label can classify every harassing message. Even if a label were present, the harassment classifier analyzes the content itself, not the label, so scanning for the label would not detect harassment in unlabeled messages. This approach misapplies the purpose of sensitivity labeling and adds no value to communication compliance.

Go deeper

Related to this question