Manage compliance by using Microsoft Purview →mediumMultiple Choice

MS-102 Manage compliance by using Microsoft Purview Practice Question

A compliance officer needs to retain all documents in a SharePoint Online site associated with the Finance department for 10 years, after which the documents must be automatically deleted. During the retention period, users must be allowed to edit the documents but not delete them. Which Microsoft Purview solution should the officer configure?

⚠ Common exam trap

Many exam-takers confuse retention labels with retention policies, thinking labels are required for site-wide retention, but policies are the correct tool for applying uniform retention and deletion to an entire site without manual 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

✓

retention policy with a retention period of 10 years and an action to delete at the end of the period

A retention policy can be applied to a SharePoint site to enforce a 10-year retention period with a deletion action at the end, while allowing users to edit documents during that period. This meets the compliance requirement because retention policies preserve content from deletion by users, but still permit editing. The 'delete at end of retention period' action ensures automatic removal after 10 years.

Answer analysis

Option-by-option breakdown

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

✓
retention policy with a retention period of 10 years and an action to delete at the end of the period
Why this is correct
A retention policy applied to the SharePoint site works at the container level, automatically covering every document and version without needing per-item labels or rules. Users can continue editing during the 10-year period, but deletion is blocked until the disposition action permanently deletes the files at period end. This directly satisfies both the preservation and the 10-year deletion requirement.
✗
retention label auto-applied to all documents in the site
Why it's wrong here
A retention label auto-applied to all documents requires an auto-application rule that targets specific conditions, such as sensitive information types or keywords, so it cannot guarantee blanket coverage of everything in the site. Even if every document were labeled, the label defaults to allowing edits but can be configured to restrict editing, and labels are item-level rather than container-level. Therefore, labels are not the correct mechanism for enforcing a site-wide lifecycle policy.
✗
Litigation hold on the site
Why it's wrong here
Litigation hold is a legal preservation tool that keeps content indefinitely for eDiscovery purposes, and it has no expiration or scheduled deletion date. Content on the site is protected from permanent deletion as long as the hold is active, but applying it does not configure a 10-year cutoff or automatic disposition. Thus it cannot enforce the required delete-at-end-of-retention behavior.
✗
Data Loss Prevention (DLP) policy with a retention action
Why it's wrong here
DLP policies focus on identifying and protecting sensitive data by enforcing actions like blocking transmission, showing policy tips, or encrypting files; they have no native retention or deletion action. Retention actions live in Microsoft Purview Information Governance, specifically retention policies and labels, not in the DLP solution, so a DLP policy cannot manage document lifecycles. Using it here would not preserve content for 10 years or schedule its deletion.

Go deeper

MS-102 Manage compliance by using Microsoft Purview Practice Question

Why each option matters

Option-by-option breakdown

Related to this question