The answer is that the cmdlet 'Set-AzSentinelSetting' does not exist in the Az module, so the script fails silently or throws an error without applying any changes. This is because Microsoft Sentinel settings, including Anomalies, are managed through the Az.SecurityInsights module, which uses 'Update-AzSentinelSetting' (a preview cmdlet) or the REST API, not a non-existent 'Set' variant. On the SC-200 exam, this question tests your understanding of the correct PowerShell cmdlets for enabling Sentinel features, often trapping candidates who assume a generic 'Set' verb works across all Azure resources. A common memory tip is that for Sentinel settings, you must "Update" rather than "Set" — think of it as updating a dynamic security posture, not setting a static configuration.
SC-200 Manage a security operations environment Practice Question
This SC-200 practice question tests your understanding of manage a security operations environment. 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.
Refer to the exhibit. You are running a PowerShell script to enable the Anomalies setting in Microsoft Sentinel. After running the script, you check the Sentinel settings in the portal and see that Anomalies is still disabled. 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 cmdlet 'Set-AzSentinelSetting' does not exist in the Az module.
The cmdlet 'Set-AzSentinelSetting' does not exist in the official Az.SecurityInsights module. Microsoft Sentinel settings, including Anomalies, are managed via the REST API or the 'Update-AzSentinelSetting' cmdlet (part of the Az.SecurityInsights preview module). Running a non-existent cmdlet would produce an error, not apply any changes, leaving Anomalies disabled in the portal.
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 cmdlet 'Set-AzSentinelSetting' does not exist in the Az module.
Why this is correct
The correct cmdlet is 'Update-AzSentinelSetting' or similar.
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 user does not have Contributor permissions on the workspace.
Why it's wrong here
Permissions are not the issue here.
✗
The script requires the -PassThru parameter to apply changes.
Why it's wrong here
The cmdlet itself is invalid.
✗
The workspace was not retrieved correctly because the name is misspelled.
Why it's wrong here
The name appears correct.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume all Azure PowerShell cmdlets follow the 'Set-*' naming convention, but Microsoft Sentinel settings specifically use 'Update-*' in the Az.SecurityInsights module, leading to the mistaken belief that 'Set-AzSentinelSetting' is valid.
Detailed technical explanation
How to think about this question
Under the hood, Microsoft Sentinel settings like Anomalies are stored as properties of the workspace's 'SecurityInsights' resource provider. The correct PowerShell cmdlet to update them is 'Update-AzSentinelSetting', which calls the REST API endpoint 'Microsoft.SecurityInsights/settings/{settingsName}'. The 'Set-AzSentinelSetting' cmdlet is a common misconception because the Az module uses 'Set-' for many resource types (e.g., Set-AzVm), but for Sentinel settings, the verb is 'Update-'. In a real-world scenario, a script using a non-existent cmdlet would throw a 'CommandNotFoundException', and the administrator would need to install the correct module or use the REST API directly.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-200 question in full detail.
Manage a security operations environment — This question tests Manage a security operations environment — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The cmdlet 'Set-AzSentinelSetting' does not exist in the Az module. — The cmdlet 'Set-AzSentinelSetting' does not exist in the official Az.SecurityInsights module. Microsoft Sentinel settings, including Anomalies, are managed via the REST API or the 'Update-AzSentinelSetting' cmdlet (part of the Az.SecurityInsights preview module). Running a non-existent cmdlet would produce an error, not apply any changes, leaving Anomalies disabled in the portal.
What should I do if I get this SC-200 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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-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.