The answer is that the KQL query uses the lowercase string 'high' when the field stores the value as 'High' with a capital H. This is the most likely reason your KQL query for high-risk sign-ins returns no results, because KQL string comparisons are case-sensitive by default, so the filter 'where RiskLevelDuringSignIn == "high"' will not match any rows where the actual stored value is "High". On the Microsoft Cybersecurity Architect exam, this tests your understanding of KQL schema and data normalization—a common trap is assuming string fields are case-insensitive or that values are stored exactly as you type them. A reliable memory tip is to always check the actual field values by running a simple query without filters first, then copy the exact casing from the results.
SC-100 Practice Question: Design security solutions for applications and data
This SC-100 practice question tests your understanding of design security solutions for applications and data. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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
SELECT
TimeGenerated,
UserPrincipalName,
AppDisplayName,
RiskLevelDuringSignIn,
RiskLevelAggregated
FROM SigninLogs
| where TimeGenerated > ago(1d)
| where RiskLevelDuringSignIn == "high"
Refer to the exhibit. A security analyst runs this KQL query in Microsoft Sentinel to find high-risk sign-ins. The query returns no results, but they know there were high-risk sign-ins. What is the most likely reason?
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 value 'high' should be 'High' (capitalized)
The query uses 'RiskLevelDuringSignIn' and 'RiskLevelAggregated' but filters on 'RiskLevelDuringSignIn'. However, in the schema, the field is named 'RiskLevelDuringSignIn' correctly. But the query uses 'where RiskLevelDuringSignIn == "high"' but the field may store values as 'High' (capitalized). Option C is correct. Option A is wrong because the field exists. Option B is wrong because the query is valid syntax. Option D is wrong because the time range is last 1 day.
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 value 'high' should be 'High' (capitalized)
Why this is correct
Risk level values are case-sensitive and stored as 'High'.
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 query uses double equals instead of single equals
Why it's wrong here
Double equals is correct for equality in KQL.
✗
The field name is incorrect; it should be 'RiskLevel'
Why it's wrong here
The correct field name is RiskLevelDuringSignIn.
✗
The time range should be 'ago(7d)'
Why it's wrong here
If sign-ins occurred in last 1 day, the time range is fine.
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 SC-100 question in full detail.
Identify which SC-100 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.
Design security solutions for applications and data — This question tests Design security solutions for applications and data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The value 'high' should be 'High' (capitalized) — The query uses 'RiskLevelDuringSignIn' and 'RiskLevelAggregated' but filters on 'RiskLevelDuringSignIn'. However, in the schema, the field is named 'RiskLevelDuringSignIn' correctly. But the query uses 'where RiskLevelDuringSignIn == "high"' but the field may store values as 'High' (capitalized). Option C is correct. Option A is wrong because the field exists. Option B is wrong because the query is valid syntax. Option D is wrong because the time range is last 1 day.
What should I do if I get this SC-100 question wrong?
Identify which SC-100 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 SC-100 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 SC-100 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.