Develop data processing →hardMultiple Choice

DP-203 Develop data processing Practice Question

Exhibit

Refer to the exhibit.

{
  "type": "Microsoft.Synapse/workspaces/sqlPools",
  "properties": {
    "createMode": "Default",
    "storageAccountType": "GRS",
    "collation": "SQL_Latin1_General_CP1_CI_AS",
    "maxSizeBytes": 263882790666240,
    "sku": {
      "name": "DW100c",
      "tier": "ServiceObjective"
    },
    "restorePointInTime": null,
    "sourceDatabaseId": null
  }
}

Refer to the exhibit. You are deploying an Azure Synapse Analytics dedicated SQL pool using the provided ARM template snippet. After deployment, you need to adjust the performance level to DW200c to handle increased workload. Which parameter should you modify?

⚠ Common exam trap

The trap is confusing the performance level (sku.name) with capacity limits (maxSizeBytes) — candidates who see 'performance' and 'size' in the same resource often pick maxSizeBytes, but performance tier is always the SKU.

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

✓

sku.name

In an Azure Synapse Analytics dedicated SQL pool ARM template, the performance level (e.g., DW100c, DW200c, DW300c) is specified in the sku.name property of the Microsoft.Synapse/workspaces/sqlPools resource. To change the performance level to DW200c, you modify sku.name. The other parameters control storage redundancy, maximum size, and collation, none of which affect the compute performance level.

Answer analysis

Option-by-option breakdown

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

✗
storageAccountType
Why it's wrong here
storageAccountType sets the pool's backing storage redundancy (LRS, GRS, ZRS), not its compute performance level. It is tempting because storage configuration genuinely matters for dedicated SQL pools, but the DW200c requirement is met by changing the serviceLevelObjective parameter, which controls the DWU allocation.
✗
maxSizeBytes
Why it's wrong here
Changing maxSizeBytes alters only the storage capacity ceiling, not the compute performance level, so DW200c cannot be reached. It is tempting because it governs dedicated SQL pool storage limits, and would be the correct parameter when you need to expand capacity beyond the default 1 TB for a dedicated SQL pool.
✗
collation
Why it's wrong here
Collation fixes sort order, comparison rules and code-page behaviour for character data at creation time; it has no bearing on compute capacity. The performance level is governed by the sku object's name or capacity value, which must specify DW200c.
✓
sku.name
Why this is correct
The performance level of a dedicated SQL pool is defined by the sku.name property, which carries values such as DW200c. Modifying sku.name in the ARM template sets the pool to the required DW200c performance level.

Go deeper

DP-203 Develop data processing Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question