The answer is to change the Customer table’s distribution to replicated. This is correct because a replicated table stores a full copy on each compute node, which eliminates data movement during joins with the large, hash-distributed Sales fact table. The poor performance stems from high data movement when joining two hash-distributed tables on different keys, compounded by the 40% data skew on Sales; replication bypasses both issues by ensuring the Customer dimension is locally available on every node. On the DP-203 exam, this scenario tests your understanding of Synapse dedicated SQL pool distribution strategies, specifically when to use replicated versus hash-distributed tables for star schema dimensions. A common trap is to try fixing the skew by changing the Sales distribution key, but that only shifts the skew problem without addressing join movement. Remember the memory tip: “Replicate the small, hash the large—if it moves, replicate the join side.”
DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
This DP-203 practice question tests your understanding of secure, monitor, and optimize data storage and data processing. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
You are a data engineer for a global e-commerce company. The company uses Azure Synapse Analytics dedicated SQL pool for its data warehouse. The environment includes a large fact table 'Sales' distributed by hash on 'CustomerID', and dimension tables 'Customer' (hash-distributed on 'CustomerID') and 'Product' (replicated). Recently, queries that join Sales and Customer are performing poorly. You run a query to check data skew on the Sales table and find that one distribution has 40% more rows than the average. Additionally, the Customer table has high data movement during joins. You need to optimize the performance of these joins. What should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change the distribution of the Customer table to replicated.
Option B is correct because changing the Customer table to replicated distribution eliminates data movement during joins. Option A is wrong because changing the distribution key of Sales to a different column may not solve skew if the key is not the join column. Option C is wrong because round-robin is not suitable for fact tables in star joins. Option D is wrong because increasing DWU may alleviate symptoms but does not fix the root cause of data movement.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Change the distribution of the Customer table to replicated.
Why this is correct
Replicated tables avoid data movement for joins.
Related concept
Static NAT maps one inside address to one outside address.
✗
Increase the data warehouse performance level (DWU) to allocate more resources.
Why it's wrong here
Scaling up does not fix data movement issues.
✗
Change the distribution of the Sales table to round-robin.
Why it's wrong here
Round-robin is not suitable for large fact tables.
✗
Change the distribution key of the Sales table to 'ProductID' to align with the Product table.
Why it's wrong here
Product is replicated, so no alignment needed; skew may remain.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
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. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-203 NAT questions on configuration and troubleshooting.
Secure, monitor, and optimize data storage and data processing — This question tests Secure, monitor, and optimize data storage and data processing — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Change the distribution of the Customer table to replicated. — Option B is correct because changing the Customer table to replicated distribution eliminates data movement during joins. Option A is wrong because changing the distribution key of Sales to a different column may not solve skew if the key is not the join column. Option C is wrong because round-robin is not suitable for fact tables in star joins. Option D is wrong because increasing DWU may alleviate symptoms but does not fix the root cause of data movement.
What should I do if I get this DP-203 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related DP-203 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
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.
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.