Develop data processing →easyMultiple ChoiceObjective-mapped

DP-203 Develop data processing Practice Question

Exhibit

Refer to the exhibit.

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "resources": [
        {
            "type": "Microsoft.Synapse/workspaces",
            "apiVersion": "2021-06-01",
            "name": "myworkspace",
            "location": "[resourceGroup().location]",
            "properties": {
                "defaultDataLakeStorage": {
                    "accountUrl": "https://mystorage.dfs.core.windows.net",
                    "filesystem": "myfilesystem"
                },
                "managedResourceGroupName": "synapse-managed-rg"
            }
        }
    ]
}

Refer to the exhibit. You are deploying the ARM template to create an Azure Synapse Analytics workspace. The deployment fails because the managed resource group cannot be created. What is the most likely reason?

⚠ Common exam trap

Many candidates assume they can control the naming of all Azure resources in an ARM template, but Azure Synapse enforces automatic management of its internal resource group, and specifying it triggers a validation error rather than a runtime failure.

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

✓

The managedResourceGroupName property is not allowed; Azure Synapse creates the resource group automatically

The `managedResourceGroupName` property is not allowed in an ARM template for Azure Synapse Analytics. Azure Synapse automatically creates and manages its own managed resource group (e.g., `managed-rg-<workspace-name>`) to hold provisioned resources like Spark pools and SQL pools. Specifying this property in the template causes a validation error, as the service requires full control over the naming and lifecycle of this group.

Answer analysis

Option-by-option breakdown

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

✓
The managedResourceGroupName property is not allowed; Azure Synapse creates the resource group automatically
Why this is correct
You cannot specify a custom managed resource group name.
✗
The apiVersion is invalid for this resource type
Why it's wrong here
2021-06-01 is valid.
✗
The location is missing the 'properties' section
Why it's wrong here
Location is correctly placed.
✗
The storage account URL must use the blob endpoint, not DFS
Why it's wrong here
DFS endpoint is correct for Data Lake Storage Gen2.

Go deeper

DP-203 Develop data processing Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question