Answer: replicated

## Analysis of Table Distribution Options in Azure Synapse Analytics For a dimension table under 1 GB that requires **fastest query time** and **minimized data movement**, the **replicated table distribution** is the optimal choice. Here's the detailed reasoning: ### Why Replicated Distribution (Option A) is Correct: 1. **Eliminates Data Movement**: Replicated tables store a full copy of the table on each compute node. When joining this dimension table with fact tables, no data movement is required across nodes since every node already has the complete dimension data. 2. **Optimized for Dimension Tables**: Dimension tables are typically used in star schema designs and are frequently joined with large fact tables. Replicated distribution ensures these joins can be performed locally on each compute node without shuffling data. 3. **Size Consideration**: At less than 1 GB, the table is well within the recommended size limit for replicated tables (generally under 2 GB). This ensures efficient storage utilization across nodes. 4. **Query Performance**: By eliminating cross-node data movement during joins and aggregations, replicated tables provide the fastest query execution for dimension table operations. ### Why Other Options Are Less Suitable: - **Hash Distributed (Option B)**: While excellent for large fact tables, hash distribution would require data movement when joining with other tables that use different distribution keys, contradicting the requirement to minimize data movement. - **Heap (Option C)**: Heap refers to table organization without a clustered index, not a distribution method. This doesn't address the data movement requirement. - **Round-Robin (Option D)**: This distributes data evenly but randomly across nodes, which maximizes data movement during queries since related data isn't co-located, leading to poor join performance. ### Best Practice Alignment: Microsoft's Azure Synapse Analytics best practices specifically recommend using replicated distribution for small dimension tables (typically under 2 GB) to optimize join performance and minimize data movement across the distributed system.

Author: LeetQuiz Editorial Team