You have an Azure Synapse Analytics serverless SQL pool. You need to catalog the serverless SQL pool by using Azure Purview. Which three actions should you perform? Each correct answer presents part…

Creating a managed identity in Azure AD is a prerequisite for Azure Purview's operation, but Purview automatically has a system-assigned managed identity, so explicit creation is not a step performed for cataloging once Purview exists.

Assigning the 'Storage Blob Data Reader' role to the Azure Purview managed service identity (MSI) for the storage account associated with the Synapse workspace grants Purview the necessary permissions to read data stored in the data lake, which is crucial for serverless SQL pool cataloging.

Assigning the 'Owner' role to the Azure Purview MSI for the Azure Purview resource group is excessive and not required for cataloging a Synapse serverless SQL pool, as only read permissions on the data source are needed.

Registering a data source in Purview is the fundamental step to tell Purview about the serverless SQL pool instance it needs to scan and catalog.

Assigning the 'Reader' role to the Azure Purview managed service identity (MSI) for the Synapse Analytics workspace allows Purview to discover and access the metadata of the serverless SQL pool itself within the Synapse workspace.