How to Retain SharePoint Documents for 7 Years After Last Modification
Your organization uses Microsoft Purview Data Lifecycle Management. You need to ensure that content in a SharePoint site is retained for 3 years after the last modification date. What should you create?
⚠ Common exam trap
The trap is to assume that adaptive retention policies can calculate retention from a per-item property. Adaptive policies use Microsoft Entra ID attributes to dynamically define the scope of the policy (which users or sites are included); they do not provide a method for calculating retention periods from item properties such as last modified date.
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
✓
A static retention policy with a 3-year duration
A static retention policy can be configured to retain content for a specific duration (e.g., 3 years) and to start the retention period based on the last modification date of the items. This directly fulfills the requirement. Adaptive retention policies are used to dynamically define the scope of the policy (which users, groups, or sites are included) based on attributes, not to define how the retention period is calculated for individual items based on their properties like 'Last Modified Date'. The 'Last Modified Date' as a retention start point is a standard option available when configuring retention settings within both static policies and retention labels.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A static retention policy with a 3-year duration
Why this is correct
A static retention policy applies to all content within specified locations (e.g., an entire SharePoint site or all Exchange mailboxes) uniformly. While it defines a retention duration, it does not dynamically calculate the retention start date for each individual item based on its unique 'last modified' property. Instead, its retention start is often tied to the content's creation date or the policy's application, making it unsuitable for granular, item-specific 'last modified' based retention.
- ✗
An auto-labeling policy for sensitive data
Why it's wrong here
An auto-labeling policy is primarily designed to automatically apply sensitivity or retention labels to content based on its characteristics, such as sensitive information types or keywords. While the applied label can dictate retention settings, the auto-labeling policy itself does not directly manage or trigger the start of a retention period based on an item's 'last modified' date. Its function is classification and label application, not dynamic retention period calculation per item.
- ✗
A default retention label for the library
Why it's wrong here
A default retention label for a library ensures that all new content uploaded to that specific library automatically inherits a pre-defined retention label. Although the assigned label can be configured to retain items based on their 'last modified' date, the default label mechanism itself does not actively manage or initiate the retention period based on this property. It merely applies the label; the label's settings then govern the retention, rather than the default label acting as a dynamic retention trigger.
- ✗
An adaptive retention policy based on a custom date property
Why it's wrong here
An adaptive retention policy is specifically designed to dynamically scope content for retention based on specific attributes of users, groups, or sites, and critically, allows for flexible retention start points. This policy type can be configured to use an item's 'last modified' date or even a custom date property as the precise trigger for when the retention period begins. This granular control ensures that retention is accurately applied from the moment an item was last altered, directly meeting the requirement.
Go deeper
Related to this question
Learn chapter
Data Residency, Sovereignty, and Privacy
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.
Key term
Data lifecycle management
Data lifecycle management is the process of managing data from its creation to its deletion, ensuring it is stored, used, and disposed of in a way that meets security, compliance, and business needs.
About these practice questions
Courseiva writes every SC-900 question from scratch — 1,279 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 SC-900 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 SC-900 exam.