DP-203 Partition table by date in Azure SQL Practice Question
You need to partition a large Azure SQL Database table by date to improve query performance and manageability. Which partitioning strategy should you use?
⚠ Common exam trap
A common mix-up: candidates confuse `RANGE LEFT` and `RANGE RIGHT`, mistakenly thinking `LEFT` is the default or more natural for date ranges, when in fact `RANGE RIGHT` is the standard for non-overlapping, sliding-window date partitions.
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 PARTITION FUNCTION myDateRange (datetime2) AS RANGE RIGHT FOR VALUES ('2023-01-01', '2023-02-01', ...)
`RANGE RIGHT` ensures that each boundary value belongs to the right partition, which is the standard approach for date-based partitioning. This means values less than '2023-01-01' go into the first partition, values >= '2023-01-01' and < '2023-02-01' go into the second, and so on, aligning with typical date range queries and simplifying partition management (e.g., switching out old partitions).
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
CREATE PARTITION FUNCTION myDateRange (datetime2) AS RANGE LEFT FOR VALUES ('2023-01-01', '2023-02-01', ...)
Why it's wrong here
RANGE LEFT includes the boundary value in the left partition, which can lead to uneven data distribution.
- ✗
Use Azure SQL Database automatic partitioning feature
Why it's wrong here
Azure SQL Database does not have automatic partitioning; you must create it manually.
- ✗
Apply a clustered columnstore index with partitioning
Why it's wrong here
Columnstore indexes are for analytics, not the primary partitioning mechanism.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The DP-203 exam frequently reuses these exact scenarios with slightly different constraints.
✓CREATE PARTITION FUNCTION myDateRange (datetime2) AS RANGE RIGHT FOR VALUES ('2023-01-01', '2023-02-01', ...)Correct answer▾
✗CREATE PARTITION FUNCTION myDateRange (datetime2) AS RANGE LEFT FOR VALUES ('2023-01-01', '2023-02-01', ...)Wrong answer — click to see why▾
Why this is wrong here
RANGE LEFT includes the boundary value in the left partition, which can lead to uneven data distribution.
✗Use Azure SQL Database automatic partitioning featureWrong answer — click to see why▾
Why this is wrong here
Azure SQL Database does not have automatic partitioning; you must create it manually.
✗Apply a clustered columnstore index with partitioningWrong answer — click to see why▾
Why this is wrong here
Columnstore indexes are for analytics, not the primary partitioning mechanism.
Analysis generated from the official DP-203blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
This DP-203 question is part of Courseiva's 760-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.