Which two components meet SharePoint Project1 retention requirements?
You have a Microsoft 365 E5 subscription that contains a Microsoft SharePoint Online site named Project1. You need to recommend a record management solution that meets the following requirements: • Retains files in Project1 for a minimum of 10 years • Once Project1 is complete, retains files for an additional five years before the files are deleted Which two components should you include in the recommendation? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Votes
100% of anonymous learners picked answer CD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests event-based retention labels versus retention policies; the trap is confusing adaptive scopes or sensitivity labels with the event type that triggers the additional five-year retention period.
This SC-400 scenario tests event-based retention for SharePoint Online files using a file plan and an event type. The correct recommendation is a file plan paired with an event type, because the retention clock must be reset when Project1 completes.
Learners often choose an adaptive scope or sensitivity label because they associate them with retention, but neither provides the event-driven trigger needed to retain files five years after Project1 completes.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
A file plan (D) is the Microsoft Purview records management container where you create the retention label that sets the 10-year minimum retention period for Project1 files. An event type (C) defines the project completion trigger; when an event of that type is created for the project, the label starts a second retention period of five years before deletion. Together they satisfy both requirements: 10-year baseline retention and an additional five years after Project1 is complete. The file plan also gives records managers the label settings and disposition review needed for SharePoint Online. Therefore CD is the two-part solution.Why the Other Options Are Wrong
A DLP policy (A) prevents data leakage and cannot retain or delete files on a time schedule. An adaptive scope (B) is used with retention policies to dynamically target users, sites, or groups, but it does not support event-based retention; it would retain content based on policy age or start date, not a project completion event. A sensitivity label (E) applies encryption, content marking, or classification and does not itself enforce a 10-year retention or event-triggered deletion. Only a file plan and an event type directly address the record retention lifecycle.Community Comment Notes
Tomaguilarsv reasoned that "once project 1 is completed is an event", pointing to the event type as the trigger for the additional retention. Ruslan23 and PedroLCG both selected CD, reflecting a strong consensus that the solution is a file plan plus event type. No commenter argued for DLP, adaptive scope, or sensitivity label. The community discussion aligns with the exam's focus on event-based retention rather than protection or classification features.Official Reference
Exam Strategy
When a question says 'once the project is complete' or names a milestone, map it to event-based retention: a file plan provides the label, and an event type provides the trigger. Eliminate DLP policies and sensitivity labels because they protect or classify content but do not govern retention and deletion.
Frequently Asked Questions
Why is an adaptive scope not enough for Project1 retention?
Adaptive scopes help target retention policies to sites, but they do not provide event-based retention triggers; the Project1 milestone requires an event type in a file plan.
Can a sensitivity label replace the file plan and event type?
No. Sensitivity labels classify and protect content but cannot enforce a 10-year retention period followed by event-driven deletion; that requires retention labels from a file plan.