The correct answer is to modify the KQL query to exclude events from a list of known administrative user accounts or IP addresses. This approach directly addresses the root cause of the false positives by filtering out legitimate administrative actions that are incorrectly triggering the privilege escalation rule, allowing the detection logic to focus on truly anomalous behavior from non-admin users. On the SC-200 exam, this scenario tests your ability to tune analytics rules by refining the underlying KQL logic rather than adjusting operational settings like frequency or suppression, which would either miss real threats or delay detection. A common trap is choosing suppression, but that only hides alerts without fixing the detection gap, while query tuning preserves detection integrity for other users. Remember the mnemonic: "Query first, suppress last" to prioritize precision over post-processing.
SC-200 Manage a security operations environment Practice Question
This SC-200 practice question tests your understanding of manage a security operations environment. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 organization has a Microsoft Sentinel workspace that ingests data from Microsoft 365 Defender (Defender for Endpoint, Office 365, Identity, Cloud Apps). You have configured a scheduled analytics rule to detect possible privilege escalation based on user activity. The rule runs every 5 minutes and looks at the last 5 minutes of data. Recently, the rule has been generating a high number of false positives. You analyze the alerts and find that they are triggered by legitimate administrative actions. You need to reduce false positives without completely disabling the rule. The rule uses a KQL query that joins the IdentityLogonEvents and CloudAppEvents tables. What should you do?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Modify the KQL query to exclude events from a list of known administrative user accounts or IP addresses.
Option C is correct because tuning the KQL query to exclude known administrative accounts or actions is the best way to reduce false positives. Option A is wrong because increasing the frequency would not reduce false positives. Option B is wrong because suppression can cause missed detections for other users. Option D is wrong because reducing lookback may miss legitimate events.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Increase the rule's run frequency to every 30 minutes.
Why it's wrong here
Frequency does not affect false positives; it only changes how often the rule runs.
✗
Reduce the query's lookback period to 1 minute.
Why it's wrong here
Shorter lookback may miss legitimate events and does not address false positives.
✓
Modify the KQL query to exclude events from a list of known administrative user accounts or IP addresses.
Why this is correct
Excluding known admins reduces false positives while retaining detection for others.
Related concept
Authentication checks who the user is.
✗
Add an incident suppression rule that closes incidents from known admin accounts.
Why it's wrong here
Suppression can hide true positives for those accounts.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SC-200 questions on access control and AAA configuration.
Manage a security operations environment — This question tests Manage a security operations environment — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Modify the KQL query to exclude events from a list of known administrative user accounts or IP addresses. — Option C is correct because tuning the KQL query to exclude known administrative accounts or actions is the best way to reduce false positives. Option A is wrong because increasing the frequency would not reduce false positives. Option B is wrong because suppression can cause missed detections for other users. Option D is wrong because reducing lookback may miss legitimate events.
What should I do if I get this SC-200 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related SC-200 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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.