You are designing a date dimension table in an Azure Synapse Analytics dedicated SQL pool. The date dimension table will be used by all the fact tables. Which distribution type should you recommend to

The correct answer is B. REPLICATE. A replicated table has a full copy of the table available on every Compute node. Queries run fast on replicated tables since joins on replicated tables don't require data movement. Replication requires extra storage, though, and isn't practical for large tables. Incorrect Answers

Submitted by miguelv· Mar 6, 2026Design and implement data storage

Question

You are designing a date dimension table in an Azure Synapse Analytics dedicated SQL pool. The date dimension table will be used by all the fact tables. Which distribution type should you recommend to minimize data movement?

Options

AHASH
BREPLICATE
CROUND_ROBIN

How the community answered

(15 responses)

A
13% (2)
B
73% (11)
C
13% (2)

Explanation

A replicated table has a full copy of the table available on every Compute node. Queries run fast on replicated tables since joins on replicated tables don't require data movement. Replication requires extra storage, though, and isn't practical for large tables. Incorrect Answers: C: A round-robin distributed table distributes table rows evenly across all distributions. The assignment of rows to distributions is random. Unlike hash-distributed tables, rows with equal values are not guaranteed to be assigned to the same distribution. As a result, the system sometimes needs to invoke a data movement operation to better organize your data before it can resolve a query. https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data- warehouse-tables-distribute

Topics

#dedicated SQL pool#table distribution#REPLICATE#data movement optimization

Community Discussion

No community discussion yet for this question.

Full DP-300 Practice