The correct answer is that the state filter is case-sensitive, causing the query to return mismatched or minimal results. In KQL, string comparisons are case-sensitive by default, so filtering for 'TEXAS' will only match rows where the state value is stored exactly as 'TEXAS'—if the actual data uses 'Texas' or 'tx', the filter silently fails, returning few or no rows. This is a common trap on the Microsoft Azure Data Fundamentals DP-900 exam, which tests your understanding of how KQL handles data types and operators; the exam often presents a scenario where a filter appears correct but yields unexpected counts due to case sensitivity. A key memory tip is to always use the `==` operator with exact casing or apply the `tolower()` function to normalize both sides of the comparison, ensuring your filters match the stored data.
DP-900 Describe core data concepts Practice Question
This DP-900 practice question tests your understanding of describe core data concepts. Examine the command output carefully: the correct answer depends on what the output actually shows, not on general recall alone. 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.
Exhibit
{
"query": "StormEvents | where State == 'TEXAS' | summarize Count = count() by EventType | order by Count desc | take 5"
}
Refer to the exhibit. You are analyzing storm event data in Azure Data Explorer. The KQL query returns the top 5 event types by count in Texas. However, the results show event types with very low counts (e.g., 'Volcanic Ash' with 2 events). What is the most likely reason for this?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The state filter is case-sensitive and the actual state value differs.
Option B is correct because the StormEvents sample table contains data from multiple states, but the filter for 'TEXAS' may be case-sensitive or the state might be stored as 'Texas' or 'tx'. If the case does not match exactly, the filter returns few or no rows, leading to unexpected results. Option A is wrong because the 'take' operator limits rows, not aggregates. Option C is wrong because summarizing by EventType should work regardless of state. Option D is wrong because the query is syntactically correct.
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.
✗
The query has a syntax error.
Why it's wrong here
The query is valid.
✗
The 'take' operator limits the number of events, not the number of types.
Why it's wrong here
'take' returns up to 5 rows after aggregation.
✓
The state filter is case-sensitive and the actual state value differs.
Why this is correct
KQL is case-sensitive; 'TEXAS' may not match 'Texas'.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The 'summarize' operator cannot be used with 'where'.
Why it's wrong here
They can be combined.
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 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-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 core data concepts — This question tests Describe core data concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The state filter is case-sensitive and the actual state value differs. — Option B is correct because the StormEvents sample table contains data from multiple states, but the filter for 'TEXAS' may be case-sensitive or the state might be stored as 'Texas' or 'tx'. If the case does not match exactly, the filter returns few or no rows, leading to unexpected results. Option A is wrong because the 'take' operator limits rows, not aggregates. Option C is wrong because summarizing by EventType should work regardless of state. Option D is wrong because the query is syntactically correct.
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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.