The answer is to create a secondary index on the email field. This is correct because Azure Cosmos DB for NoSQL automatically indexes the partition key, but any other field used in a filter—like email—requires a secondary index to avoid a full cross-partition scan. Without it, the query engine must fan out to every physical partition, which is inefficient for occasional lookups. A secondary index, whether a single-field or composite index, enables index-based lookup across all partitions, allowing the query to run quickly without redesigning the data model. On the DP-203 exam, this scenario tests your understanding of indexing strategies for non-partition key queries, a common trap being to assume all fields are automatically indexed or to suggest changing the partition key. Remember the memory tip: “If it’s not the key, index it for speed.”
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 Cosmos DB for NoSQL to store user profiles. The application frequently reads profiles by user ID (the partition key). Occasionally, the application needs to query by email address, which is not part of the partition key. What should you do to optimize the occasional queries by email?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a secondary (composite) index on the email field.
Creating a secondary index on the email field allows Azure Cosmos DB for NoSQL to efficiently serve queries filtering by email without scanning all partitions. Since email is not the partition key, a secondary index (specifically a composite index if needed for multi-field queries, or a single-field index) enables index-based lookup across all physical partitions, optimizing the occasional query without redesigning the data model.
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 secondary (composite) index on the email field.
Why this is correct
A secondary index allows efficient queries on non-partition key fields.
Related concept
Read the scenario before looking for a memorised answer.
✗
Change the partition key to the email field.
Why it's wrong here
This would hurt the primary workload that queries by user ID.
✗
Denormalize the data by storing a copy of the email in the partition key.
Why it's wrong here
Unnecessary if a secondary index exists.
✗
Use the Azure Cosmos DB change feed to maintain a separate container keyed by email.
Why it's wrong here
This adds complexity and latency; a secondary index is simpler.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume a secondary index is unnecessary or that changing the partition key is the only way to optimize non-key queries, but Azure Cosmos DB supports secondary indexes for non-partition key fields, and altering the partition key would disrupt the primary access pattern.
Detailed technical explanation
How to think about this question
Azure Cosmos DB secondary indexes are automatically maintained for all fields by default unless explicitly excluded via indexing policy. For queries on non-partition key fields, the index allows the query engine to route to the relevant physical partitions efficiently, but if the query does not include the partition key, it still requires a fan-out across all partitions (though the index reduces the data scanned per partition). In a real-world scenario, if the email query is very rare, a secondary index is cost-effective; however, if it becomes frequent, consider using a materialized view via change feed to avoid cross-partition overhead.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
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 secondary (composite) index on the email field. — Creating a secondary index on the email field allows Azure Cosmos DB for NoSQL to efficiently serve queries filtering by email without scanning all partitions. Since email is not the partition key, a secondary index (specifically a composite index if needed for multi-field queries, or a single-field index) enables index-based lookup across all physical partitions, optimizing the occasional query without redesigning the data model.
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 →
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-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.