Minimize Effort for Former Employee Data Deletion
You have a Microsoft 365 E5 subscription. Microsoft Priva Privacy Risk Management licenses are assigned to all users. You need to review and delete all the personal data that relates to a former employee. The solution must minimize administrative effort. What should you do first?
Community Votes
80% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests the distinction between standard eDiscovery workflows and privacy-specific Subject Rights Requests, highlighting that SRR is the intended tool for this scenario.
This SC-400 question addresses the initial step for reviewing and deleting a former employee's personal data with minimal administrative effort using Microsoft Priva.
Learners often select creating an eDiscovery case (B) because it is a standard compliance tool, failing to recognize that Priva Subject Rights Requests is the specialized solution for privacy inquiries.
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
The correct action is to ensure you have the necessary license, which involves purchasing or verifying the Microsoft Priva Subject Rights Requests license (Option C). The core of the question is minimizing administrative effort. Standard eDiscovery (Option B) requires manual setup, query creation, and review, which is labor-intensive. In contrast, Microsoft Priva’s Subject Rights Requests feature automates the collection and processing of data based on predefined schemas, significantly reducing admin overhead. Since the licenses are assigned to 'all users' but SRR is a premium add-on not included in base E5, ensuring the specific capability is licensed/active is the prerequisite first step to enabling the automated workflow.Why the Other Options Are Wrong
Creating a retention policy (A) governs how long data is kept, not how to locate and delete it upon request. Creating an eDiscovery (Standard) case (B) is a valid way to find data but lacks the automation and privacy-specific features of Priva, leading to higher administrative effort. Adding a personal data schema (D) is part of the configuration process for Priva, but one must first ensure the service/license is active; furthermore, the question asks for the action to review and delete, implying the use of the request workflow rather than just schema definition.Community Comment Notes
Community consensus strongly favors Option C. As user belyo noted, "Subject Rights Requests is an add-on not included in E3/E5 so you need to purchase it definitely." Another user, Glacierdk, confirmed via Copilot that SRR is the feature designed for this exact purpose to minimize effort. User Phil_79 raised a nuanced point about administrator vs. user requests, but acknowledged that SRR is the more suitable tool for handling such privacy-centric tasks efficiently compared to manual eDiscovery.Exam Strategy
When a question emphasizes 'minimizing administrative effort' regarding privacy or data subject rights, look for Microsoft Priva solutions like Subject Rights Requests before standard eDiscovery tools. Always check if the required premium license is implied as a prerequisite.
Frequently Asked Questions
Why isn't eDiscovery (Standard) the best choice?
eDiscovery requires manual case setup and content search, increasing administrative effort. Priva SRR automates data discovery and response.
Is Priva included in Microsoft 365 E5?
Base Priva features may be included, but Subject Rights Requests is often a premium add-on or separate entitlement requiring explicit assignment/purchase.