- A
Repartition the table by OrderStatus
Why wrong: Repartitioning by status could cause data skew and does not replace partitioning by month.
- B
Create a non-clustered columnstore index on OrderStatus
A non-clustered columnstore index on OrderStatus allows efficient filtering.
- C
Change the distribution key to include OrderStatus
Why wrong: Changing distribution key would require rebuilding the table and may not improve status queries.
- D
Create a materialized view that aggregates by OrderStatus and month
Why wrong: A materialized view could help but is overkill if indexing solves the problem.
Question 810 of 851
DP-203 Design and implement data storage Practice Question
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.
Your company uses Azure Synapse Analytics for its enterprise data warehouse. The main fact table, OrdersFact, is distributed using hash on OrderID. It has 10 billion rows. The table is partitioned by month. Recently, the data engineering team added a new column 'OrderStatus' that is used in many queries with filters like 'WHERE OrderStatus = 'Shipped''. These queries are scanning the entire table because the partition pruning is not effective. You need to improve query performance for these status-based queries without redesigning the entire table. What should you do?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a non-clustered columnstore index on OrderStatus
Creating a non-clustered columnstore index on OrderStatus allows SQL Server to perform batch mode processing and predicate pushdown, enabling efficient rowgroup elimination without requiring a full table scan. This index stores OrderStatus in a compressed, columnar format that can be quickly filtered, and it does not require redesigning the existing hash distribution or monthly partitioning.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Repartition the table by OrderStatus
Why it's wrong here
Repartitioning by status could cause data skew and does not replace partitioning by month.
- ✓
Create a non-clustered columnstore index on OrderStatus
Why this is correct
A non-clustered columnstore index on OrderStatus allows efficient filtering.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Change the distribution key to include OrderStatus
Why it's wrong here
Changing distribution key would require rebuilding the table and may not improve status queries.
- ✗
Create a materialized view that aggregates by OrderStatus and month
Why it's wrong here
A materialized view could help but is overkill if indexing solves the problem.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse partitioning with indexing, assuming that repartitioning by the filter column (OrderStatus) will solve the scan problem, but in a columnstore environment, a non-clustered columnstore index is the correct way to enable efficient predicate filtering without altering the physical table design.
Detailed technical explanation
How to think about this question
Non-clustered columnstore indexes (NCCI) store data in column segments that are compressed and organized into rowgroups; when a query filters on a column like OrderStatus, the NCCI can perform segment elimination by reading only the rowgroups that contain matching values, drastically reducing I/O. In Azure Synapse, columnstore indexes also support batch mode execution, which processes rows in chunks of ~900 rows, improving CPU efficiency for large scans. A key nuance is that the NCCI must be created on the entire table (not just a partition) to enable full rowgroup elimination across all partitions.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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. 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
Got this wrong? Here's your next step.
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
851 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
Related DP-203 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Secure, monitor, and optimize data storage and data processing practice questions
Practise DP-203 questions linked to Secure, monitor, and optimize data storage and data processing.
Design and develop data processing practice questions
Practise DP-203 questions linked to Design and develop data processing.
Design and implement data security practice questions
Practise DP-203 questions linked to Design and implement data security.
Monitor and optimize data storage and processing practice questions
Practise DP-203 questions linked to Monitor and optimize data storage and processing.
Design and implement data storage practice questions
Practise DP-203 questions linked to Design and implement data storage.
Develop data processing practice questions
Practise DP-203 questions linked to Develop data processing.
DP-203 fundamentals practice questions
Practise DP-203 questions linked to DP-203 fundamentals.
DP-203 scenario practice questions
Practise DP-203 questions linked to DP-203 scenario.
DP-203 troubleshooting practice questions
Practise DP-203 questions linked to DP-203 troubleshooting.
Practice this exam
Start a free DP-203 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DP-203 question test?
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a non-clustered columnstore index on OrderStatus — Creating a non-clustered columnstore index on OrderStatus allows SQL Server to perform batch mode processing and predicate pushdown, enabling efficient rowgroup elimination without requiring a full table scan. This index stores OrderStatus in a compressed, columnar format that can be quickly filtered, and it does not require redesigning the existing hash distribution or monthly partitioning.
What should I do if I get this DP-203 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
Keep practising
More DP-203 practice questions
- You are designing a data storage solution for IoT sensor data. The data is written thousands of times per second and req…
- A data processing job in Azure Synapse Analytics writes results to a table in the dedicated SQL pool. After a failure, t…
- A multinational corporation uses Azure Data Lake Storage Gen2 to store petabytes of parquet files partitioned by date an…
- A company ingests streaming data from IoT devices into Azure Event Hubs. The data must be processed in near real-time to…
- Which THREE factors should be considered when choosing between Azure Stream Analytics and Azure Databricks for a real-ti…
- You are designing a data lake on Azure Data Lake Storage Gen2. The data will be used by both batch processing (Spark) an…
Last reviewed: Jul 4, 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.