Quick Answer
The correct answer is to create a composite index on (status ASC, timestamp ASC) and choose a partition key that ensures even distribution. This works because Azure Cosmos DB Core (SQL) API composite indexes are purpose-built for queries that combine a filter on one field with a sort on another, allowing the query engine to perform a single index seek rather than a costly cross-partition scan or in-memory sort. On the DP-203 exam, this scenario tests your understanding of how composite indexes optimize ORDER BY with WHERE clauses, and a common trap is assuming a single-field index on status alone will suffice—it won’t, because the sort on timestamp still requires a separate operation. Remember the memory tip: “Filter first, sort second—composite index is your friend.”
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 stores JSON documents in Azure Cosmos DB Core (SQL) API. You need to improve query performance for a common filter on the 'status' field and a sort on 'timestamp'. Which three actions should you take?
Denormalize the status field into a separate container
Why wrong: Unnecessary complexity; composite index is sufficient.
Disable indexing on the timestamp field
Why wrong: Sorting requires indexing on that field.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Create a composite index on (status, timestamp)
A composite index on (status, timestamp) is correct because Azure Cosmos DB Core (SQL) API uses composite indexes to efficiently support queries with multiple filter and sort conditions. This index allows the query engine to first filter on the 'status' field and then sort by 'timestamp' in a single index seek, avoiding a full scan or in-memory sort. Without this composite index, the query would require a cross-partition scan or an expensive sort operation, degrading performance.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Denormalize the status field into a separate container
Why it's wrong here
Unnecessary complexity; composite index is sufficient.
Disable indexing on the timestamp field
Why it's wrong here
Sorting requires indexing on that field.
Option-by-option analysis
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.
Why this is wrong here
Unnecessary complexity; composite index is sufficient.
Why this is wrong here
Sorting requires indexing on that field.
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?”
Common exam traps
The trap here is that candidates may think increasing RU/s (Option B) or disabling indexing (Option E) are sufficient fixes, but the core issue is the lack of an appropriate composite index to support the combined filter and sort, which is a common DP-203 exam pattern for Cosmos DB query optimization.
Detailed technical explanation
Under the hood, Azure Cosmos DB composite indexes store concatenated keys in a B-tree structure, enabling the query engine to perform index seeks for equality filters on the leading property and range/sort on the trailing property. A real-world scenario is a logging system where you filter by 'status' (e.g., 'Error') and sort by 'timestamp' descending; without the composite index, the RU cost can spike by 10x or more due to cross-partition fan-out and sorting. Additionally, the composite index must be explicitly defined in the indexing policy, as Cosmos DB does not automatically create multi-property indexes.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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
846 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise DP-203 questions linked to Secure, monitor, and optimize data storage and data processing.
Practise DP-203 questions linked to Design and develop data processing.
Practise DP-203 questions linked to Design and implement data security.
Practise DP-203 questions linked to Monitor and optimize data storage and processing.
Practise DP-203 questions linked to Design and implement data storage.
Practise DP-203 questions linked to Develop data processing.
Practise DP-203 questions linked to DP-203 fundamentals.
Practise DP-203 questions linked to DP-203 scenario.
Practise DP-203 questions linked to DP-203 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
The correct answer is: Create a composite index on (status, timestamp) — A composite index on (status, timestamp) is correct because Azure Cosmos DB Core (SQL) API uses composite indexes to efficiently support queries with multiple filter and sort conditions. This index allows the query engine to first filter on the 'status' field and then sort by 'timestamp' in a single index seek, avoiding a full scan or in-memory sort. Without this composite index, the query would require a cross-partition scan or an expensive sort operation, degrading performance.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Last reviewed: Jun 11, 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.