Manage compliance by using Microsoft Purview →mediumMultiple Choice

MS-102 Manage compliance by using Microsoft Purview Practice Question

Your organization uses Microsoft Purview Records Management and has a file plan that categorizes records by department. You need to ensure that HR records are retained for seven years after employee termination, while finance records are retained for ten years after the end of the fiscal year. What is the most efficient way to implement this?

⚠ Common exam trap

MS-102 often tests the distinction between retention policies (location-wide, no event triggers) and retention labels (item-level, support event-based triggers) — candidates pick policies because they sound simpler, missing that event-based retention requires 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

✓

Create two retention labels: one for HR with termination trigger and seven-year retention, and one for Finance with end-of-fiscal-year trigger and ten-year retention.

Retention labels in Microsoft Purview Records Management support event-based retention triggers, and each label can have its own retention period and trigger type. Creating one label for HR with a termination trigger and seven-year retention, and another for Finance with an end-of-fiscal-year trigger and ten-year retention, directly maps to the two distinct business requirements. Labels are the correct construct for file-plan-based records management because they can be published to specific locations and applied per-item.

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 single retention label with a trigger event and adjust the retention period using PowerShell.
Why it's wrong here
A single retention label cannot hold two different retention periods, and PowerShell cannot override a label's configured duration. It tempts because trigger events correctly handle termination- and fiscal-year-based retention, but the file plan needs separate labels per department to express seven versus ten years.
✓
Create two retention labels: one for HR with termination trigger and seven-year retention, and one for Finance with end-of-fiscal-year trigger and ten-year retention.
Why this is correct
Retention labels support event-based triggers, letting HR use a termination trigger and Finance an end-of-fiscal-year trigger, each with its own retention period. Two labels satisfy both departmental rules within one file plan, avoiding separate policies per department.
✗
Define the retention settings in the file plan and apply them to both departments.
Why it's wrong here
The file plan defines labels and their retention settings, but a single label cannot carry both seven-year and ten-year periods, so applying one setting to both departments fails. It tempts because the file plan is the correct place to organise records, yet distinct labels per department are still required.
✗
Create two retention policies, one for HR and one for Finance, each with the appropriate retention period.
Why it's wrong here
Retention policies apply at workload or location level and cannot trigger retention from an event such as employee termination or fiscal year end; they also bypass the file plan's departmental categorisation. It tempts because policies are quick to deploy, but event-driven retention requires retention labels with trigger events.

Go deeper

MS-102 Manage compliance by using Microsoft Purview Practice Question

Why each option matters

Option-by-option breakdown

Related to this question