nerdexam
Microsoft

DP-203 · Question #371

Drag and Drop Question You have an Azure Synapse Analytics dedicated SQL pool named SQL1 that contains a hash- distributed fact table named Table1. You need to recreate Table1 and add a new…

The correct answer is Create a new table named Table1v2 by running CTAS.; Rename Table1 as Table1_old.; Rename Table1v2 as Table1.; Drop Table1_old. The correct sequence uses CTAS (Create Table As Select) to build the new hash-distributed table with the desired distribution column first, ensuring data is always available - at no point is the original Table1 unavailable to users. Renaming Table1 to Table1_old before swapping…

Submitted by ashley.k· Mar 30, 2026Design and Implement Data Storage - specifically managing and optimizing distributed tables in Azure Synapse Analytics dedicated SQL pools, including zero-downtime schema changes using CTAS and rename patterns.

Question

Drag and Drop Question You have an Azure Synapse Analytics dedicated SQL pool named SQL1 that contains a hash- distributed fact table named Table1. You need to recreate Table1 and add a new distribution column. The solution must maximize the availability of data. Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:

Exhibit

DP-203 question #371 exhibit

Answer Area

Drag items

Create a new table named Table1v2 by running CTAS.Rename Table1v2 as Table1.Rename Table1 as Table1_old.Run DBCC PDW_SHOWSPACEUSED.Drop Table1_old.Drop the indexes of Table1.

Correct arrangement

  • Create a new table named Table1v2 by running CTAS.
  • Rename Table1 as Table1_old.
  • Rename Table1v2 as Table1.
  • Drop Table1_old.

Explanation

The correct sequence uses CTAS (Create Table As Select) to build the new hash-distributed table with the desired distribution column first, ensuring data is always available - at no point is the original Table1 unavailable to users. Renaming Table1 to Table1_old before swapping in Table1v2 ensures a seamless cutover with zero downtime, and dropping Table1_old last cleans up only after the new table is fully in place and accessible. This approach maximizes availability because the original table remains queryable until the very moment the rename swap occurs.

Topics

#Azure Synapse Analytics#Dedicated SQL Pool#CTAS#Hash Distribution#Table Migration

Community Discussion

No community discussion yet for this question.

Full DP-203 Practice