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…

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…

Submitted by yuriko_h· Mar 30, 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

(41 responses)

A
15% (6)
B
78% (32)
C
7% (3)

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: A: A hash distributed table is designed to achieve high performance for queries on large tables. C: A round-robin table distributes table rows evenly across all distributions. The rows are distributed randomly. Loading data into a round-robin table is fast. Keep in mind that queries can require more data movement than the other distribution methods. https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data- warehouse-tables-overview

Topics

#REPLICATE distribution#date dimension#Synapse SQL pool#data movement optimization

Community Discussion

No community discussion yet for this question.

Full DP-203 Practice