SC-200 Kusto Query Language (KQL) Practice Question
This SC-200 practice question tests your understanding of perform threat hunting. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: kusto Query Language (KQL). 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
Refer to the exhibit.
```powershell
$table = "DeviceProcessEvents"
$query = "DeviceProcessEvents | where FileName == 'reg.exe' | project Timestamp, DeviceName, AccountName"
Invoke-AzOperationalInsightsQuery -WorkspaceId $wsId -Query $query
```
Refer to the exhibit. A threat hunter runs this PowerShell script to query Microsoft Sentinel. The script fails with an error stating that the query language is not recognized. What is the most likely cause?
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.
Exhibit
Refer to the exhibit.
```powershell
$table = "DeviceProcessEvents"
$query = "DeviceProcessEvents | where FileName == 'reg.exe' | project Timestamp, DeviceName, AccountName"
Invoke-AzOperationalInsightsQuery -WorkspaceId $wsId -Query $query
```
A
The query contains a reference to a table that does not exist in the workspace.
Correct. The query tries to read from 'DeviceProcessEvents', a table that does not exist in the workspace, causing the error.
B
The cmdlet requires the query to be passed as a script block, not a string.
Why wrong: Incorrect. The cmdlet accepts the query as a string parameter; a script block is not required.
C
The query should use 'search' instead of 'where' for cross-table queries.
Why wrong: Incorrect. The 'search' operator is not needed for cross-table queries; the 'where' operator works fine.
D
The query uses pipe syntax ('|') which is not supported by the PowerShell cmdlet.
Why wrong: Incorrect. Pipe syntax is a core part of KQL and is fully supported by Invoke-AzOperationalInsightsQuery.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The query contains a reference to a table that does not exist in the workspace.
The correct answer is A. The error 'query language not recognized' occurs because the Kusto Query Language (KQL) parser cannot resolve the table 'DeviceProcessEvents' referenced in the query. If the table does not exist in the Log Analytics workspace, the query fails with a 'language not recognized' error because the parser treats the undefined table reference as a syntax or semantic error. Options B, C, and D are incorrect because Invoke-AzOperationalInsightsQuery accepts a string query, 'search' is not required for cross-table queries, and pipe syntax is fully supported in KQL and by the cmdlet.
Key principle: Kusto Query Language (KQL)
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 contains a reference to a table that does not exist in the workspace.
Why this is correct
Correct. The query tries to read from 'DeviceProcessEvents', a table that does not exist in the workspace, causing the error.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Kusto Query Language (KQL)
✗
The cmdlet requires the query to be passed as a script block, not a string.
Why it's wrong here
Incorrect. The cmdlet accepts the query as a string parameter; a script block is not required.
✗
The query should use 'search' instead of 'where' for cross-table queries.
Why it's wrong here
Incorrect. The 'search' operator is not needed for cross-table queries; the 'where' operator works fine.
✗
The query uses pipe syntax ('|') which is not supported by the PowerShell cmdlet.
Why it's wrong here
Incorrect. Pipe syntax is a core part of KQL and is fully supported by Invoke-AzOperationalInsightsQuery.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates may mistakenly attribute the error to PowerShell syntax (option B) or to the use of '|' pipe (option D), but the real issue is that the table referenced in the KQL query does not exist in the workspace.
Detailed technical explanation
How to think about this question
Treat this as a scenario question. Identify the problem, the constraint, and the best action. Then compare each option against those facts.
KKey Concepts to Remember
Kusto Query Language (KQL)
Table reference
Invoke-AzOperationalInsightsQuery
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
Kusto Query Language (KQL)
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. Kusto Query Language (KQL) Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Visual reference
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-200 question in full detail.
Perform threat hunting — This question tests Perform threat hunting — Kusto Query Language (KQL).
What is the correct answer to this question?
The correct answer is: The query contains a reference to a table that does not exist in the workspace. — The correct answer is A. The error 'query language not recognized' occurs because the Kusto Query Language (KQL) parser cannot resolve the table 'DeviceProcessEvents' referenced in the query. If the table does not exist in the Log Analytics workspace, the query fails with a 'language not recognized' error because the parser treats the undefined table reference as a syntax or semantic error. Options B, C, and D are incorrect because Invoke-AzOperationalInsightsQuery accepts a string query, 'search' is not required for cross-table queries, and pipe syntax is fully supported in KQL and by the cmdlet.
What should I do if I get this SC-200 question wrong?
Review kusto Query Language (KQL), then practise related SC-200 questions on the same topic to reinforce the concept.
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?
Kusto Query Language (KQL)
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-200 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-200 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.