Describe the capabilities of Microsoft compliance solutions practice questions

Insider Risk Management

Why wrong: Insider Risk Management analyzes user activities for potential data exfiltration but does not directly classify or control sharing.

Communication Compliance

Why wrong: Communication Compliance monitors emails and Teams messages for policy violations like harassment, not for data classification or DLP.

Create new assessments for each regulation

Why wrong: Assessments group controls, but they do not automatically assign actions to team members.

Set up connectors to import external risk data

Why wrong: Connectors bring in signals from other compliance systems but do not assign actions to owners.

Use the Microsoft 365 admin center to delegate tasks

Why wrong: The admin center handles administrative tasks for Microsoft 365, not Compliance Manager action assignments.

Data Lifecycle Management

Why wrong: Incorrect. Data Lifecycle Management manages retention and deletion policies for routine compliance, but it does not provide the ability to place a legal hold that overrides existing policies.

Audit (Premium)

Why wrong: Incorrect. Audit (Premium) logs and retains audit records of activities but does not prevent the deletion of documents or enforce retention.

Communication Compliance

Why wrong: Incorrect. Communication Compliance is designed to detect policy violations in communications (e.g., harassment, sensitive info), not to preserve documents for legal hold.

A DLP policy that detects sensitive info

Why wrong: Incorrect. DLP policies are focused on actions like blocking or notifying when sensitive data is shared. Auto-labeling is accomplished via a separate auto-labeling policy, not DLP.

A data classification dashboard

Why wrong: Incorrect. The data classification dashboard provides reports and visibility into classified data, but it does not perform automatic labeling.

Data Loss Prevention (DLP)

Why wrong: DLP policies detect and prevent unauthorized sharing of sensitive data, not retention or deletion scheduling.

eDiscovery

Why wrong: eDiscovery is used to search, hold, and export content for legal or investigative purposes, not for scheduled retention and deletion.

Information Protection

Why wrong: Information Protection applies sensitivity labels to classify and protect data but does not manage retention or deletion schedules.

Data Lifecycle Management

Why wrong: Data Lifecycle Management is used to automatically retain or delete data based on policies, not to prevent sharing in real time.

Insider Risk Management

Why wrong: Insider Risk Management helps identify and investigate malicious or accidental insider activities, but it does not enforce real-time prevention of sharing sensitive data via DLP rules.

eDiscovery

Why wrong: eDiscovery is used for searching and exporting content for legal or investigative purposes, not for preventing data loss.

eDiscovery (Standard)

Why wrong: eDiscovery is used for legal hold and content search, not for automated retention and deletion.

Compliance Manager

Why wrong: Compliance Manager provides compliance assessments and recommendations but does not enforce retention or deletion.

Information Protection with sensitivity labels

Why wrong: Sensitivity labels classify and protect data (e.g., encryption) but do not automatically manage retention or deletion.

Retention labels

Why wrong: Retention labels can preserve content, but they are policy-based and can be overridden by users unless locked. Litigation Hold is more appropriate for legal hold scenarios.

Data loss prevention

Why wrong: DLP prevents data sharing but does not preserve data for legal holds.

Compliance Manager

Why wrong: Compliance Manager helps manage compliance activities and assessments but does not place holds on data.

Data Loss Prevention (DLP)

Why wrong: DLP prevents users from sharing sensitive data, but does not block communication between specific groups entirely.

Data Lifecycle Management

Why wrong: This manages retention and deletion of data, not real-time communication restrictions.

Microsoft Purview eDiscovery

Why wrong: eDiscovery is for searching and exporting content related to legal cases, not for preventing communication.

Communication Compliance

Why wrong: Communication Compliance helps organizations capture and monitor communications (e.g., email, Teams) to minimize compliance and regulatory risks. It does not control Microsoft support access.

Insider Risk Management

Why wrong: Insider Risk Management uses analytics to identify potentially risky user activities that may lead to data breaches, but it does not manage support access.

Data Lifecycle Management

Why wrong: Data Lifecycle Management automates retention and deletion of data based on policies. It does not provide a mechanism to approve or deny support access.

Communication Compliance and Insider Risk Management

Why wrong: Incorrect. Communication Compliance monitors and reviews communications but does not block them; Insider Risk Management identifies risky user behavior but does not enforce segmentation or prevent data sharing.

Information Barriers and Communication Compliance

Why wrong: Incorrect. While Information Barriers block communications, Communication Compliance only monitors and does not prevent the sharing of sensitive data. This combination lacks DLP to stop credit card numbers from being shared externally.

Data Lifecycle Management and Data Loss Prevention

Why wrong: Incorrect. Data Lifecycle Management governs retention and deletion, not communication segmentation. DLP alone cannot prevent communications between departments.

Microsoft Purview Data Loss Prevention (DLP)

Why wrong: DLP policies can automatically block or warn users from sharing sensitive data, but they do not use behavioral analytics to proactively detect potential data theft; they are rule-based prevention mechanisms.

Microsoft Purview Audit (Standard)

Why wrong: Audit (Standard) records user and admin activities for investigation and compliance purposes, but it does not include automated detection or behavioral analytics to identify risky patterns.

Microsoft Purview Information Barriers

Why wrong: Information Barriers prevent communication and collaboration between specific groups via Teams, SharePoint, and email, but they do not detect data theft or use behavioral analytics.

Data Lifecycle Management (DLM)

Why wrong: Data Lifecycle Management (via retention policies and labels) can manage retention and deletion, but it does not provide the 'record' status that locks a document to prevent editing. DLM is for general content lifecycle, not regulatory records.

eDiscovery (Premium)

Why wrong: eDiscovery is used for legal discovery holds and searches, not for automating retention and disposition of records based on a fixed schedule.

Sensitivity Labels

Why wrong: Sensitivity labels apply classification and protection (e.g., encryption, visual markings) but do not enforce immutable retention that prevents deletion or editing for a specified period.

Microsoft Purview Information Protection

Why wrong: Information Protection enables classification, labeling, and protection of data (e.g., sensitivity labels), but does not assess overall compliance with multiple frameworks.

Microsoft Purview Data Loss Prevention (DLP)

Why wrong: DLP prevents accidental sharing of sensitive information, but does not provide compliance scores or assessments against regulatory frameworks.

Microsoft Purview eDiscovery

Why wrong: eDiscovery is used for legal holds, content searches, and case management during investigations, not for ongoing compliance posture assessment.

Information Protection

Why wrong: Microsoft Purview Information Protection helps discover, classify, and protect sensitive data using labels and encryption. It does not provide regulatory assessments, scores, or a unified compliance tracking dashboard.

Data Lifecycle Management

Why wrong: Microsoft Purview Data Lifecycle Management (formerly Records Management) governs the lifecycle of data, including retention and deletion policies. It does not assess compliance posture against regulatory frameworks.

Insider Risk Management

Why wrong: Microsoft Purview Insider Risk Management detects, investigates, and acts on risky user activities that may lead to data breaches. It is not designed for regulatory compliance assessment or scoring.

Microsoft Purview Retention Labels with a disposition review that requires manual approval at the end of the retention period

Why wrong: A disposition review with manual approval does not guarantee automatic deletion; it would require someone to manually approve each item.

Microsoft Purview Retention Policy with a record label to mark items as regulatory records

Why wrong: Marking items as regulatory records makes them immutable and prevents modification or deletion, even after the retention period, so automatic deletion would not occur.

Microsoft Purview eDiscovery with a hold policy to preserve the documents indefinitely

Why wrong: eDiscovery hold is for preserving data for legal investigations; it does not enforce a retention period with automatic deletion.

Microsoft Purview eDiscovery

Why wrong: eDiscovery is used for legal investigations and litigation, not for managing subject rights requests under privacy regulations.

Microsoft Purview Audit

Why wrong: Audit records user and admin activities but does not provide workflow to discover and manage personal data in response to a subject rights request.

Microsoft Purview Data Lifecycle Management (retention labels)

Why wrong: Retention labels are for retaining or deleting content based on policies, not for orchestrating the discovery and response to subject rights requests.

Microsoft Purview Communication Compliance

Why wrong: Communication Compliance is used to detect policy violations in communications but does not block communication between groups or block outbound emails.

Microsoft Purview Audit (Standard)

Why wrong: Audit only logs activities; it does not enforce communication separation or block data sharing.

Microsoft Purview Compliance Manager

Why wrong: Compliance Manager helps organizations assess and improve their compliance posture across regulations, but it does not place legal holds or search for content.

Microsoft Purview Data Lifecycle Management

Why wrong: Data Lifecycle Management (retention labels and policies) can enforce retention and deletion rules, but it cannot place a legal hold that preserves content against modification or deletion, nor does it provide the search and export features needed for litigation.

Microsoft Purview Audit (Standard)

Why wrong: Audit (Standard) records user activities for security and compliance, but it does not preserve content or allow search and export of the actual items.

Data Lifecycle Management

Why wrong: Data Lifecycle Management focuses on retaining and deleting content based on policies, not on assessing compliance posture or tracking improvement actions against regulations.

Audit

Why wrong: Microsoft Purview Audit logs user and admin activities but does not assess compliance posture or provide improvement actions for regulatory frameworks.

eDiscovery

Why wrong: eDiscovery is used to search, hold, and export content for legal investigations, not for continuous compliance assessment against regulations.