- A
Create a clustered index on OrderDate and a non-clustered index on OrderStatus
Why wrong: Changing the clustered index to OrderDate might help with range queries but could impact insert performance and other queries that use the primary key. Also, the sort order is not optimized.
- B
Create a non-clustered index on (OrderDate, OrderStatus) and keep the existing clustered index on OrderID
Why wrong: This index covers the filter but does not specify descending order for OrderDate, so the query may still need to sort the results.
- C
Create a clustered index on OrderID and a non-clustered index on (OrderStatus, OrderDate)
Why wrong: Having OrderStatus first in the index does not help with filtering on OrderDate, as the index cannot be used efficiently for the date range.
- D
Create a non-clustered index on (OrderDate DESC, OrderStatus) and keep the existing clustered index on OrderID
This index is a covering index that supports the filter on both columns and the sort order, allowing the query to retrieve data without additional sorting.
DP-900 Practice Question: Identify considerations for relational data on Azure
This DP-900 practice question tests your understanding of identify considerations for relational data on azure. 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. A key principle to apply: non-clustered indexes can include sort order specifications (ASC/DESC) for columns.. 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 uses Azure SQL Database for an e-commerce application. The Orders table has millions of rows. Queries frequently filter on OrderDate and OrderStatus, and sort by OrderDate descending. Which indexing strategy will most improve query performance?
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 index on (OrderDate DESC, OrderStatus) and keep the existing clustered index on OrderID
Option D creates a covering index for the most common query pattern: filtering on OrderDate and OrderStatus, and sorting by OrderDate descending. By specifying DESC in the index key, the index is ordered in the same direction as the sort, allowing SQL Server to avoid a sort operation and retrieve rows in order directly from the index. This non-clustered index can satisfy the query entirely without touching the clustered index (OrderID), reducing I/O and improving performance.
Key principle: Non-clustered indexes can include sort order specifications (ASC/DESC) for columns.
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 clustered index on OrderDate and a non-clustered index on OrderStatus
Why it's wrong here
Changing the clustered index to OrderDate might help with range queries but could impact insert performance and other queries that use the primary key. Also, the sort order is not optimized.
- ✗
Create a non-clustered index on (OrderDate, OrderStatus) and keep the existing clustered index on OrderID
Why it's wrong here
This index covers the filter but does not specify descending order for OrderDate, so the query may still need to sort the results.
- ✗
Create a clustered index on OrderID and a non-clustered index on (OrderStatus, OrderDate)
Why it's wrong here
Having OrderStatus first in the index does not help with filtering on OrderDate, as the index cannot be used efficiently for the date range.
- ✓
Create a non-clustered index on (OrderDate DESC, OrderStatus) and keep the existing clustered index on OrderID
Why this is correct
This index is a covering index that supports the filter on both columns and the sort order, allowing the query to retrieve data without additional sorting.
Related concept
Non-clustered indexes can include sort order specifications (ASC/DESC) for columns.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume any index on the filtered columns will help, but they overlook the importance of index key order matching the sort direction (DESC) to avoid a sort operation, which is a common performance pitfall in Azure SQL Database.
Detailed technical explanation
How to think about this question
In SQL Server, when a query includes an ORDER BY clause, the query optimizer can avoid a sort if the index is ordered in the same direction as the sort. A non-clustered index with (OrderDate DESC, OrderStatus) stores rows in descending order by OrderDate, so scanning the index in order directly returns sorted results. Additionally, if the index is covering (includes all columns needed), it eliminates key lookups to the clustered index, which is critical for tables with millions of rows to minimize logical reads.
KKey Concepts to Remember
- Non-clustered indexes can include sort order specifications (ASC/DESC) for columns.
- Matching index sort order to query sort order eliminates the need for additional sorting.
- Leading columns in a composite index are crucial for efficient range and equality filtering.
- A covering index includes all columns needed by the query's SELECT, WHERE, and ORDER BY clauses.
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
Non-clustered indexes can include sort order specifications (ASC/DESC) for columns.
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. Non-clustered indexes can include sort order specifications (ASC/DESC) for columns. 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.
Review non-clustered indexes can include sort order specifications (ASC/DESC) for columns., then practise related DP-900 questions on the same topic to reinforce the concept.
- →
Identify considerations for relational data on Azure — study guide chapter
Learn the concepts, then practise the questions
- →
Identify considerations for relational data on Azure practice questions
Targeted practice on this topic area only
- →
All DP-900 questions
982 questions across all exam domains
- →
Microsoft Azure Data Fundamentals DP-900 study guide
Full concept coverage aligned to exam objectives
- →
DP-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DP-900 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Describe core data concepts practice questions
Practise DP-900 questions linked to Describe core data concepts.
Describe an analytics workload on Azure practice questions
Practise DP-900 questions linked to Describe an analytics workload on Azure.
Identify considerations for relational data on Azure practice questions
Practise DP-900 questions linked to Identify considerations for relational data on Azure.
Describe considerations for working with non-relational data on Azure practice questions
Practise DP-900 questions linked to Describe considerations for working with non-relational data on Azure.
DP-900 fundamentals practice questions
Practise DP-900 questions linked to DP-900 fundamentals.
DP-900 scenario practice questions
Practise DP-900 questions linked to DP-900 scenario.
DP-900 troubleshooting practice questions
Practise DP-900 questions linked to DP-900 troubleshooting.
Practice this exam
Start a free DP-900 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-900 question test?
Identify considerations for relational data on Azure — This question tests Identify considerations for relational data on Azure — Non-clustered indexes can include sort order specifications (ASC/DESC) for columns..
What is the correct answer to this question?
The correct answer is: Create a non-clustered index on (OrderDate DESC, OrderStatus) and keep the existing clustered index on OrderID — Option D creates a covering index for the most common query pattern: filtering on OrderDate and OrderStatus, and sorting by OrderDate descending. By specifying DESC in the index key, the index is ordered in the same direction as the sort, allowing SQL Server to avoid a sort operation and retrieve rows in order directly from the index. This non-clustered index can satisfy the query entirely without touching the clustered index (OrderID), reducing I/O and improving performance.
What should I do if I get this DP-900 question wrong?
Review non-clustered indexes can include sort order specifications (ASC/DESC) for columns., then practise related DP-900 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Non-clustered indexes can include sort order specifications (ASC/DESC) for columns.
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 →
Last reviewed: Jun 11, 2026
This DP-900 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-900 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.