An organization processes financial data using Azure Machine Learning. Microsoft Purview must be configured to automatically classify files uploaded to Azure Data Lake Storage Gen2 that contain International Bank Account Numbers (IBANs). The classification must happen within 24 hours of file upload. How should this be configured?
Select an answer to reveal the explanation.
Short Explanation
You need to register the Azure Data Lake Storage Gen2 account in Purview, then set up a recurring scan every 24 hours with a built-in IBAN classification rule. That way, newly uploaded files get classified within the required window.
Full Explanation
Register the Azure Data Lake Storage Gen2 account in Purview and configure a scan with a recurring trigger every 24 hours using a built-in IBAN classification rule. Microsoft Purview Data Map supports scanning registered Azure Data Lake Storage Gen2 accounts using built-in classification rules including IBAN detection, and a recurring 24-hour trigger ensures newly uploaded files are classified within the required timeframe. The option deploying an Azure Event Grid trigger to invoke a Purview scan whenever a file is uploaded is incorrect because Purview does not natively support Event Grid-triggered scans; scans are scheduled or triggered manually in the Purview governance portal. The option configuring Microsoft Purview auto-labeling policies to scan Data Lake storage on upload events is incorrect because auto-labeling policies apply sensitivity labels to files in Microsoft 365 services like SharePoint, not directly to Azure Data Lake Storage Gen2. The option installing the Microsoft Purview Information Protection scanner on the Data Lake storage endpoints is incorrect because that scanner is for on-premises file shares and SharePoint Server, not Azure Data Lake Storage Gen2.