MS-102 Manage compliance by using Microsoft Purview Practice Question
An administrator is creating a Microsoft Purview auto-labeling policy for documents containing personally identifiable information. Before turning the policy on automatically, what should the administrator do to reduce false positives?
⚠ Common exam trap
Test-takers frequently confuse simulation mode with other compliance features like eDiscovery or retention, or assume that immediate application is safe because the policy uses predefined PII types, but Microsoft explicitly recommends simulation mode to validate and reduce false positives before enabling automatic labeling.
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
✓
Run the auto-labeling policy in simulation mode and review matches
Running the auto-labeling policy in simulation mode allows the administrator to review which documents would be matched by the policy without actually applying labels. This enables analysis of the detection results to identify and reduce false positives before enabling automatic application, ensuring the policy accurately targets only documents containing the specified PII.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Run the auto-labeling policy in simulation mode and review matches
Why this is correct
Running the auto-labeling policy in simulation mode is the essential first step because it executes the policy's detection logic against actual content without applying any labels, producing a match report that shows which items would have been labeled and which conditions triggered the match. Reviewing this output lets you validate whether the sensitive information types, conditions, and exclusions are correctly scoped, and tune them to reduce false positives. Only after simulation confirms accurate matches should the policy be switched to enforcement mode, preventing mass mislabeling at scale.
- ✗
Publish the label directly to all users and enable automatic application immediately
Why it's wrong here
Publishing the label directly and immediately enabling automatic application skips the validation phase entirely, so any overly broad conditions or misconfigured sensitive information types will instantly label large volumes of content, creating false positives that are difficult to remediate. Because sensitivity labels often trigger encryption, permissions, or downstream governance actions, unchecked automatic application can lock legitimate content out of collaboration or interfere with eDiscovery. Unlike simulation mode, immediate enforcement provides no pre-deployment report to review, meaning the organization absorbs the full risk of incorrect classification from the moment the policy acts.
- ✗
Create an eDiscovery hold for the SharePoint locations
Why it's wrong here
Creating an eDiscovery hold for SharePoint locations is a preservation mechanism that prevents content from being altered or purged for legal or regulatory purposes; it does not exercise or validate the auto-labeling policy's pattern matching in any way. A hold cannot indicate whether sensitive information types are matching accurately, whether label conditions are producing false positives, or how the policy would behave at scale. Therefore, setting an eDiscovery hold is an unrelated compliance action that does not replace the need to run a simulation and review the match results.
- ✗
Configure a retention policy before creating the sensitivity label
Why it's wrong here
Configuring a retention policy before creating the sensitivity label is an information governance action that solely defines how long content is kept and when it is permanently deleted; it has no role in how sensitive content is detected or classified. Auto-labeling relies on content inspection via sensitive information types and trainable classifiers, while retention policies operate on lifecycle timestamps and locations, so a retention schema will not expose false positives or improve label matching. These are separate Purview functions, and focusing on retention instead of simulation can even obscure the real task of tuning detection logic and increase the risk of mislabeling.
Go deeper
Related to this question
Learn chapter
Sensitivity Labels: Admin Configuration
Key term
Microsoft Purview
Microsoft Purview is a unified data governance and compliance service that helps organizations discover, manage, and protect their data across on-premises, cloud, and hybrid environments.
Key term
Policy
A policy is a set of rules or guidelines that defines how an organization manages, secures, and operates its IT systems and services.
About these practice questions
Courseiva writes every MS-102 question from scratch — 712 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MS-102 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MS-102 exam.