Design and implement data storage →hardMultiple Choice

DP-203 Design and implement data storage Practice Question

Exhibit

Refer to the exhibit.

{
  "properties": {
    "dataLakeStorageAccountDetails": [
      {
        "accountUrl": "https://mystorageaccount.dfs.core.windows.net"
      }
    ],
    "defaultDataLakeStorage": {
      "accountUrl": "https://mystorageaccount.dfs.core.windows.net",
      "filesystem": "synapseworkspace"
    },
    "sqlAdministratorLogin": "adminuser",
    "sqlAdministratorLoginPassword": "",
    "managedResourceGroupName": "managedRG",
    "purviewConfiguration": {
      "purviewResourceId": "/subscriptions/sub-id/resourceGroups/rg/providers/Microsoft.Purview/accounts/purview-account"
    },
    "encryption": {
      "cmk": {
        "key": {
          "name": "cmk-key",
          "keyVaultUrl": "https://kv.vault.azure.net/"
        }
      }
    }
  }
}

Refer to the exhibit. A Bicep file is used to deploy an Azure Synapse Analytics workspace. What is the purpose of the 'purviewConfiguration' property?

⚠ Common exam trap

Test-takers frequently confuse the Purview integration with general cataloging or monitoring features, assuming it only applies to pipeline sources rather than understanding it provides full data lineage and cataloging across the entire Synapse workspace.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

It links the workspace to a Microsoft Purview account for data lineage and cataloging

The 'purviewConfiguration' property in a Bicep file for Azure Synapse Analytics links the workspace to a Microsoft Purview account. This integration enables automated data lineage tracking, cataloging, and discovery across the Synapse environment, allowing users to search for and govern data assets directly from Purview. Without this property, the Synapse workspace operates independently of Purview's unified data governance capabilities.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
It links the workspace to a Microsoft Purview account for data lineage and cataloging
Why this is correct
The purviewConfiguration property binds the Synapse workspace to a Microsoft Purview account, enabling automatic lineage capture and metadata cataloging for workspace artefacts. This satisfies the requirement to govern and trace data assets across the workspace.
✗
It configures automated backups of the Synapse workspace
Why it's wrong here
purviewConfiguration associates the workspace with Microsoft Purview for data governance and lineage; backup scheduling is not its function. Synapse workspace backups are handled through Azure-native recovery options, which would be the correct mechanism when disaster recovery is the requirement.
✗
It enables monitoring of data movement by Azure Monitor
Why it's wrong here
purviewConfiguration links the Synapse workspace to a Microsoft Purview account for lineage and cataloguing; it does not enable Azure Monitor data-movement monitoring, which uses diagnostic settings and Log Analytics. Purview would be correct when governance and lineage tracking are required.
✗
It connects the workspace to a data catalog for pipeline sources
Why it's wrong here
purviewConfiguration registers the workspace with a Microsoft Purview account so lineage and metadata flow into the governance portal; it does not connect pipeline sources. Pipeline source connections are configured through linked services, which would be correct when external data stores must be accessed.

Visual reference

Go deeper

DP-203 Design and implement data storage Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question