nerdexam
Microsoft

DP-700 · Question #62

Your organization wants to classify data based on its sensitivity and regulatory requirements. Which of the following methods would be most appropriate for implementing data classification within…

The correct answer is A. Use Azure Information Protection (AIP) labels to classify data at the file or folder level. To implement data classification based on sensitivity and regulatory requirements in Microsoft Fabric, using Azure Information Protection (AIP) labels is the most appropriate method.

Manage data governance and security

Question

Your organization wants to classify data based on its sensitivity and regulatory requirements. Which of the following methods would be most appropriate for implementing data classification within Microsoft Fabric ?

Options

  • AUse Azure Information Protection (AIP) labels to classify data at the file or folder level.
  • BCreate custom tags in Azure Data Factory to label data based on its sensitivity.
  • CConfigure row-level security (RLS) to restrict data visibility based on sensitivity levels.
  • DImplement data masking to obfuscate sensitive data.

How the community answered

(32 responses)
  • A
    78% (25)
  • B
    3% (1)
  • C
    13% (4)
  • D
    6% (2)

Why each option

To implement data classification based on sensitivity and regulatory requirements in Microsoft Fabric, using Azure Information Protection (AIP) labels is the most appropriate method.

AUse Azure Information Protection (AIP) labels to classify data at the file or folder level.Correct

Azure Information Protection (AIP) labels, now often integrated with Microsoft Purview Information Protection, are specifically designed for classifying data based on its sensitivity and regulatory requirements. These labels can be applied at various levels in Fabric, providing a consistent and enforceable mechanism for data governance and protection.

BCreate custom tags in Azure Data Factory to label data based on its sensitivity.

Custom tags in Azure Data Factory are primarily for organizing and filtering pipelines or datasets within Data Factory itself, not for enterprise-wide data sensitivity classification or regulatory compliance.

CConfigure row-level security (RLS) to restrict data visibility based on sensitivity levels.

Row-level security (RLS) restricts who can see which rows of data based on permissions, which is an access control mechanism, not a method for classifying the inherent sensitivity of the data itself.

DImplement data masking to obfuscate sensitive data.

Data masking is a technique to obfuscate or hide sensitive data from unauthorized users, serving as a data protection measure, but it is not a method for classifying the data's sensitivity or regulatory requirements.

Concept tested: Data classification and Microsoft Purview

Source: https://learn.microsoft.com/en-us/fabric/data-governance/microsoft-purview-information-protection-overview

Topics

#Data Classification#Microsoft Purview#Sensitivity Labels#Data Governance

Community Discussion

No community discussion yet for this question.

Full DP-700 Practice