Quick Answer
The answer is to hash-distribute the fact table on CustomerID and partition on OrderDate. Hash distribution on the join key ensures that rows with the same CustomerID are co-located on the same distribution node, eliminating costly data movement during joins, while partitioning on the filter key OrderDate enables partition elimination to drastically reduce the data scanned for date-range queries. This design directly addresses the core DP-203 exam objective of optimizing large fact tables in Azure Synapse Analytics, where the common trap is choosing round-robin distribution (which scatters data randomly) or forgetting to partition on the filter column. A reliable memory tip is “Hash the join, partition the filter”—if you remember that hash distribution handles joins and partitioning handles filters, you’ll avoid the mistake of reversing the two.
This DP-203 practice question tests your understanding of design and implement data storage. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company is migrating its on-premises SQL Server data warehouse to Azure Synapse Analytics. They have a fact table with 2 billion rows and 30 columns. The table is frequently joined on CustomerID and filtered on OrderDate. What is the recommended table design?
Hash-distribute on CustomerID and partition on OrderDate
Optimizes joins and filtering.
Replicate the table to all nodes
Why wrong: Table too large to replicate.
Round-robin distribution with partitions on OrderDate
Why wrong: Joins will be inefficient.
Hash-distribute on OrderDate and partition on CustomerID
Why wrong: Partition on CustomerID not beneficial for date filtering.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Hash-distribute on CustomerID and partition on OrderDate
Hash-distributing the fact table on CustomerID ensures that rows with the same CustomerID are co-located on the same distribution node, which makes joins on CustomerID efficient by avoiding data movement. Partitioning on OrderDate enables partition elimination when filtering by date, reducing the amount of data scanned. This combination optimizes both the join and filter operations for a large fact table in Azure Synapse Analytics.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Hash-distribute on CustomerID and partition on OrderDate
Why this is correct
Optimizes joins and filtering.
Related concept
Read the scenario before looking for a memorised answer.
Replicate the table to all nodes
Why it's wrong here
Table too large to replicate.
Round-robin distribution with partitions on OrderDate
Why it's wrong here
Joins will be inefficient.
Hash-distribute on OrderDate and partition on CustomerID
Why it's wrong here
Partition on CustomerID not beneficial for date filtering.
Common exam traps
The trap here is that candidates often confuse the roles of distribution and partitioning, thinking that partitioning on the join column or distributing on the filter column will improve performance, when in fact distribution should align with join keys and partitioning with filter keys.
Detailed technical explanation
In Azure Synapse, hash distribution uses a deterministic hash function on the distribution column to assign rows to one of 60 distributions, ensuring co-location for equi-joins. Partitioning on OrderDate allows partition pruning at the storage layer, where only relevant partitions are read during queries with date filters. A real-world scenario is a sales fact table where daily order data is loaded and queried by month; partitioning by month or year can dramatically reduce I/O and improve query response times.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design and implement data storage — study guide chapter
Learn the concepts, then practise the questions
Design and implement data storage practice questions
Targeted practice on this topic area only
All DP-203 questions
846 questions across all exam domains
Microsoft Azure Data Engineer Associate DP-203 study guide
Full concept coverage aligned to exam objectives
DP-203 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise DP-203 questions linked to Secure, monitor, and optimize data storage and data processing.
Practise DP-203 questions linked to Design and develop data processing.
Practise DP-203 questions linked to Design and implement data security.
Practise DP-203 questions linked to Monitor and optimize data storage and processing.
Practise DP-203 questions linked to Design and implement data storage.
Practise DP-203 questions linked to Develop data processing.
Practise DP-203 questions linked to DP-203 fundamentals.
Practise DP-203 questions linked to DP-203 scenario.
Practise DP-203 questions linked to DP-203 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
The correct answer is: Hash-distribute on CustomerID and partition on OrderDate — Hash-distributing the fact table on CustomerID ensures that rows with the same CustomerID are co-located on the same distribution node, which makes joins on CustomerID efficient by avoiding data movement. Partitioning on OrderDate enables partition elimination when filtering by date, reducing the amount of data scanned. This combination optimizes both the join and filter operations for a large fact table in Azure Synapse Analytics.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A financial services company is migrating its data warehouse to Azure Synapse Analytics. They have a star schema with a 10-billion-row fact table and 50 dimension tables. Query performance is critical, and they need to minimize data movement during joins. Which distribution strategy should they use for the fact table?
mediumWhy C: Hash distribution on the most frequently joined dimension key is correct because it co-locates matching rows from the fact and dimension tables on the same compute node, minimizing data movement during joins. For a 10-billion-row fact table, this distribution ensures that the most common join operation is performed locally without shuffling data across nodes, which is critical for query performance in Azure Synapse Analytics.
Keep practising
Last reviewed: Jun 24, 2026
This DP-203 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-203 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.