The correct answer is to create a nonclustered index on the partition key column, such as OrderDate, and include other columns as needed. This works because a clustered columnstore index is optimized for large-scale analytics and compression, not for point lookups or narrow range scans; adding a nonclustered b-tree index on the partition key enables SQL Server to perform an index seek for date-range queries, bypassing the full columnstore scan and dramatically reducing I/O. On the DP-300 exam, this scenario tests your understanding of hybrid workload optimization—balancing analytics with transactional queries on partitioned tables. A common trap is assuming that partitioning alone guarantees fast seeks, but without a supporting nonclustered index, the engine still scans the entire partition. Remember the mnemonic: “Partition for management, index for performance.”
DP-300 Plan and implement data platform resources Practice Question
This DP-300 practice question tests your understanding of plan and implement data platform resources. 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.
You are a database administrator for a large e-commerce company. The company has an Azure SQL Database named 'OrdersDB' in the General Purpose service tier, with a 2 TB database. The database has a table named 'OrderDetails' that contains over 1 billion rows. The table is partitioned by date using a partition function that splits data by month. You notice that queries that filter on a specific date range are performing poorly, and the query plan shows a clustered index scan on the partition column. The table has a clustered columnstore index to support analytics. You need to improve query performance for date-range queries without affecting the analytics workload. 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
✓
Create a nonclustered index on the partition key column (OrderDate) and include other columns as needed.
Option B is correct because creating a nonclustered index on the partition key (OrderDate) allows SQL Server to perform an index seek for date-range queries, avoiding the full clustered columnstore index scan. This index does not interfere with the existing columnstore index, which remains optimal for analytics workloads. The nonclustered index can include additional columns as included columns to cover the query without touching the base table.
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.
✗
Create a new partition scheme with a different partition function.
Why it's wrong here
Partitioning is already by date; changing scheme may not help.
✓
Create a nonclustered index on the partition key column (OrderDate) and include other columns as needed.
Why this is correct
Nonclustered index supports seek for date range queries without affecting columnstore.
Related concept
Read the scenario before looking for a memorised answer.
✗
Rebuild the clustered columnstore index with a different compression setting.
Why it's wrong here
Rebuilding may not change the scan behavior for range queries.
✗
Change the clustered index to a rowstore B-tree index on the partition key.
Why it's wrong here
This would negatively impact analytics queries that benefit from columnstore.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume partitioning alone improves query performance, but without an appropriate index, the query still scans all partitions; they may also mistakenly think rebuilding or changing the clustered index is necessary, ignoring that a nonclustered index can coexist with a columnstore index.
Detailed technical explanation
How to think about this question
A clustered columnstore index stores data in columnar format and is optimized for large scans and aggregations, but it lacks a B-tree structure for efficient point or range seeks. A nonclustered B-tree index on the partition key provides ordered, seekable access for date-range queries, and SQL Server can use index intersection or included columns to avoid key lookups. In real-world scenarios, this hybrid approach is common in Azure SQL Database where transactional and analytical workloads coexist on the same table.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Plan and implement data platform resources — This question tests Plan and implement data platform resources — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a nonclustered index on the partition key column (OrderDate) and include other columns as needed. — Option B is correct because creating a nonclustered index on the partition key (OrderDate) allows SQL Server to perform an index seek for date-range queries, avoiding the full clustered columnstore index scan. This index does not interfere with the existing columnstore index, which remains optimal for analytics workloads. The nonclustered index can include additional columns as included columns to cover the query without touching the base table.
What should I do if I get this DP-300 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 →
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-300 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-300 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.