Quick Answer
The answer is the Entity behavior blade. This feature in Microsoft Sentinel is correct because it provides a user-centric investigation workspace that aggregates all incidents, alerts, and activities tied to a specific user account, allowing you to quickly find user incidents without writing custom queries. By selecting a user entity and navigating to the Incidents tab within the blade, you can filter incidents over a defined time range, such as the past week, making it the ideal tool for a SOC analyst needing to identify if a specific user account has been involved in any incidents. On the SC-200 exam, this question tests your understanding of user-focused investigation tools versus generic log search or analytics rule features; a common trap is choosing the “Incidents” page or “Hunting” queries, which lack the direct user-centric aggregation. Memory tip: think “Entity = User, Behavior = History” — the blade shows the user’s full security story in one place.
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.
As a SOC analyst, you need to quickly identify if a specific user account has been involved in any incidents in the past week. Which feature in Microsoft Sentinel allows you to search for user-related incidents?
Incidents blade with time range filter
Why wrong: You can filter by time but not by user entity directly.
Hunting blade with user query
Why wrong: Hunting queries raw events, not incidents.
Entity behavior blade
Entity behavior shows incident history for that entity.
Workbooks with KQL query
Why wrong: Workbooks require manual querying; not a direct feature.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Entity behavior blade
Option C is correct because the Entity behavior blade in Microsoft Sentinel provides a user-centric view that aggregates all incidents, alerts, and activities associated with a specific user account. By selecting a user entity and navigating to the 'Incidents' tab within the blade, you can quickly filter incidents involving that user over a defined time range, such as the past week. This feature is designed specifically for investigating user-related security events without needing to write custom queries.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Incidents blade with time range filter
Why it's wrong here
You can filter by time but not by user entity directly.
Hunting blade with user query
Why it's wrong here
Hunting queries raw events, not incidents.
Entity behavior blade
Why this is correct
Entity behavior shows incident history for that entity.
Related concept
Read the scenario before looking for a memorised answer.
Workbooks with KQL query
Why it's wrong here
Workbooks require manual querying; not a direct feature.
Common exam traps
Microsoft often tests the misconception that the Incidents blade (Option A) is sufficient for user-specific searches, but the trap is that it lacks entity-level filtering, requiring analysts to manually correlate users across incidents, whereas the Entity behavior blade provides a consolidated user-centric view.
Detailed technical explanation
Under the hood, the Entity behavior blade leverages Microsoft Sentinel's UEBA (User and Entity Behavior Analytics) engine, which profiles user activities and correlates them with incidents, alerts, and anomalies. The blade uses a graph-based entity model that links user accounts to related security events, enabling drill-down into timelines and incident associations. In a real-world scenario, a SOC analyst can use this blade to quickly pivot from a compromised user to all associated incidents, reducing mean time to respond (MTTR) without writing KQL.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Manage a security operations environment — study guide chapter
Learn the concepts, then practise the questions
Manage a security operations environment practice questions
Targeted practice on this topic area only
All SC-200 questions
1,639 questions across all exam domains
Microsoft Security Operations Analyst SC-200 study guide
Full concept coverage aligned to exam objectives
SC-200 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SC-200 questions linked to Manage a security operations environment.
Practise SC-200 questions linked to Respond to security incidents.
Practise SC-200 questions linked to Perform threat hunting.
Practise SC-200 questions linked to Mitigate threats using Microsoft Defender XDR.
Practise SC-200 questions linked to Mitigate threats using Microsoft Defender for Cloud.
Practise SC-200 questions linked to Mitigate threats using Microsoft Sentinel.
Practise SC-200 questions linked to SC-200 fundamentals.
Practise SC-200 questions linked to SC-200 scenario.
Practise SC-200 questions linked to SC-200 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Manage a security operations environment — This question tests Manage a security operations environment — Read the scenario before looking for a memorised answer..
The correct answer is: Entity behavior blade — Option C is correct because the Entity behavior blade in Microsoft Sentinel provides a user-centric view that aggregates all incidents, alerts, and activities associated with a specific user account. By selecting a user entity and navigating to the 'Incidents' tab within the blade, you can quickly filter incidents involving that user over a defined time range, such as the past week. This feature is designed specifically for investigating user-related security events without needing to write custom queries.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Keep practising
Last reviewed: Jun 30, 2026
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.