The answer is to create a new table with the timestamp as the partition key and copy data there for time-based queries. This works because Azure Table Storage uses the partition key to physically distribute data, and timestamp range queries across partitions are slow since they require a full table scan. By designing a separate table where the timestamp serves as the partition key, you enable efficient, targeted scans across a single partition key range, directly optimizing timestamp queries across partitions. On the DP-900 exam, this tests your understanding of Table Storage’s limited indexing—only the partition key and row key are indexed, so you must design your schema around your query patterns. A common trap is assuming you can add a secondary index or switch to Cosmos DB unnecessarily, but the correct, cost-effective solution is a dedicated table. Memory tip: “Time-based table, time-based key” — if you query by time, make time your partition key.
DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
This DP-900 practice question tests your understanding of describe considerations for working with non-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. 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 application stores millions of small log entries in Azure Table Storage. Queries by partition key and row key are fast, but you also need to query by timestamp across partitions. The query performance is slow. What is the best way to improve query performance?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a new table with the timestamp as the partition key and copy data there for time-based queries.
Creating a separate table with timestamp as the partition key allows efficient range queries across all data. Option A is wrong because indexing options in Table Storage are limited. Option B is wrong because Cosmos DB is more expensive and may not be necessary. Option D is wrong because a secondary index is not supported in Table Storage.
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.
✗
Migrate the data to Azure Cosmos DB and use the SQL API.
Why it's wrong here
This is a valid option but not the best if you want to stay with Table Storage; it also increases cost.
✗
Use Azure Cognitive Search to index the Table Storage data.
Why it's wrong here
Cognitive Search can index but adds complexity and cost; not the most straightforward.
✓
Create a new table with the timestamp as the partition key and copy data there for time-based queries.
Why this is correct
This allows efficient queries by timestamp using partition key design.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add a secondary index on the timestamp column.
Why it's wrong here
Azure Table Storage does not support secondary indexes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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-900 question in full detail.
Identify which DP-900 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Describe considerations for working with non-relational data on Azure — This question tests Describe considerations for working with non-relational data on Azure — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a new table with the timestamp as the partition key and copy data there for time-based queries. — Creating a separate table with timestamp as the partition key allows efficient range queries across all data. Option A is wrong because indexing options in Table Storage are limited. Option B is wrong because Cosmos DB is more expensive and may not be necessary. Option D is wrong because a secondary index is not supported in Table Storage.
What should I do if I get this DP-900 question wrong?
Identify which DP-900 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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-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.