SC-200 Practice Test

Exam SC-200: Microsoft Certified: Security Operations Analyst Associate

SC-200 overview

  • 200 practice questions
  • 33 flashcards
  • 3 study guide topics
  • 37 key terms

What you'll study

  • Manage a security operations environment
  • Respond to security incidents
  • Perform threat hunting

The Microsoft Certified: Security Operations Analyst Associate credential is an intermediate-level, Azure-focused certification for security professionals who investigate, search for, and mitigate threats using Microsoft Sentinel, Microsoft Defender for Cloud, and Microsoft 365 Defender. Microsoft positions the role around reducing organizational risk through triage, incident response, threat hunting, and detection engineering, working across Microsoft Defender XDR, Microsoft Sentinel, Microsoft Entra ID, Microsoft Purview, and Defender for Cloud workload protections in multi-cloud and on-premises environments. Candidates should already be familiar with Microsoft security, compliance, and identity solutions; Microsoft 365; Azure cloud services; AI agents and Copilots; and Windows, Linux, and mobile operating systems. The exam assesses three areas: managing a security operations environment, responding to security incidents, and performing threat hunting. It is proctored, lasts 100 minutes, and may include interactive components, so build hands-on familiarity with portal workflows and KQL rather than memorizing definitions. Microsoft publishes an exam study guide and prep videos, and a practice assessment is available through AI Skills Navigator; the older Microsoft Learn practice assessment is no longer updated. Certification renewal is required every 12 months and can be completed at no cost by passing an online assessment on Microsoft Learn. Always confirm current logistics on Microsoft's official exam page before scheduling.

Common mistakes

Treating Microsoft Sentinel analytics rules as fire-and-forget, so candidates cannot explain why a given incident was or was not generated, or which entity mappings feed the incident.

Candidates memorize the rule-creation wizard screens but never learn how entity mapping, alert grouping, and rule scheduling interact, so they cannot reason about missed or merged detections.

What to do instead

Before the exam, build a small lab tenant and create one scheduled rule, deliberately vary the query window, entity mapping, and incident grouping settings, then observe the resulting incident in the queue. Practice stating aloud which settings produced the observed behavior.

Confusing data connectors with data collection rules (DCRs) and diagnostic settings, and picking a connector when the scenario asks how to route or transform events.

All three appear in ingestion discussions and the portal surfaces overlap, so candidates default to 'connector' for every ingestion question.

What to do instead

Map each tool to its job: connectors bring data in from sources, DCRs define collection and transformation for Azure Monitor/AMA pipelines, and diagnostic settings route platform logs to a destination. Drill with scenario stems that name the source and the required transformation.

Ignoring role-based access control and Microsoft Sentinel roles when answering workspace or incident-handling questions, assuming Contributor is always sufficient.

Candidates focus on features and skip the permissions layer, so they miss questions where least privilege or a specific Sentinel role is the deciding factor.

What to do instead

Study the Sentinel role set and the Azure RBAC roles relevant to Log Analytics workspaces, then practice matching a task (triage, automation runbook execution, playbook deployment) to the minimum role that permits it.

Selecting a playbook action that requires a connection or permission the scenario does not grant, such as assuming a playbook can act on a resource without a managed identity or API connection.

Candidates learn playbook triggers but not the authentication and connector prerequisites, so they choose an automation that would fail at runtime.

What to do instead

For each common playbook pattern (block user, isolate device, post to Teams, enrich with threat intel), write down the required connector, identity, and permission. Review that list before answering automation questions.

Misclassifying incident severity and status transitions, for example closing an incident as Resolved without addressing the classification, or treating 'New' and 'Active' as interchangeable.

The incident lifecycle fields look cosmetic, so candidates skim them and pick the wrong state for a described workflow.

What to do instead

Learn the incident state model and the classification options, then walk through a full lifecycle in the portal: assign, set to Active, add a comment, resolve with a classification and reason. Note which fields are mandatory at each step.

Answering containment questions with the most aggressive action available (for example, full device isolation or account deletion) when the scenario calls for a proportionate first step.

Candidates equate 'respond' with 'act hard', and exam stems often describe a suspicious but unconfirmed signal where a softer action is correct.

What to do instead

Practice ranking response actions by impact: investigate and collect evidence, then restrict, then isolate, then remediate. For each scenario, justify why the chosen action is the least disruptive step that contains the confirmed risk.

Skipping evidence gathering and chain-of-custody considerations, jumping straight to remediation and losing the ability to answer questions about investigation packages or evidence preservation.

Remediation feels like the satisfying end of an incident, so candidates underweight the investigative steps that precede it.

What to do instead

Rehearse a standard incident sequence: confirm scope, collect and preserve evidence, contain, eradicate, recover, then document. Identify which Microsoft Defender and Sentinel features support each step, including live response and investigation artifacts.

Treating advanced hunting queries as generic KQL and ignoring the schema differences between Defender XDR tables and Sentinel/Log Analytics tables.

Candidates practice KQL on one table set and then assume table names and fields are identical across portals, so they choose queries that would not run in the named environment.

What to do instead

Maintain a short reference of the key tables in each environment (device, email, identity, and alert tables in advanced hunting versus the equivalent Log Analytics tables) and practice writing the same hunt in both contexts.

Building a hunting hypothesis as a broad keyword search rather than a testable statement about attacker behavior mapped to a technique.

Candidates treat hunting as 'search logs for something bad', which produces noisy queries and cannot be evaluated against a described scenario.

What to do instead

Practice writing hunts in the form: hypothesis, technique, data source, query, expected benign explanation, and escalation criteria. Review a handful of common techniques and identify the telemetry each would leave behind.

Confusing custom detections with hunting queries, and assuming a saved hunting query automatically generates alerts or incidents.

Both are authored in KQL and stored in the same interface area, so candidates assume saving a query is equivalent to creating a detection.

What to do instead

Learn the distinct purpose and lifecycle of each: hunting queries are exploratory and analyst-driven, custom detections are scheduled and produce alerts. Practice converting a validated hunting query into a detection and note every setting that must change.

Exam requirements can change. Confirm current details with the exam provider.

SC-200 practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Manage a security operations environment

    A security operations team wants Microsoft Sentinel to automatically create an incident when a suspicious sign-in is detected. Which Sentinel component is responsible for generating incidents from alerts?

    1. Watchlists
    2. Workbooks
    3. Data connectors
    4. Analytics rules Correct answer.

    Explanation

    Analytics rules evaluate ingested data on a schedule or in near real time and produce alerts that are grouped into incidents. Workbooks only visualize data, watchlists supply reference data, and connectors bring data in.

  2. Question 2Manage a security operations environment

    Which role should be assigned to an analyst who must triage and investigate incidents in Microsoft Sentinel but should not be able to modify analytics rules?

    1. Microsoft Sentinel Contributor
    2. Owner
    3. Microsoft Sentinel Reader
    4. Microsoft Sentinel Responder Correct answer.

    Explanation

    The Microsoft Sentinel Responder role allows an analyst to view data and manage incidents, including assigning and closing them, without changing detection content. Contributor and Owner can modify rules, while Reader is view-only.

  3. Question 3Manage a security operations environment

    An organization needs Microsoft Defender XDR to correlate alerts across endpoints, email, identity, and cloud apps. Which configuration is required to enable this cross-domain correlation?

    1. Create a separate workspace for each Defender workload
    2. Disable built-in alert correlation in each product
    3. Enable the unified Microsoft Defender XDR portal and connect each workload Correct answer.
    4. Install the Log Analytics agent on all domain controllers

    Explanation

    Cross-domain incident correlation in Defender XDR occurs when the individual Defender workloads are onboarded and surfaced through the unified portal. Separate workspaces or disabling correlation would prevent unified incidents, and the Log Analytics agent is unrelated.

  4. Question 4Manage a security operations environment

    A SOC wants to reduce noise by suppressing a specific low-fidelity analytics rule during business hours only. What is the most appropriate built-in mechanism?

    1. Change the rule severity to Informational
    2. Add an automation rule with a time condition that closes matching incidents Correct answer.
    3. Delete the analytics rule each morning
    4. Disable the connector that supplies the data

    Explanation

    Automation rules can run conditionally, including time-based conditions, and can close or modify matching incidents without destroying detection content. Deleting rules or disabling connectors removes detection entirely, and lowering severity does not suppress the incidents.

  5. Question 5Manage a security operations environment

    Which Microsoft Sentinel feature lets analysts run a saved query on demand and optionally attach it to an incident for investigation?

    1. Data collection rules
    2. Playbooks
    3. Watchlists
    4. Hunting queries Correct answer.

    Explanation

    Hunting queries are saved log queries that analysts run proactively to look for threats and can be linked to incidents as part of investigation. Watchlists hold reference data, playbooks automate responses, and collection rules govern ingestion.

  6. Question 6Manage a security operations environment

    A SOC needs to automatically enrich new incidents with threat intelligence indicators before an analyst reviews them. Which Sentinel capability should be used?

    1. A workbook with a time chart
    2. A scheduled analytics rule
    3. A watchlist uploaded manually each week
    4. An automation rule that triggers a playbook Correct answer.

    Explanation

    Automation rules can trigger playbooks when incidents are created, and the playbook can query threat intelligence and write results back to the incident. Scheduled rules only detect, workbooks only display, and manual watchlists are not automated enrichment.

  7. Question 7Manage a security operations environment

    Which data connector type in Microsoft Sentinel uses the Azure Monitor Agent and data collection rules to ingest Windows security events from virtual machines?

    1. Microsoft 365 Defender connector
    2. Codeless connector via the data connector page
    3. Syslog via the Log Analytics agent
    4. Windows Security Events via AMA Correct answer.

    Explanation

    The Windows Security Events via AMA connector uses the Azure Monitor Agent and data collection rules to select which event sets to collect. The legacy Log Analytics agent connector is deprecated, and the other connectors target different sources.

  8. Question 8Manage a security operations environment

    An analyst wants to see which analytics rules are currently firing most often to prioritize tuning. Which Sentinel area provides rule-level health and incident counts?

    1. The Analytics blade with rule status and incident metrics Correct answer.
    2. The Logs blade query history
    3. The Repositories blade
    4. The Watchlist blade

    Explanation

    The Analytics blade lists rules with their status and links to the incidents they generate, which supports tuning decisions. Query history, watchlists, and repositories do not summarize rule firing frequency.

  9. Question 9Manage a security operations environment

    A SOC wants to ensure that only specific IP ranges can access the Microsoft Sentinel workspace while analysts work remotely. Which control should be applied?

    1. A watchlist of allowed IPs
    2. An analytics rule that flags foreign IPs
    3. Conditional Access with named locations Correct answer.
    4. A workbook showing sign-in locations

    Explanation

    Conditional Access policies with named locations enforce network-based access conditions at the identity layer. A watchlist or analytic rule only observes traffic after access, and a workbook only reports on it.

  10. Question 10Manage a security operations environment

    Which Microsoft Sentinel setting determines how long ingested data is retained in the workspace before being purged?

    1. The playbook trigger condition
    2. The data connector schedule
    3. The analytics rule frequency
    4. The workspace retention setting Correct answer.

    Explanation

    Workspace retention controls how long data remains queryable before deletion, and it can be configured per table. Rule frequency, connector schedules, and playbook triggers affect processing, not storage duration.

  11. Question 11Manage a security operations environment

    An analyst is investigating an incident and wants to view the full alert timeline and related entities such as accounts, hosts, and IP addresses. Which incident feature provides this?

    1. The data connector status page
    2. The watchlist editor
    3. The workbook gallery
    4. The incident investigation graph Correct answer.

    Explanation

    The investigation graph maps entities and their relationships around an incident so analysts can explore the attack path. Workbooks, connector pages, and watchlist editors do not provide entity relationship mapping.

  12. Question 12Manage a security operations environment

    A SOC needs to grant a managed identity permission to read incidents so a playbook can update them automatically. Which approach follows least privilege?

    1. Assign Owner at the subscription scope to the managed identity
    2. Assign the Microsoft Sentinel Responder role at the workspace scope Correct answer.
    3. Share an administrator account credential with the playbook
    4. Enable the global administrator role for the identity

    Explanation

    Granting the Sentinel Responder role scoped to the workspace gives the identity exactly the incident permissions needed. Subscription Owner and global administrator are far broader than required, and sharing credentials violates secure practice.

  13. Question 13Manage a security operations environment

    Which Microsoft Defender XDR feature allows a SOC to run a query across all connected workloads to hunt for threats?

    1. Advanced hunting Correct answer.
    2. Attack surface reduction rules
    3. Safe Links policies
    4. Device groups

    Explanation

    Advanced hunting uses Kusto Query Language to search across endpoint, email, identity, and cloud app data in Defender XDR. Attack surface reduction, Safe Links, and device groups are protection or management features, not cross-workload hunting.

  14. Question 14Manage a security operations environment

    An organization wants automated investigation and remediation to run when Defender XDR raises a high-severity incident. Which configuration enables this?

    1. Create a watchlist of high-severity alerts
    2. Disable the alert correlation engine
    3. Set the incident severity to Informational
    4. Enable automated investigation in the Defender XDR settings Correct answer.

    Explanation

    Automated investigation settings in Defender XDR control whether incidents trigger automated analysis and remediation actions. Severity changes, watchlists, and disabling correlation do not start automated investigations.

  15. Question 15Manage a security operations environment

    A SOC wants to onboard a new analyst quickly and ensure they can see incidents but not change workspace settings. Which built-in role best fits?

    1. Logic App Contributor
    2. Microsoft Sentinel Playbook Operator
    3. Microsoft Sentinel Contributor
    4. Microsoft Sentinel Reader Correct answer.

    Explanation

    Microsoft Sentinel Reader grants read access to incidents and data without configuration rights. Contributor can modify content, Playbook Operator runs playbooks, and Logic App Contributor manages automation resources.

  16. Question 16Manage a security operations environment

    An analyst needs to correlate sign-in events with a list of known bad IP addresses maintained by the threat intelligence team. Which Sentinel feature is designed for this correlation?

    1. A data collection rule
    2. A playbook trigger
    3. A workbook parameter
    4. A watchlist queried in an analytics rule Correct answer.

    Explanation

    Watchlists store reference lists such as known bad IPs and can be joined in analytics rule queries for correlation. Workbooks, collection rules, and playbook triggers do not provide reference list correlation.

  17. Question 17Manage a security operations environment

    Which Microsoft Sentinel content type packages analytics rules, playbooks, and workbooks for deployment across multiple workspaces?

    1. A data connector
    2. A watchlist
    3. A solution Correct answer.
    4. An incident task

    Explanation

    Solutions bundle related Sentinel content such as rules, playbooks, and workbooks for consistent deployment. Watchlists, connectors, and incident tasks are individual components rather than packaged content.

  18. Question 18Manage a security operations environment

    A SOC wants to automatically assign new incidents to the on-call analyst based on a rotating schedule stored in a watchlist. Which approach is most appropriate?

    1. Use an automation rule with a playbook that reads the watchlist and sets the owner Correct answer.
    2. Add the roster to an analytics rule query
    3. Manually reassign incidents each shift
    4. Create a workbook showing the on-call roster

    Explanation

    Automation rules can trigger a playbook that looks up the on-call entry in a watchlist and updates the incident owner. Manual reassignment is inefficient, and workbooks or rule queries cannot change incident ownership.

  19. Question 19Manage a security operations environment

    An analyst wants to test a new analytics rule without generating production incidents. Which approach is recommended?

    1. Disable all other rules while testing
    2. Set the rule severity to High and monitor closely
    3. Set the rule to run in a test workspace with sample data
    4. Run the rule query manually in Logs and review results Correct answer.

    Explanation

    Running the rule's query manually in Logs lets an analyst validate logic and results without creating incidents. Disabling other rules disrupts detection, and severity changes do not prevent incident creation.

  20. Question 20Manage a security operations environment

    Which setting in Microsoft Sentinel controls whether an incident is created when multiple alerts from the same rule fire within a short window?

    1. The workspace retention period
    2. The playbook run history
    3. Alert grouping settings in the analytics rule Correct answer.
    4. The data connector schedule

    Explanation

    Alert grouping settings determine how related alerts are combined into a single incident, reducing duplicate incidents. Retention, connector schedules, and playbook history do not affect incident grouping.

  21. Question 21Manage a security operations environment

    A SOC wants to review which automation playbooks failed during the last week. Where can this information be found?

    1. The data connector health page
    2. The watchlist audit log
    3. The automation run history in Microsoft Sentinel Correct answer.
    4. The incident investigation graph

    Explanation

    Automation run history shows playbook executions and their outcomes, allowing failed runs to be identified. Investigation graphs, connector health, and watchlist logs do not track playbook execution results.

  22. Question 22Manage a security operations environment

    An organization wants to ensure that Defender XDR incidents and Microsoft Sentinel incidents appear in a single view. Which configuration achieves this?

    1. Export incidents to a spreadsheet daily
    2. Create a separate workbook for each product
    3. Connect Microsoft Sentinel to the unified Defender portal Correct answer.
    4. Disable incident creation in Sentinel

    Explanation

    Onboarding Microsoft Sentinel to the unified Microsoft Defender portal surfaces both Sentinel and Defender incidents in one experience. Separate workbooks, disabling Sentinel incidents, and manual exports do not unify the views.

  23. Question 23Manage a security operations environment

    A SOC lead must design a process so that only approved analytics rule changes reach production. Which approach best supports this governance requirement?

    1. Allow all analysts to edit rules directly in production
    2. Disable audit logging to reduce noise
    3. Rely on workbook change history
    4. Use source control repositories with review and deployment pipelines Correct answer.

    Explanation

    Storing Sentinel content in repositories enables pull-request review and automated deployment, enforcing approval before production changes. Direct edits, workbook history, and disabling audit logs do not provide controlled change management.

  24. Question 24Manage a security operations environment

    Which Microsoft Sentinel table typically stores security events collected from Windows machines through the Azure Monitor Agent?

    1. SecurityEvent Correct answer.
    2. SigninLogs
    3. AuditLogs
    4. CommonSecurityLog

    Explanation

    The SecurityEvent table holds Windows security events collected via the Azure Monitor Agent. SigninLogs holds Entra ID sign-ins, AuditLogs holds directory audit records, and CommonSecurityLog holds CEF-formatted device logs.

  25. Question 25Manage a security operations environment

    A SOC wants to detect impossible travel sign-ins and automatically open an incident with the affected user as an entity. Which configuration is required in the analytics rule?

    1. Enable entity mapping for the account field Correct answer.
    2. Disable alert grouping
    3. Set the rule to run every 24 hours
    4. Add the user list to a workbook

    Explanation

    Entity mapping links fields in the query output to entity types such as Account so the incident shows the affected user. Rule frequency, workbooks, and alert grouping do not populate incident entities.

  26. Question 26Manage a security operations environment

    Which Microsoft Sentinel role allows a user to manage incidents and automation rules but does not allow changing workspace-level settings such as data retention?

    1. Microsoft Sentinel Reader
    2. Microsoft Sentinel Responder Correct answer.
    3. Microsoft Sentinel Contributor
    4. Microsoft Sentinel Playbook Operator

    Explanation

    The Microsoft Sentinel Responder role is scoped to triaging and acting on incidents, including assigning, closing, and running automation on them, but it deliberately excludes workspace configuration. Contributor adds the ability to create and edit content such as analytics rules and workbooks. Only Owner-level or specific administrative roles control workspace settings like retention.

  27. Question 27Manage a security operations environment

    A SOC wants a single identity to authenticate playbooks that read and update Microsoft Sentinel incidents without storing a client secret. Which Azure AD construct should be used?

    1. A managed identity assigned to the logic app Correct answer.
    2. A service principal with a client secret stored in the playbook
    3. A shared mailbox account with delegated permissions
    4. A user account with multi-factor authentication disabled

    Explanation

    A managed identity gives an Azure resource, such as a Logic App, an automatically managed credential in Azure AD, so no secret is stored or rotated by the SOC. The identity is then granted a Sentinel role on the workspace, such as Responder. This removes the credential-management risk that secrets and password-based accounts introduce.

  28. Question 28Manage a security operations environment

    An analyst needs to review the complete alert history, entities, and investigation graph for a single security incident in Microsoft Sentinel. Which feature provides this consolidated view?

    1. The incident details page Correct answer.
    2. The workbooks gallery
    3. The data connectors page
    4. The Logs blade

    Explanation

    The incident details page consolidates the alerts that make up an incident, the mapped entities such as accounts and hosts, and the investigation experience. Analysts use it as the starting point for triage and evidence gathering. The other areas serve querying, reporting, and ingestion configuration rather than incident-centric review.

  29. Question 29Manage a security operations environment

    Which Microsoft Sentinel table stores Windows security events forwarded from machines using the Azure Monitor Agent and a data collection rule?

    1. SecurityEvent Correct answer.
    2. CommonSecurityLog
    3. SigninLogs
    4. AuditLogs

    Explanation

    The SecurityEvent table is the standard destination for Windows Security event log data collected through the Azure Monitor Agent and an associated data collection rule. SigninLogs holds Azure AD sign-in records, CommonSecurityLog holds CEF-formatted device logs, and AuditLogs holds Azure AD audit activity. Analysts query SecurityEvent when investigating Windows authentication and privilege events.

  30. Question 30Manage a security operations environment

    Which Microsoft Sentinel setting controls how long ingested data remains queryable in the workspace before it is removed?

    1. The analytics rule lookback window
    2. The data collection rule stream declaration
    3. The incident grouping setting
    4. The workspace retention setting Correct answer.

    Explanation

    Workspace retention defines how long data stays available in the workspace, and it can be configured per table. After the retention period elapses, data is purged unless archived or exported. Lookback windows and grouping settings affect detection behavior, not storage lifetime.

  31. Question 31Manage a security operations environment

    A SOC wants to run a single hunting query across Microsoft Defender XDR workloads such as endpoints, email, and identities. Which capability should the analyst use?

    1. Sentinel workbooks
    2. Attack surface reduction rules
    3. Advanced hunting with KQL Correct answer.
    4. Defender for Cloud regulatory compliance

    Explanation

    Advanced hunting in Microsoft Defender XDR uses KQL to query a unified schema spanning endpoints, email, identities, and cloud apps. This lets analysts correlate signals across workloads in one query rather than switching portals. Workbooks, compliance dashboards, and ASR rules do not provide cross-workload query access.

  32. Question 32Manage a security operations environment

    Which Microsoft Sentinel content type bundles analytics rules, playbooks, workbooks, and parsers so they can be deployed consistently across many workspaces?

    1. A hunting query
    2. A watchlist
    3. A saved search
    4. A solution Correct answer.

    Explanation

    Solutions package related Sentinel content, including analytics rules, automation playbooks, workbooks, and parsers, so they can be installed and versioned across workspaces. Saved searches, watchlists, and hunting queries are individual artifacts rather than deployment packages. Using solutions keeps multi-workspace deployments consistent.

  33. Question 33Manage a security operations environment

    A SOC lead wants to confirm which automation playbooks failed during the past week. Where should the lead look?

    1. The workspace usage and cost report
    2. The Logic Apps run history for the playbooks Correct answer.
    3. The Sentinel automation rule run history
    4. The analytics rule health page

    Explanation

    Playbooks are Logic Apps, so each execution and its failure details appear in the Logic App run history, where failed actions and error messages can be inspected. Automation rule history shows whether the rule triggered and which playbook it invoked, but the detailed failure diagnostics live in the Logic App. Reviewing run history is the standard way to troubleshoot playbook failures.

  34. Question 34Manage a security operations environment

    An analyst wants to correlate sign-in events with a list of known malicious IP addresses maintained outside Sentinel. Which approach is most appropriate?

    1. Export SigninLogs to a spreadsheet and compare manually
    2. Create a watchlist and join it to the SigninLogs table in a KQL query Correct answer.
    3. Add the IPs as entity mappings in an analytics rule
    4. Create an automation rule that emails the IP list daily

    Explanation

    Watchlists store reference data, such as threat indicators, that can be joined to log tables in KQL queries and referenced by analytics rules. Uploading the IP list to a watchlist makes the comparison repeatable and automatable. Manual comparison, emailing the list, and entity mappings do not provide a queryable data set for correlation.

  35. Question 35Manage a security operations environment

    A SOC wants new incidents automatically assigned to the on-call analyst whose name rotates weekly in a SharePoint list. Which Sentinel capability should be used?

    1. A data collection rule transform
    2. A workbook with a parameter for the analyst name
    3. An automation rule that reads a watchlist and assigns the owner Correct answer.
    4. An analytics rule with entity mapping

    Explanation

    Automation rules can trigger on incident creation and invoke a playbook that reads the current on-call entry from a watchlist, then assigns the incident owner. Keeping the rotation in a watchlist lets the schedule be updated without editing the rule. Analytics rules detect events, workbooks display data, and collection rules transform ingestion, so none of them assign ownership.

  36. Question 36Manage a security operations environment

    An analyst wants to validate a new analytics rule against historical data without creating production incidents. Which approach is recommended?

    1. Disable all other analytics rules while testing
    2. Ask another team to test the rule in their workspace
    3. Run the rule in a production workspace and delete any incidents it creates
    4. Enable the rule with incident creation turned off and review its results Correct answer.

    Explanation

    Sentinel lets a rule run while incident creation is disabled, so the analyst can see whether and how often it would fire without polluting the incident queue. After validating the results and tuning thresholds, incident creation can be enabled. Disabling other rules, deleting incidents, or testing in another team's workspace introduces avoidable risk or disruption.

  37. Question 37Manage a security operations environment

    A SOC wants multiple alerts from the same analytics rule to be combined into one incident while the incident is open. Which Sentinel setting controls this behavior?

    1. The rule's severity level
    2. The workspace retention period
    3. The incident grouping setting on the analytics rule Correct answer.
    4. The entity mapping configuration

    Explanation

    Incident grouping determines whether alerts are grouped into a single incident, for example by combining all alerts from one rule into one incident while it remains open. Severity affects prioritization, retention affects storage, and entity mapping affects which entities are attached. Grouping is the setting that governs alert-to-incident consolidation.

  38. Question 38Manage a security operations environment

    An organization wants Defender XDR incidents and Microsoft Sentinel incidents to appear in a unified incident queue. What must be configured?

    1. Export Defender incidents to a watchlist on a schedule
    2. Enable auditing on the Sentinel workspace
    3. Connect Microsoft Defender XDR to Microsoft Sentinel in the workspace data connectors Correct answer.
    4. Create a duplicate analytics rule for each Defender detection

    Explanation

    Connecting Microsoft Defender XDR to Microsoft Sentinel streams Defender incidents and alerts into the workspace, so analysts can triage them alongside native Sentinel incidents. This integration also supports advanced hunting data and incident updates flowing between the products. Exporting, auditing, or duplicating rules does not produce a unified queue.

  39. Question 39Manage a security operations environment

    A SOC wants automated investigation and remediation to start when Defender XDR raises a high-severity incident. Which configuration is required?

    1. Set the incident severity threshold in the automated investigation settings Correct answer.
    2. Enable audit logging on the Defender portal
    3. Create a Sentinel watchlist of high-severity alerts
    4. Assign the Security Reader role to the automation account

    Explanation

    Defender XDR automated investigation and response settings let administrators define the severity threshold and whether remediation actions run automatically or require approval. Once configured, qualifying incidents trigger investigations without analyst initiation. Watchlists, audit logging, and read-only roles do not start automated investigations.

  40. Question 40Manage a security operations environment

    A SOC must ensure that only approved analytics rule changes reach production. Which approach best supports this requirement?

    1. Deploy rules from a source-controlled repository using an infrastructure-as-code pipeline with approvals Correct answer.
    2. Allow analysts to edit rules directly in the portal
    3. Restrict all rule creation to a single administrator
    4. Rely on weekly manual reviews of the analytics page

    Explanation

    Managing analytics rules as code in a repository, with a deployment pipeline that enforces review and approval, provides traceability and prevents unreviewed changes from reaching production. Direct portal edits, manual reviews, and single-administrator restrictions lack enforced gates and version history. This approach also supports rollback and consistent multi-workspace deployment.

  41. Question 41Manage a security operations environment

    An analyst needs to see which analytics rules are firing most frequently to prioritize tuning. Which Sentinel area should the analyst use?

    1. The analytics rule health and insights view Correct answer.
    2. The workspace settings blade
    3. The data connectors page
    4. The entity behavior analytics page

    Explanation

    The analytics rule insights and health view summarizes rule execution, alert volume, and firing frequency so analysts can spot noisy rules. This information supports tuning thresholds and reducing alert fatigue. Connector pages, workspace settings, and entity behavior pages do not report per-rule firing frequency.

  42. Question 42Manage a security operations environment

    A SOC wants to detect impossible travel sign-ins and open an incident that includes the affected user as an entity. Which configuration is needed?

    1. A data collection rule with a transform
    2. An analytics rule with scheduled frequency and user entity mapping Correct answer.
    3. A watchlist containing all user accounts
    4. A workbook with a user parameter

    Explanation

    A scheduled analytics rule evaluates sign-in data at a defined frequency, and entity mapping identifies the user field so the incident includes the account entity. Including the entity enables investigation and response actions against the user. Collection rules, workbooks, and watchlists do not create incidents with mapped entities.

  43. Question 43Manage a security operations environment

    A SOC wants to restrict access to the Microsoft Sentinel workspace so only specific IP ranges can reach it while analysts work remotely. Which control should be applied?

    1. Data collection rule filters
    2. Workspace retention settings
    3. Incident grouping rules
    4. Conditional Access with named locations Correct answer.

    Explanation

    Conditional Access policies with named locations can allow or block access based on the source network, and they apply across the Microsoft security portal and related services. Retention, collection filters, and grouping rules affect data handling rather than access control. Combining named locations with other conditions tightens remote access.

  44. Question 44Manage a security operations environment

    A SOC ingests third-party firewall logs in CEF format through a log forwarder. Which Sentinel table receives this data by default?

    1. SecurityEvent
    2. Heartbeat
    3. Syslog
    4. CommonSecurityLog Correct answer.

    Explanation

    CEF-formatted logs sent through the Log Analytics agent or AMA-based forwarder land in the CommonSecurityLog table, where they can be parsed and correlated. SecurityEvent holds Windows events, Syslog holds raw Linux-style messages, and Heartbeat tracks agent health. Knowing the destination table is essential for writing detection queries.

  45. Question 45Manage a security operations environment

    An analyst wants to enrich incidents with threat intelligence indicators from Microsoft Defender Threat Intelligence inside Microsoft Sentinel. Which approach provides this enrichment?

    1. Create a workbook that lists indicators
    2. Enable auditing on the workspace
    3. Use the threat intelligence data connector and matching analytics rules Correct answer.
    4. Add indicators to an incident comment manually

    Explanation

    The threat intelligence connector imports indicators into Sentinel, and analytics rules that use the built-in matching templates generate alerts when logs match those indicators. This automates enrichment and detection rather than relying on manual review. Workbooks, manual comments, and auditing do not provide indicator matching.

  46. Question 46Manage a security operations environment

    A SOC wants an incident to be created only when a scheduled analytics rule produces more results than a defined baseline in a single run. Which rule configuration supports this?

    1. Change the rule severity to High
    2. Set the rule's alert threshold to trigger on the number of results Correct answer.
    3. Increase the rule's query lookback period
    4. Add more entity mappings to the rule

    Explanation

    Scheduled analytics rules can be configured so an alert fires only when the number of query results exceeds a threshold, which helps suppress low-volume noise. Lookback changes the query window, severity affects prioritization, and entity mappings affect incident content. Only the threshold setting gates alert creation on result count.

  47. Question 47Manage a security operations environment

    A SOC needs to grant a playbook permission to read incidents in a specific workspace only, following least privilege. Which assignment is most appropriate?

    1. Assign the managed identity the Global Administrator directory role
    2. Assign the managed identity the Owner role at the subscription scope
    3. Assign the managed identity the Security Reader role at the tenant root scope
    4. Assign the managed identity the Microsoft Sentinel Responder role on the workspace resource Correct answer.

    Explanation

    Granting the playbook's managed identity the Responder role scoped to the specific workspace gives it the incident read and update permissions it needs without broader access. Subscription-level Owner and tenant-wide directory roles vastly exceed the requirement. Least privilege limits the blast radius if the identity is misused.

  48. Question 48Manage a security operations environment

    A SOC observes that an automation rule fires but the playbook never runs. Which cause should be investigated first?

    1. The playbook's connection or managed identity lacks the required permissions Correct answer.
    2. The workspace retention period is too short
    3. The analytics rule severity is set to Low
    4. The incident grouping setting is disabled

    Explanation

    When an automation rule triggers but the playbook does not execute, the most common cause is an authorization failure in the playbook's connections or managed identity. Checking the Logic App run history and the identity's role assignments confirms whether permission is the blocker. Retention, severity, and grouping affect data lifetime or incident formation, not playbook authorization.

  49. Question 49Manage a security operations environment

    An analyst must determine whether a spike in incidents is caused by a single noisy analytics rule or by a genuine increase in malicious activity. Which analysis approach is most reliable?

    1. Compare per-rule alert volume against historical baselines and inspect a sample of matched events Correct answer.
    2. Assign all new incidents to a single analyst for review
    3. Increase retention to ninety days and wait for the next spike
    4. Disable the noisiest rule and observe whether the incident count drops

    Explanation

    Comparing per-rule volume with historical baselines, then sampling matched events, distinguishes a tuning problem from real adversary activity. Disabling a rule merely hides the signal, longer retention does not explain the spike, and assigning incidents does not analyze the cause. Evidence-based triage avoids both false alarms and missed threats.

  50. Question 50Manage a security operations environment

    A SOC wants to reduce ingestion cost without losing the ability to detect high-value events. Which strategy best balances cost and detection coverage?

    1. Send all logs to a basic logs table and query them only during incidents
    2. Disable all data connectors and rely on manual log review
    3. Reduce the number of analytics rules to lower ingestion volume
    4. Apply ingestion-time filtering and table-level retention plans to keep only security-relevant events Correct answer.

    Explanation

    Filtering at ingestion with data collection rule transforms and choosing appropriate table plans or retention tiers removes low-value data while preserving events that detections depend on. Disabling connectors, indiscriminately using basic logs, or cutting analytics rules degrades detection coverage rather than optimizing cost. The goal is to retain high-value telemetry at the right tier.

  51. Question 51Manage a security operations environment

    Which Microsoft Sentinel role allows a user to create and edit analytics rules, playbooks, and workbooks but not to manage workspace-level settings or user assignments?

    1. Microsoft Sentinel Contributor Correct answer.
    2. Microsoft Sentinel Reader
    3. Microsoft Sentinel Playbook Operator
    4. Microsoft Sentinel Responder

    Explanation

    The Microsoft Sentinel Contributor role grants full management of Sentinel content such as analytics rules, automation, and workbooks, but it does not include the rights to change workspace settings or assign roles. Those higher privileges are reserved for the Owner role at the resource scope.

  52. Question 52Manage a security operations environment

    An analyst wants to connect Microsoft Defender for Cloud alerts into Microsoft Sentinel so they appear alongside other detections. Which configuration object performs this integration?

    1. A workbook
    2. A watchlist
    3. A data connector Correct answer.
    4. An automation rule

    Explanation

    Data connectors are the mechanism that ingests data and alerts from external sources such as Microsoft Defender for Cloud into a Sentinel workspace. Once connected, the alerts flow into the incidents and alerts tables for correlation and analysis.

  53. Question 53Manage a security operations environment

    A SOC manager wants to review which users hold elevated permissions on the Sentinel workspace and when those assignments were last changed. Which capability provides this audit trail?

    1. Azure Activity log Correct answer.
    2. Watchlist management
    3. Sentinel hunting queries
    4. Workbook dashboards

    Explanation

    Role assignments and workspace configuration changes are Azure resource operations, so they are recorded in the Azure Activity log rather than in the Sentinel data tables. Auditors can query that log to see who changed access and when.

  54. Question 54Manage a security operations environment

    A team wants to grant a security analyst access to incidents in one Sentinel workspace without giving the same access to other workspaces in the subscription. Which approach satisfies this?

    1. Assign the Sentinel Responder role at the resource group scope Correct answer.
    2. Assign the Reader role at the tenant root scope
    3. Assign the Global Administrator directory role to the analyst
    4. Assign the Sentinel Responder role at the subscription scope

    Explanation

    Azure RBAC is inherited downward, so assigning a role at a narrower scope such as the resource group limits its effect to resources within that scope. Assigning at the subscription or tenant level would grant access to every workspace beneath it.

  55. Question 55Manage a security operations environment

    A SOC wants analysts to see the MITRE ATT&CK tactics and techniques that each detection covers so they can spot coverage gaps. Where is this mapping configured and reviewed?

    1. In the playbook trigger conditions
    2. In the analytics rule definition and the MITRE ATT&CK blade Correct answer.
    3. In the workspace retention settings
    4. In the data collection rule transformations

    Explanation

    Analytics rules include an optional tactics and techniques mapping, and the MITRE ATT&CK coverage blade aggregates those mappings into a coverage matrix. This lets the team identify which tactics lack detections.

  56. Question 56Manage a security operations environment

    An organization needs to ensure that Sentinel data for a workspace is stored in a specific geographic region for regulatory reasons. Which setting determines this?

    1. The region chosen when the workspace was created Correct answer.
    2. The data connector configuration
    3. The log analytics pricing tier
    4. The retention tier selected for each table

    Explanation

    The geographic location of the Log Analytics workspace, chosen at creation, determines where the ingested data is stored. This location cannot be changed after creation without recreating or migrating the workspace.

  57. Question 57Manage a security operations environment

    A SOC wants to keep certain sensitive incident fields from being visible to a group of junior analysts while letting them triage other incidents. Which Sentinel capability supports field-level restriction?

    1. Apply a watchlist filter to the incident queue
    2. Configure table-level retention policies
    3. Enable the entity behavior analytics toggle
    4. No built-in field-level masking exists; separate workspaces or role scoping is required Correct answer.

    Explanation

    Sentinel does not provide per-field masking within incidents; access control is applied at the workspace and resource scope. To restrict visibility of sensitive data, organizations typically isolate that data in a separate workspace with its own role assignments.

  58. Question 58Manage a security operations environment

    A SOC wants to receive an email notification whenever a new high-severity incident is created in Sentinel. Which configuration should the analyst use?

    1. A workbook with a severity filter
    2. An automation rule with a notification action Correct answer.
    3. A scheduled analytics rule with entity mapping
    4. A hunting query saved as a bookmark

    Explanation

    Automation rules run when incidents are created or updated and can trigger notification actions such as sending email or calling a playbook. They are the standard mechanism for incident-time alerting to staff.

  59. Question 59Manage a security operations environment

    A SOC wants to prevent a noisy analytics rule from generating more than a set number of incidents per hour during a known attack campaign. Which setting on the analytics rule should be adjusted?

    1. The entity mapping configuration
    2. The playbook run order
    3. Incident settings that control grouping and suppression Correct answer.
    4. The rule query frequency only

    Explanation

    Analytics rules include incident settings that control how alerts are grouped into incidents and whether suppression stops new incidents for a period after one is created. Tuning these settings limits incident volume without disabling detection.

  60. Question 60Manage a security operations environment

    A SOC wants to define a reusable list of privileged service accounts that analysts can reference in hunting queries without retyping them. Which Sentinel feature is designed for this?

    1. A watchlist Correct answer.
    2. A data collection rule
    3. A bookmark
    4. A saved search

    Explanation

    Watchlists store reference data such as account inventories that can be joined to log queries for enrichment and filtering. They centralize maintenance of lists that many queries share.

  61. Question 61Manage a security operations environment

    A SOC wants to ensure that all new analytics rules created by analysts are reviewed by a senior engineer before they can generate incidents. Which practice best achieves this?

    1. Enable rule scheduling at a five-minute frequency
    2. Assign the Reader role to all analysts
    3. Turn on entity behavior analytics for the workspace
    4. Deploy rules through a repository-based pipeline with approval gates Correct answer.

    Explanation

    Managing Sentinel content as code in a source repository with a deployment pipeline lets reviewers approve changes before they reach the production workspace. This enforces a review gate that cannot be bypassed by direct portal edits if permissions are restricted.

  62. Question 62Manage a security operations environment

    An analyst wants to understand why a particular incident was created, including which analytics rule fired and what query produced the alert. Which action provides this detail?

    1. Check the workspace pricing tier
    2. Review the data connector status page
    3. Inspect the playbook run history
    4. Open the incident and review its linked alerts and associated query Correct answer.

    Explanation

    Each incident links to the alerts that created it, and each alert records the analytics rule and query that generated it. Opening the incident and drilling into the alert gives the full detection context.

  63. Question 63Manage a security operations environment

    A SOC wants to limit which users can manually run a specific response playbook from the incident page. Which control should be applied?

    1. Assign the Microsoft Sentinel Playbook Operator role only to approved users Correct answer.
    2. Add the playbook to a watchlist
    3. Grant Contributor on the logic app to all analysts
    4. Enable managed identity on the logic app

    Explanation

    The Playbook Operator role grants the specific right to run playbooks manually without granting broader authoring or workspace permissions. Scoping this role to approved responders enforces least privilege for manual execution.

  64. Question 64Manage a security operations environment

    A SOC wants to reduce the volume of low-value informational alerts reaching the incident queue while keeping the raw events available for hunting. Which approach best balances this?

    1. Disable all analytics rules and rely on manual hunting
    2. Increase the workspace retention period to one year
    3. Route all events to a second workspace without rules
    4. Filter or transform data at ingestion and tune rules to create incidents only for high-value events Correct answer.

    Explanation

    Ingestion-time filtering and transformation reduces stored noise, while tuned analytics rules ensure incidents reflect meaningful detections. Raw high-value events remain queryable for hunting without flooding the queue.

  65. Question 65Manage a security operations environment

    A SOC needs to confirm that a newly connected data source is actually delivering events before enabling dependent analytics rules. Which check should the analyst perform first?

    1. Open the MITRE ATT&CK coverage blade
    2. Export the incident list to a spreadsheet
    3. Review the automation rule run history
    4. Query the target table for recent records using a time range filter Correct answer.

    Explanation

    Verifying recent records in the destination table confirms that the connector is delivering data and that parsing works as expected. Only after this validation should dependent analytics rules be enabled.

  66. Question 66Manage a security operations environment

    A SOC wants to give a partner organization read-only visibility into incidents in a specific Sentinel workspace without granting access to the rest of the subscription. Which combination is most appropriate?

    1. Share workspace keys with the partner for direct query access
    2. Assign the Security Admin role at the tenant level to the partner
    3. Assign the Sentinel Reader role at the workspace or resource group scope to the partner account Correct answer.
    4. Assign the Owner role at the subscription scope to the partner account

    Explanation

    The Sentinel Reader role provides read-only access to incidents and data, and assigning it at the workspace or resource group scope limits exposure to that boundary. This meets the partner's need without granting broader administrative rights.

  67. Question 67Manage a security operations environment

    A SOC wants to know whether analysts are consistently closing incidents with proper classification so they can report on true positive rates. Which Sentinel area should they use?

    1. The data connector health page
    2. The incident queue filtered by classification and the workbook reporting on incidents Correct answer.
    3. The hunting query gallery
    4. The watchlist management page

    Explanation

    Incident classification fields capture whether an incident was a true or false positive, and workbooks can aggregate these values for reporting. Reviewing the queue with classification filters reveals analyst consistency.

  68. Question 68Respond to security incidents

    An analyst wants Microsoft Defender XDR to automatically investigate and remediate alerts without manual approval. Which setting should be enabled?

    1. Advanced hunting
    2. Threat analytics
    3. Attack surface reduction rules
    4. Automated investigation and response Correct answer.

    Explanation

    Automated investigation and response (AIR) lets Defender XDR triage alerts, build investigation graphs, and apply remediation actions automatically or with approval depending on configuration. Advanced hunting and threat analytics are read/analysis features and do not remediate. ASR rules block behaviors at the endpoint but are not the orchestration engine for incident response.

  69. Question 69Respond to security incidents

    A security team needs every high-severity incident in Microsoft Defender XDR to be triaged by a human before any remediation runs. Which configuration achieves this?

    1. Disable all alert policies in Microsoft Sentinel
    2. Set automated investigation to run but require approval for remediation actions Correct answer.
    3. Turn off the Microsoft Defender for Endpoint real-time protection
    4. Lower the incident severity threshold to informational

    Explanation

    Defender XDR allows investigations to run automatically while remediation actions are placed in a pending-approval queue, preserving human oversight. Disabling alert policies or real-time protection removes detection rather than adding approval. Severity thresholds affect which alerts become incidents, not whether remediation requires approval.

  70. Question 70Respond to security incidents

    An analyst is reviewing an incident in the Microsoft Defender portal and wants to see which alerts, entities, and evidence are grouped together. Which incident component provides this?

    1. The secure score trend
    2. The device timeline only
    3. The incident graph and evidence tab Correct answer.
    4. The threat analytics report

    Explanation

    The incident graph and evidence tab visualize related alerts, impacted entities, and supporting evidence so analysts understand scope before acting. Secure score measures posture, not incident composition. A device timeline shows local events but not cross-workload correlation.

  71. Question 71Respond to security incidents

    During triage, an analyst confirms a malicious file was executed on a device. Which Defender XDR action immediately stops the running process and quarantines the file?

    1. Initiate automated investigation
    2. Restrict app execution
    3. Live response collect
    4. Stop and quarantine file Correct answer.

    Explanation

    The 'stop and quarantine file' action terminates the running process and quarantines the file on the device. Live response collect gathers forensic artifacts without stopping execution. Restrict app execution limits future execution but does not terminate the current process.

  72. Question 72Respond to security incidents

    An analyst wants to isolate a compromised device from the network while still allowing the analyst to connect via Live Response. Which action should be used?

    1. Selective isolation Correct answer.
    2. Full isolation
    3. Run antivirus scan
    4. Restrict app execution

    Explanation

    Selective isolation blocks most network traffic but preserves the Defender Live Response connection so analysts can continue investigating. Full isolation blocks all traffic including Live Response. Restrict app execution and antivirus scans do not isolate the device from the network.

  73. Question 73Respond to security incidents

    A security operations team wants a playbook to run automatically whenever a specific incident is created in Microsoft Sentinel. Which component triggers the playbook?

    1. A scheduled analytics rule
    2. An automation rule with a run playbook action Correct answer.
    3. A data connector
    4. A workbook with a parameter

    Explanation

    Automation rules in Microsoft Sentinel evaluate incident conditions and can invoke a playbook when the rule matches. Scheduled analytics rules generate alerts and incidents but do not directly launch playbooks. Workbooks are visualization tools and connectors ingest data.

  74. Question 74Respond to security incidents

    An analyst needs to automatically assign incidents from a Sentinel analytics rule to the on-call owner and add a tag. Which Sentinel feature should be configured?

    1. Automation rule Correct answer.
    2. Watchlist
    3. Analytics rule threshold
    4. Hunting query

    Explanation

    Automation rules can change owner, severity, status, and tags on incidents that meet conditions, providing consistent triage. Analytics rule thresholds affect alert generation, not assignment. Watchlists and hunting queries supply data or search capability but do not modify incident ownership.

  75. Question 75Respond to security incidents

    A playbook in Microsoft Sentinel must be invoked by an automation rule. Which resource must the playbook be based on to support this?

    1. A PowerShell runbook in Azure Automation
    2. Azure Logic Apps with the Microsoft Sentinel trigger Correct answer.
    3. An Azure Function with an HTTP trigger
    4. A Microsoft Teams webhook

    Explanation

    Sentinel playbooks are built on Azure Logic Apps and use the Microsoft Sentinel incident trigger so automation rules can invoke them. Azure Functions, Automation runbooks, and Teams webhooks can be called from Logic Apps but are not the playbook resource type itself.

  76. Question 76Respond to security incidents

    An analyst wants to run a KQL query during incident investigation in Microsoft Sentinel to find related sign-in events. Which feature provides an ad hoc query interface scoped to the investigation?

    1. Data collection rules
    2. Workbooks
    3. Metrics
    4. Logs with a custom time range Correct answer.

    Explanation

    The Logs experience lets analysts run ad hoc KQL against Log Analytics tables, and adjusting the time range scopes results to the incident window. Workbooks are static visualizations, Metrics is not a Sentinel query tool, and data collection rules govern ingestion rather than querying.

  77. Question 77Respond to security incidents

    An analyst needs to correlate a suspicious IP address across sign-in logs, device events, and email events in Microsoft Defender XDR. Which capability provides a unified query across these workloads?

    1. Secure score
    2. Device timeline
    3. Advanced hunting with the unified schema Correct answer.
    4. Attack surface reduction report

    Explanation

    Advanced hunting in Defender XDR queries a unified schema spanning identities, endpoints, email, and cloud apps, enabling cross-workload correlation. Device timeline is endpoint-scoped, secure score is a posture metric, and ASR reports summarize rule activity only.

  78. Question 78Respond to security incidents

    A suspicious email was delivered to several mailboxes. Which Defender for Office 365 action removes the message from all affected mailboxes after delivery?

    1. Soft delete
    2. Quarantine release
    3. Hard delete Correct answer.
    4. Move to junk

    Explanation

    Hard delete removes the delivered message from affected mailboxes, which is the appropriate remediation for confirmed malicious mail. Soft delete moves messages to the Deleted Items folder where users can recover them. Move to junk and quarantine release do not remove the message from mailboxes.

  79. Question 79Respond to security incidents

    An analyst is investigating a phishing incident in Defender XDR and wants to see which users clicked the malicious link. Which data source in the incident provides this?

    1. Email events and URL click data Correct answer.
    2. Registry key events
    3. Firewall logs
    4. Device process events

    Explanation

    Email events combined with URL click telemetry show delivery, click, and post-click activity for phishing campaigns. Device process and registry events relate to endpoint execution, and firewall logs show network connections rather than link clicks.

  80. Question 80Respond to security incidents

    A compromised user account is confirmed. Which action should an analyst take first to contain the identity threat?

    1. Remove the user from all groups permanently
    2. Disable conditional access for the tenant
    3. Delete the user's mailbox
    4. Revoke the user's refresh tokens and reset the password Correct answer.

    Explanation

    Revoking refresh tokens invalidates existing sessions and combined with a password reset stops the attacker from continuing to use stolen credentials. Deleting the mailbox destroys evidence and is not a containment step. Disabling conditional access weakens controls, and permanent group removal is not the immediate containment action.

  81. Question 81Respond to security incidents

    An analyst wants to mark a compromised user as risky and force a secure password change at next sign-in. Which Microsoft Entra ID Protection action supports this?

    1. Disable user
    2. Dismiss user risk
    3. Confirm user compromised Correct answer.
    4. Reset password

    Explanation

    Confirming the user as compromised in Entra ID Protection sets the risk state to high and, with a risk policy, forces a secure password reset. Dismissing risk clears the detection, reset password alone does not mark risk, and disabling the account is a separate containment action.

  82. Question 82Respond to security incidents

    A security analyst is building a Live Response session to collect forensic artifacts from a device. Which capability must be enabled on the device?

    1. Network protection
    2. Live response Correct answer.
    3. Tamper protection
    4. Cloud-delivered protection

    Explanation

    Live Response must be enabled in the Defender for Endpoint settings for the device to accept remote commands and collect artifacts. Tamper protection, cloud-delivered protection, and network protection are defense features, not the remote shell capability.

  83. Question 83Respond to security incidents

    During a Live Response session, an analyst wants to retrieve a suspicious executable from a device for offline analysis. Which command should be used?

    1. connections
    2. getfile Correct answer.
    3. processes
    4. putfile

    Explanation

    The getfile command downloads a file from the device to the analyst for analysis. Putfile uploads a file to the device. Processes and connections list running processes and network connections respectively.

  84. Question 84Respond to security incidents

    An analyst needs to determine whether a malicious process spawned child processes on a device after an alert. Which hunting table should be queried?

    1. DeviceProcessEvents Correct answer.
    2. DeviceNetworkEvents
    3. DeviceRegistryEvents
    4. DeviceFileEvents

    Explanation

    DeviceProcessEvents records process creation, command lines, and parent-child relationships, which is exactly what is needed to trace spawned processes. Network, file, and registry tables capture other telemetry types and cannot show process lineage.

  85. Question 85Respond to security incidents

    An analyst wants to identify all devices that communicated with a known malicious IP in the last seven days. Which approach is most appropriate in Defender XDR advanced hunting?

    1. Query DeviceNetworkEvents filtered by the remote IP and time range Correct answer.
    2. Query the secure score recommendations
    3. Query DeviceProcessEvents for the IP string
    4. Query DeviceRegistryEvents for the IP

    Explanation

    DeviceNetworkEvents contains remote IP and connection data, so filtering on the malicious address and a seven-day window returns affected devices. Process and registry tables do not store remote IP connections, and secure score is a posture report.

  86. Question 86Respond to security incidents

    A Sentinel incident is a duplicate of an existing investigation. Which action should an analyst take to consolidate tracking?

    1. Close the incident as benign
    2. Change the incident severity to informational
    3. Delete the analytics rule
    4. Merge the incident into the primary incident Correct answer.

    Explanation

    Merging links related incidents so alerts and evidence are tracked under one primary incident, avoiding duplicated effort. Closing as benign discards valid data, deleting the rule removes detection, and changing severity does not consolidate records.

  87. Question 87Respond to security incidents

    An analyst wants to add a comment and attach a custom tag to a Sentinel incident for team tracking. Which incident property supports this without altering detection logic?

    1. Analytics rule query
    2. Watchlist entity mapping
    3. Incident tags and comments Correct answer.
    4. Data collection rule

    Explanation

    Tags and comments are incident metadata used for tracking and collaboration and do not change detection logic. Analytics queries, collection rules, and watchlist mappings affect detection or ingestion behavior.

  88. Question 88Respond to security incidents

    A Defender XDR incident shows an alert for a suspicious sign-in and a related alert for anomalous mailbox rules. Which concept explains why these alerts appear in one incident?

    1. Each alert is a separate incident by default
    2. Alerts are grouped only by detection source
    3. Incident correlation groups related alerts by entities and timing Correct answer.
    4. Alerts are grouped only by severity

    Explanation

    Defender XDR correlates alerts that share entities, time proximity, and attack story into a single incident. Alerts are not automatically separate incidents, and grouping is not based solely on severity or detection source.

  89. Question 89Respond to security incidents

    An analyst needs to revert a remediation action that quarantined a file on a device after confirming it was a false positive. Which Defender XDR capability supports this?

    1. Action center history with undo Correct answer.
    2. Threat analytics report
    3. Attack surface reduction audit
    4. Secure score improvement action

    Explanation

    The Action center records remediation history and allows undo of actions such as file quarantine when a false positive is confirmed. Threat analytics, secure score, and ASR audit reports do not provide action reversal.

  90. Question 90Respond to security incidents

    A security team wants to automatically block a known malicious hash across all onboarded devices. Which Defender for Endpoint indicator type should be created?

    1. IP address indicator with audit action
    2. Certificate indicator with allow action
    3. Domain indicator with alert only
    4. File hash indicator with block and remediate action Correct answer.

    Explanation

    A file hash custom indicator set to block and remediate prevents execution and removes the file on onboarded devices. Allow actions permit rather than block, and audit or alert-only actions do not enforce blocking.

  91. Question 91Respond to security incidents

    An analyst is investigating a multi-stage attack and wants to see the sequence of alerts mapped to MITRE ATT&CK tactics within the incident. Which Defender XDR view provides this?

    1. The data connector status page
    2. The incident attack story timeline Correct answer.
    3. The secure score breakdown
    4. The device compliance report

    Explanation

    The incident attack story timeline orders alerts and maps them to MITRE ATT&CK tactics, helping analysts understand the attack progression. Compliance reports, secure score breakdowns, and connector status pages do not show attack sequencing.

  92. Question 92Respond to security incidents

    A Sentinel automation rule must run a playbook only for incidents with high severity. Which configuration enforces this condition?

    1. Add a condition on severity in the automation rule trigger Correct answer.
    2. Enable the playbook in the analytics rule query
    3. Attach the playbook to a workbook
    4. Set the playbook to run on a schedule

    Explanation

    Automation rules support conditions such as severity, so the run playbook action executes only when the condition matches. Scheduling changes when a playbook runs but not the incident condition, and queries or workbooks cannot gate playbook execution by severity.

  93. Question 93Respond to security incidents

    In Microsoft Defender XDR, which incident feature groups related alerts from multiple workloads into a single investigation record?

    1. Alert classification
    2. Alert suppression
    3. Alert tuning
    4. Alert correlation Correct answer.

    Explanation

    Incident correlation combines alerts that share entities such as users, devices, or mailboxes into one incident so analysts investigate the attack as a whole rather than alert by alert. Tuning and suppression instead reduce or silence noise and do not build a unified investigation record.

  94. Question 94Respond to security incidents

    An analyst resolves a Defender XDR incident and wants to record whether it was a true positive or a false positive. Which incident field captures this?

    1. Status
    2. Determination Correct answer.
    3. Severity
    4. Assigned to

    Explanation

    The determination field records the analyst's conclusion about the incident, such as true positive, false positive, or informational. Status tracks the workflow state, and severity reflects impact, so neither records the verdict.

  95. Question 95Respond to security incidents

    An analyst wants to use advanced hunting in Microsoft Defender XDR to find all alerts linked to a specific incident. Which table should the analyst query?

    1. DeviceProcessEvents
    2. EmailEvents
    3. AlertInfo Correct answer.
    4. IdentityLogonEvents

    Explanation

    AlertInfo holds alert records, including the incident identifier, so it can be filtered to list alerts belonging to a given incident. The other tables contain raw telemetry such as process, sign-in, or email events rather than alert metadata.

  96. Question 96Respond to security incidents

    Which Microsoft Sentinel feature lets an analyst run a saved query and view results alongside an incident without writing new KQL each time?

    1. Watchlist
    2. Analytics rule
    3. Hunting query Correct answer.
    4. Workbook

    Explanation

    Hunting queries are saved KQL queries that analysts can run repeatedly and launch from an incident to gather supporting evidence. Workbooks visualize data, watchlists supply reference data, and analytics rules generate alerts rather than ad hoc investigation queries.

  97. Question 97Respond to security incidents

    A Defender for Endpoint analyst wants to run a predefined remediation script on a device from the portal without opening a remote session. Which action should the analyst use?

    1. Collect investigation package
    2. Initiate Live Response Correct answer.
    3. Restrict app execution
    4. Run antivirus scan

    Explanation

    Live Response provides a remote shell on the device where analysts can run approved scripts and commands for investigation or remediation. Antivirus scan and investigation package collection gather data but do not execute custom remediation scripts.

  98. Question 98Respond to security incidents

    When an analyst marks a Defender XDR incident as a false positive, what is the primary benefit for future alert handling?

    1. The alert is deleted from all history
    2. Similar alerts can be automatically resolved or tuned Correct answer.
    3. The affected device is automatically isolated
    4. The user account is disabled

    Explanation

    Recording a false positive determination gives the platform feedback that can drive automatic resolution of similar alerts and inform tuning. It does not delete history, isolate devices, or disable accounts, since those are separate response actions.

  99. Question 99Respond to security incidents

    An analyst wants to see the full audit trail of actions taken on a Microsoft Sentinel incident, including status changes. Which incident element provides this?

    1. Alert grouping
    2. Incident activity log Correct answer.
    3. Entities pane
    4. Owner field

    Explanation

    The incident activity log records comments and changes such as status updates and assignments, providing an audit trail. Entities list involved resources and the owner field only shows current assignment, so neither gives history.

  100. Question 100Respond to security incidents

    Which Microsoft Sentinel component stores lists of known malicious IP addresses that analytics rules can reference during detection?

    1. Watchlist Correct answer.
    2. Data connector
    3. Workbook
    4. Playbook

    Explanation

    A watchlist holds reference data such as threat indicators that rules and queries can join against to enrich detections. Playbooks automate responses, workbooks visualize data, and connectors ingest logs.

  101. Question 101Respond to security incidents

    An analyst investigating a Defender XDR incident needs to see all alerts that share the same compromised user account across incidents. Which approach is most efficient?

    1. Run an antivirus scan
    2. Query AlertInfo filtered by the account Correct answer.
    3. Open each incident manually
    4. Export all device events

    Explanation

    Advanced hunting against AlertInfo can filter by the user entity to surface every alert referencing that account across incidents in one query. Manual review and unrelated data exports do not efficiently correlate the account across incidents.

  102. Question 102Respond to security incidents

    A Sentinel incident should be escalated to a senior analyst only when it contains an entity of type IP address. Which automation rule condition accomplishes this?

    1. Incident contains entity type IP Correct answer.
    2. Incident severity equals High
    3. Incident provider name equals Microsoft Defender XDR
    4. Incident title contains a keyword

    Explanation

    Automation rule conditions can evaluate incident entities, so a condition on entity type IP triggers only when an IP entity is present. Title, severity, and provider conditions test other attributes and cannot detect entity types.

  103. Question 103Respond to security incidents

    During a Defender for Endpoint investigation, an analyst confirms a file is malicious and wants to prevent it from running on other devices. Which response action is most appropriate?

    1. Stop and quarantine the file Correct answer.
    2. Run antivirus scan
    3. Restrict app execution
    4. Collect investigation package

    Explanation

    Stop and quarantine blocks the file and removes it from the device, and the indicator can be extended to other devices for prevention. Investigation packages and scans gather data, and app restriction is broader than the single confirmed file.

  104. Question 104Respond to security incidents

    An analyst wants to add a custom indicator for a malicious domain so Defender for Endpoint blocks connections to it. Which indicator type should be created?

    1. File hash
    2. IP address
    3. Domain name or URL Correct answer.
    4. Certificate

    Explanation

    To block traffic to a malicious domain, the analyst creates a domain name or URL indicator with a block action. File hash and certificate indicators apply to files and signing certificates, and IP indicators apply to addresses rather than hostnames.

  105. Question 105Respond to security incidents

    A phishing campaign delivered a malicious attachment to many mailboxes. Which Defender for Office 365 capability lets an analyst find and remove all copies after delivery?

    1. Threat Explorer with soft delete Correct answer.
    2. Safe Links policy
    3. Quarantine policy
    4. Anti-spam policy

    Explanation

    Threat Explorer identifies delivered messages matching the campaign, and the soft delete action removes them from mailboxes after delivery. Safe Links, anti-spam, and quarantine policies act at delivery time rather than purging existing messages.

  106. Question 106Respond to security incidents

    An analyst suspects a compromised account in Defender XDR and wants to see all sign-ins from an unusual location. Which advanced hunting table provides identity sign-in telemetry?

    1. IdentityLogonEvents Correct answer.
    2. DeviceFileEvents
    3. DeviceNetworkEvents
    4. EmailEvents

    Explanation

    IdentityLogonEvents contains authentication telemetry from identity providers, so filtering by location surfaces anomalous sign-ins. Device and email tables record endpoint and mail activity rather than identity authentication events.

  107. Question 107Respond to security incidents

    A Sentinel analyst wants a playbook to post incident details to a chat channel automatically whenever a high-severity incident is created. Which two components are required?

    1. An automation rule and a playbook Correct answer.
    2. A hunting query and a bookmark
    3. A scheduled analytics rule and a workbook
    4. A watchlist and a data connector

    Explanation

    The automation rule detects the incident creation and condition, then invokes a playbook that performs the chat notification. Workbooks, watchlists, connectors, and hunting queries do not trigger automated responses to incidents.

  108. Question 108Respond to security incidents

    An analyst wants to isolate a device from the network while preserving the ability to investigate it. Which Defender for Endpoint action should be used?

    1. Live Response
    2. Full isolation
    3. Selective isolation Correct answer.
    4. Restrict app execution

    Explanation

    Selective isolation limits network access to only what is needed for management and investigation while blocking broader connectivity. Full isolation cuts off more communication, and the other actions do not provide controlled network containment.

  109. Question 109Respond to security incidents

    An analyst needs to review which automated investigation actions were taken on a device and approve pending remediation. Which Defender for Endpoint area provides this?

    1. Threat analytics
    2. Vulnerability management
    3. Action center Correct answer.
    4. Device inventory

    Explanation

    The Action center lists automated and manual response actions, their status, and pending approvals so analysts can review and act. Device inventory, threat analytics, and vulnerability management provide asset and risk information rather than action approvals.

  110. Question 110Respond to security incidents

    A Sentinel incident references a suspicious sign-in and a related mailbox rule change. Which approach best determines whether the two events are linked to the same actor?

    1. Disable the analytics rule
    2. Close both alerts as benign
    3. Delete the mailbox rule
    4. Correlate entities such as the account and IP across both events Correct answer.

    Explanation

    Comparing shared entities like the user account and source IP across the sign-in and mailbox events establishes whether a common actor is involved. Closing alerts, deleting the rule, or disabling detection removes evidence without proving linkage.

  111. Question 111Respond to security incidents

    An analyst wants to review the MITRE ATT&CK tactics covered by alerts in an incident to understand attacker progression. Which Defender XDR view supports this mapping?

    1. Device timeline
    2. Software inventory
    3. Secure score
    4. Incident attack story Correct answer.

    Explanation

    The incident attack story maps alerts to MITRE ATT&CK tactics and stages, showing the progression of the attack. Device timeline shows local events, software inventory lists installed software, and secure score measures posture.

  112. Question 112Respond to security incidents

    An analyst must preserve volatile evidence such as running processes from a device before containing it. Which Defender for Endpoint capability is appropriate?

    1. Device grouping
    2. Antivirus full scan
    3. Live Response session Correct answer.
    4. Full isolation

    Explanation

    A Live Response session allows the analyst to run commands that capture volatile data like running processes before containment changes the system state. Isolation, scans, and device grouping alter or organize devices without collecting volatile artifacts.

  113. Question 113Respond to security incidents

    A Sentinel automation rule must run a playbook only when an incident is created by a specific analytics rule and has high severity. How should the conditions be combined?

    1. Create two separate automation rules that each run the playbook
    2. Use a single condition on severity only
    3. Use an OR condition between the analytics rule name and severity
    4. Combine the analytics rule name and severity conditions with AND logic Correct answer.

    Explanation

    Combining conditions with AND logic ensures the playbook runs only when both the analytics rule name and the severity match. Using OR or a single condition would allow execution when only one criterion is met.

  114. Question 114Respond to security incidents

    An analyst confirms a false positive remediation quarantined a legitimate file on several devices. Which action reverses this in Defender for Endpoint?

    1. Run a full antivirus scan
    2. Isolate the affected devices
    3. Add the file hash as a block indicator
    4. Restore the quarantined file from the action center Correct answer.

    Explanation

    The action center allows the analyst to restore a quarantined file, reverting the remediation on affected devices. Scans, block indicators, and isolation are containment actions that would worsen rather than undo the false positive.

  115. Question 115Respond to security incidents

    An analyst sees repeated low-fidelity alerts from a noisy detection that mask a genuine high-severity incident. Which approach best reduces noise while preserving visibility of the real threat?

    1. Tune or suppress only the noisy detection and keep high-severity detections active Correct answer.
    2. Turn off incident creation for all rules
    3. Disable all analytics rules in the workspace
    4. Lower the severity of every incident

    Explanation

    Targeted tuning or suppression of the noisy detection reduces clutter while high-severity detections remain active to surface the real threat. Broad disabling or severity changes would hide genuine incidents along with the noise.

  116. Question 116Respond to security incidents

    During a multi-stage incident, an analyst needs to determine the initial access vector before scoping containment. Which evidence is most relevant to review first?

    1. The most recent alert only
    2. The earliest alert in the attack story and its related entities Correct answer.
    3. The organization's secure score
    4. The device's installed software list

    Explanation

    The initial access vector is best identified from the earliest alert in the attack story and the entities it involves, which reveals how the attacker entered. Later alerts show subsequent stages, and inventory or posture data do not identify the entry point.

  117. Question 117Respond to security incidents

    In Microsoft Sentinel, which entity type represents a user account referenced by an incident and can be used to pivot to related activity?

    1. Mailbox
    2. Host
    3. Account Correct answer.
    4. FileHash

    Explanation

    Sentinel classifies incident entities into types such as Account, Host, IP, FileHash, URL, and Mailbox. The Account entity maps to user identities so analysts can pivot across incidents that involve the same identity.

  118. Question 118Respond to security incidents

    Which Microsoft Sentinel feature lets an analyst manually correlate multiple alerts and entities into a single investigation record?

    1. Configuring a data collection rule
    2. Enabling UEBA on the workspace
    3. Publishing a workbook to a dashboard
    4. Creating a new incident manually and adding alerts and entities Correct answer.

    Explanation

    Analysts can create incidents manually in Sentinel and attach relevant alerts and entities, which groups related signals into one investigation record. This is useful when automated correlation does not group related activity together.

  119. Question 119Respond to security incidents

    When an analyst closes a Microsoft Sentinel incident, which field documents the reason so reporting can distinguish true positives from benign activity?

    1. Severity
    2. Classification Correct answer.
    3. Owner
    4. Status

    Explanation

    The classification field records whether an incident was a true positive, false positive, or benign positive, along with a reason. This classification supports metrics and tuning of detections.

  120. Question 120Respond to security incidents

    An analyst wants to add a comment to a Microsoft Sentinel incident so other analysts see investigation notes directly on the incident. Which action accomplishes this?

    1. Edit the analytics rule query to include the note
    2. Tag the incident with a custom severity label
    3. Post the note in the incident's activity log comments Correct answer.
    4. Create a new watchlist containing the note

    Explanation

    Sentinel incidents include a comments area in the activity log where analysts add investigation notes visible to the team. Comments are timestamped and preserved with the incident record.

  121. Question 121Respond to security incidents

    Which Microsoft Defender XDR capability automatically groups related alerts across workloads into a single incident for triage?

    1. Device onboarding
    2. Incident correlation Correct answer.
    3. Attack simulation training
    4. Advanced hunting

    Explanation

    Defender XDR correlates alerts from endpoints, identities, email, and cloud apps into incidents so analysts triage related activity together. This reduces duplicate work compared with handling each alert separately.

  122. Question 122Respond to security incidents

    An analyst wants to run a KQL query across Microsoft Sentinel and Defender XDR data in one place to investigate an incident. Which capability supports this?

    1. Defender for Cloud Apps activity log export
    2. Advanced hunting with the unified Microsoft 365 Defender portal Correct answer.
    3. Log Analytics workspace-only queries
    4. Sentinel workbook templates

    Explanation

    Advanced hunting in the unified portal allows KQL queries across Defender XDR and, when connected, Sentinel data. This gives analysts a single query surface for cross-workload investigation.

  123. Question 123Respond to security incidents

    A Sentinel incident involves a compromised account. The analyst wants to disable the account in Microsoft Entra ID as part of response. Which approach performs this action from Sentinel?

    1. Trigger a playbook that calls the Microsoft Entra ID connector to disable the user Correct answer.
    2. Enable entity behavior analytics for the workspace
    3. Add the account entity to a watchlist
    4. Change the incident severity to High

    Explanation

    Sentinel playbooks built on Logic Apps can call connectors, including Microsoft Entra ID actions, to disable a user as an automated or manual response step. This executes the response action outside Sentinel through the connector.

  124. Question 124Respond to security incidents

    An analyst wants to automatically assign every new high-severity Sentinel incident to a specific owner group. Which Sentinel feature should be configured?

    1. A data connector for Microsoft Defender XDR
    2. A scheduled analytics rule with entity mapping
    3. A workbook with a filter parameter
    4. An automation rule with an owner assignment action Correct answer.

    Explanation

    Automation rules evaluate incident conditions and can assign owners, change severity, add tags, or run playbooks. Owner assignment on high-severity incidents is a typical automation rule action.

  125. Question 125Respond to security incidents

    During triage, an analyst wants to see which devices in the organization communicated with a malicious IP found in an incident. Which Defender XDR approach best answers this?

    1. Export the incident to CSV and filter by title
    2. Run an advanced hunting query against device network events for the IP Correct answer.
    3. Review the incident's MITRE tactic mapping
    4. Open the incident's alert list and sort by severity

    Explanation

    Advanced hunting queries against device network event tables reveal all devices that connected to a given remote IP. This scopes the blast radius beyond the originally alerted device.

  126. Question 126Respond to security incidents

    An analyst needs to review the timeline of alerts and actions within a Defender XDR incident to understand the sequence of events. Which incident view provides this?

    1. The device inventory report
    2. The incident timeline and attack story view Correct answer.
    3. The email threat explorer
    4. The secure score recommendations page

    Explanation

    The incident attack story and timeline present alerts, entities, and actions in chronological order, helping analysts reconstruct the sequence. This supports understanding how the attack progressed.

  127. Question 127Respond to security incidents

    An analyst wants to suppress a specific known-benign alert from repeatedly creating new incidents while keeping the detection rule active. Which Sentinel capability fits best?

    1. Disable the data connector feeding the workspace
    2. Delete the analytics rule that generates the alert
    3. Remove the entity mapping from the analytics rule
    4. Configure alert grouping or an automation rule that closes matching incidents Correct answer.

    Explanation

    Alert grouping settings and automation rules can close or merge matching benign incidents without disabling detection. This preserves visibility while reducing noise.

  128. Question 128Respond to security incidents

    An analyst confirms a user account was compromised and wants to revoke active sessions in addition to resetting the password. Which Microsoft Entra ID response action accomplishes session revocation?

    1. Require MFA re-registration only
    2. Remove the user from all groups
    3. Disable conditional access policies
    4. Revoke sessions for the user Correct answer.

    Explanation

    Revoking sessions invalidates refresh tokens so existing sessions cannot continue, which is essential when a token may be stolen. Password reset alone does not terminate already-issued sessions.

  129. Question 129Respond to security incidents

    A Sentinel analyst wants to attach a custom entity such as a project identifier to incidents so playbooks can read it. Which approach enables this?

    1. Create a new Log Analytics workspace
    2. Enable the Microsoft Sentinel auditing connector
    3. Increase the incident severity threshold
    4. Define a custom entity or use incident labels and map the value in the analytics rule Correct answer.

    Explanation

    Analytics rules can map custom entities or incident labels that playbooks and automation rules can reference. This extends incident context beyond built-in entity types.

  130. Question 130Respond to security incidents

    An analyst is investigating a multi-stage incident and wants to identify which alerts were raised by the same analytics rule over time to spot recurring patterns. Which Sentinel query approach is most direct?

    1. Query the Watchlist table for reference data
    2. Query the Usage table for ingestion volume
    3. Query the SecurityAlert table filtering by the rule's product name or alert name Correct answer.
    4. Query the Heartbeat table for agent status

    Explanation

    The SecurityAlert table stores alert records, including names and product sources, so filtering reveals recurring alerts from the same rule. This supports identifying repeat patterns during investigation.

  131. Question 131Respond to security incidents

    An analyst wants to test a new Sentinel automation rule that runs a playbook without affecting production incidents. Which practice is appropriate?

    1. Run the playbook directly against production incidents
    2. Create a test incident matching the rule conditions in a non-production workspace or with a scoped condition Correct answer.
    3. Disable all analytics rules during the test
    4. Delete the automation rule after the first production run

    Explanation

    Testing in a non-production workspace or with narrowly scoped conditions validates the playbook without disrupting live response. This isolates test effects from real incidents.

  132. Question 132Respond to security incidents

    An analyst needs to determine whether a suspicious email that triggered an incident was delivered to other recipients. Which Defender for Office 365 capability supports this investigation?

    1. Attack surface reduction rule reports
    2. Threat Explorer with a filter on the sender or subject Correct answer.
    3. Secure score improvement actions
    4. Device timeline in Defender for Endpoint

    Explanation

    Threat Explorer lets analysts search email events by sender, subject, or URL to find all recipients of a campaign. This scopes delivery beyond the initially reported message.

  133. Question 133Respond to security incidents

    An analyst wants to view the raw alert evidence collected for a Defender XDR incident to verify what triggered detection. Which location provides this?

    1. The Defender for Cloud regulatory compliance page
    2. The Sentinel workspace usage report
    3. The Microsoft 365 service health dashboard
    4. The alert details page with the evidence and entities tab Correct answer.

    Explanation

    Alert details include an evidence and entities section showing the artifacts that triggered detection, such as files, processes, or IPs. Reviewing evidence verifies the detection basis before response.

  134. Question 134Respond to security incidents

    An analyst wants to coordinate response by linking a Sentinel incident to a related Defender XDR incident so the team sees one investigation record. Which capability supports cross-platform incident linking?

    1. The unified incident view in the Microsoft Defender portal with Sentinel connected Correct answer.
    2. A separate workbook per platform
    3. A watchlist of incident IDs
    4. Duplicate incident creation in both portals

    Explanation

    Connecting Sentinel to the Defender portal surfaces Sentinel incidents alongside Defender XDR incidents in a unified view. Analysts can then triage related activity in one place.

  135. Question 135Perform threat hunting

    In Microsoft Sentinel, which component stores the raw security events that KQL queries run against?

    1. The Log Analytics workspace Correct answer.
    2. The automation rule engine
    3. The incident queue
    4. The watchlist table

    Explanation

    Sentinel stores ingested security data in an underlying Log Analytics workspace, and every hunting query, analytics rule, and workbook reads from that workspace's tables. Incidents, watchlists, and automation are built on top of that data rather than holding the raw events themselves.

  136. Question 136Perform threat hunting

    Which KQL operator removes duplicate rows from a result set based on specified columns?

    1. project
    2. distinct Correct answer.
    3. summarize
    4. extend

    Explanation

    The distinct operator returns a unique set of rows for the columns you list, which is useful when you want to see each unique value once. summarize aggregates rows using functions such as count or dcount, and project and extend manipulate columns rather than deduplicate rows.

  137. Question 137Perform threat hunting

    An analyst wants to compare this week's sign-in volume against the same period last week in one query. Which approach fits best?

    1. Create a watchlist containing last week's counts
    2. Run two separate queries and compare the totals by hand
    3. Use the ago() function with a time window and summarize by bin Correct answer.
    4. Export both weeks to CSV and diff the files

    Explanation

    A single query can use a time filter such as TimeGenerated > ago(14d) and then summarize by bin(TimeGenerated, 1d) to produce a daily series spanning both weeks. The resulting chart or table shows both periods side by side without manual export or extra artifacts.

  138. Question 138Perform threat hunting

    What is the primary purpose of a hunting query saved as a custom detection in Microsoft Defender XDR?

    1. To block the matched activity automatically at the endpoint
    2. To convert the hunting logic into an alert-generating custom detection rule Correct answer.
    3. To lower the retention cost of advanced hunting tables
    4. To export raw telemetry to a third-party SIEM

    Explanation

    Advanced hunting queries that find malicious behavior can be promoted to custom detections, which run on a schedule and generate alerts and incidents when matches occur. Blocking is handled by indicators or device controls, and export or retention are separate configuration concerns.

  139. Question 139Perform threat hunting

    In Microsoft Defender XDR advanced hunting, which operator lets you correlate two tables on a shared key such as DeviceId?

    1. union
    2. summarize
    3. where
    4. join Correct answer.

    Explanation

    The join operator merges rows from two tables where the values of specified columns match, which is how analysts pivot from a process event to related network or identity events for the same device. union appends rows, summarize aggregates, and where filters.

  140. Question 140Perform threat hunting

    An analyst needs to find devices that ran a suspicious process and also made an outbound connection to a rare domain within ten minutes. Which technique is most appropriate?

    1. Search each table separately and eyeball the timestamps
    2. Use summarize count() on DeviceProcessEvents only
    3. Filter DeviceNetworkEvents by a single known-bad IP address
    4. Join DeviceProcessEvents and DeviceNetworkEvents on DeviceId with a time-bound condition Correct answer.

    Explanation

    Correlating the two tables on DeviceId while constraining the network event timestamp relative to the process timestamp isolates the sequence of interest. This time-bound join is the standard way to express causal chains across different telemetry tables.

  141. Question 141Perform threat hunting

    Which Microsoft Sentinel feature lets you run a hunting query and then bookmark individual rows as evidence for later investigation?

    1. Workbooks
    2. Data connectors
    3. Hunting bookmarks Correct answer.
    4. Analytics rules

    Explanation

    Bookmarks capture specific rows returned by a hunting query along with notes and tags, and they can be linked to incidents as evidence. Analytics rules generate alerts, workbooks visualize data, and connectors bring data in.

  142. Question 142Perform threat hunting

    What is the main advantage of using a Sentinel watchlist during threat hunting?

    1. It replaces the need for analytics rules
    2. It automatically remediates matched entities
    3. It stores high-volume raw logs at a lower cost
    4. It provides a reference list for lookups and enrichment in queries Correct answer.

    Explanation

    Watchlists hold curated reference data such as VIP users, high-value assets, or indicators, and queries can join against them with the _GetWatchlist function. They enrich and filter results rather than storing telemetry, remediating, or replacing detections.

  143. Question 143Perform threat hunting

    An analyst wants to surface accounts with an unusually high number of failed sign-ins compared with their own normal baseline. Which approach best fits?

    1. Disable the accounts with any failed sign-in
    2. Alert on every single failed sign-in event
    3. Use make-series or summarize by account and compare against a learned baseline Correct answer.
    4. Filter for a fixed threshold of ten failures per hour for every account

    Explanation

    Behavioral hunting compares each entity against its own historical norm, often using make-series plus series_decompose_anomalies or a computed baseline average. Fixed thresholds ignore per-account variation, and reacting to every failure or disabling accounts is disruptive and noisy.

  144. Question 144Perform threat hunting

    In KQL, which function returns the number of distinct values in a column?

    1. sum()
    2. countif()
    3. dcount() Correct answer.
    4. count()

    Explanation

    dcount() estimates the number of unique values in a column, which is useful for measuring how many distinct hosts, users, or IP addresses appear. count() counts rows, countif() counts rows meeting a predicate, and sum() adds numeric values.

  145. Question 145Perform threat hunting

    A hunter wants to identify rare parent-child process relationships that could indicate malicious spawning. Which query pattern is most suitable?

    1. Summarize count() by InitiatingProcessFileName and ProcessCommandLine, then sort ascending Correct answer.
    2. Filter for a list of known-good parent processes only
    3. Remove all rows where the process is signed
    4. Project only the ProcessCommandLine column

    Explanation

    Counting occurrences of each parent-child command combination and sorting ascending surfaces the rarest relationships, which are often the most suspicious. This frequency analysis is a core hunting pattern for detecting unusual process lineage.

  146. Question 146Perform threat hunting

    What does the DeviceFileEvents table in Defender XDR advanced hunting primarily record?

    1. Network connections initiated by processes
    2. Registry key modifications
    3. User sign-in and authentication events
    4. File creation, modification, and deletion activity on devices Correct answer.

    Explanation

    DeviceFileEvents captures file system activity such as creation, modification, renaming, and deletion, along with the initiating process. Network, identity, and registry activity live in other tables such as DeviceNetworkEvents, identity logs, and DeviceRegistryEvents.

  147. Question 147Perform threat hunting

    An analyst suspects lateral movement using remote service creation. Which advanced hunting table and field combination is most directly relevant?

    1. DeviceNetworkEvents filtered on RemoteIPType
    2. DeviceInfo filtered on OSPlatform
    3. DeviceFileEvents filtered on FolderPath
    4. DeviceProcessEvents filtered on ProcessCommandLine containing service creation indicators Correct answer.

    Explanation

    Lateral movement via remote service creation appears as service or sc.exe commands with remote host parameters in process command lines. Inspecting ProcessCommandLine in DeviceProcessEvents exposes those invocations and their parent processes.

  148. Question 148Perform threat hunting

    What is the purpose of the DeviceTvmSoftwareVulnerabilities table in advanced hunting?

    1. It records every outbound network connection
    2. It contains identity risk detections
    3. It stores email attachment metadata
    4. It lists software installed on devices with known vulnerability identifiers Correct answer.

    Explanation

    This table pairs installed software inventory with known vulnerability identifiers so hunters can find devices exposed to specific CVEs. Network, email, and identity data live in separate tables.

  149. Question 149Perform threat hunting

    A hunter wants to find devices that communicated with an IP address that also appears in threat intelligence indicators. Which approach is most efficient?

    1. Join DeviceNetworkEvents against the ThreatIntelligenceIndicator table on the remote IP Correct answer.
    2. Filter DeviceNetworkEvents by port 443 only
    3. Export all network events and search them in a spreadsheet
    4. Query DeviceNetworkEvents and manually scan every remote IP

    Explanation

    Sentinel and Defender expose threat intelligence indicators in a dedicated table, and joining network telemetry to it on the remote IP field matches observed traffic to known indicators. This scales far better than manual review and avoids unnecessary narrowing.

  150. Question 150Perform threat hunting

    Which Sentinel entity type would represent a user account extracted from a query result for use in an incident investigation?

    1. Host
    2. FileHash
    3. Account Correct answer.
    4. IP

    Explanation

    Sentinel maps extracted values to entity types, and a user account or UPN is represented by the Account entity. Host represents devices, IP represents network addresses, and FileHash represents file indicators.

  151. Question 151Perform threat hunting

    An analyst wants to detect beaconing behavior, where a host contacts the same destination at regular intervals. Which analytic approach is most appropriate?

    1. List all distinct destination ports per host
    2. Compute the time deltas between connections per host-destination pair and look for low variance Correct answer.
    3. Count total connections per host and alert on the highest counts
    4. Filter for connections to port 53 only

    Explanation

    Beaconing shows up as repeated connections to the same destination with fairly consistent intervals, so calculating inter-arrival deltas and measuring their variance reveals regularity. High total counts or port listings do not capture the timing pattern that defines beaconing.

  152. Question 152Perform threat hunting

    What does the summarize operator do when combined with the bin() function on a timestamp column?

    1. It removes duplicate timestamps from the table
    2. It converts timestamps to a different time zone
    3. It groups events into fixed time buckets for aggregation Correct answer.
    4. It joins two tables on the timestamp

    Explanation

    bin() rounds a timestamp down to a fixed interval such as one hour, and summarize then aggregates rows within each bucket. This produces time-series counts suitable for charting trends or spotting spikes.

  153. Question 153Perform threat hunting

    A hunter needs to review activity for a specific compromised user across identity and endpoint telemetry. Which pivot is most useful?

    1. Sort the incident queue by severity
    2. Join identity sign-in events with endpoint events on the account name or user identifier Correct answer.
    3. Filter only endpoint process events by device name
    4. Query the watchlist table for the username

    Explanation

    Correlating identity sign-in data with endpoint telemetry on the account identifier connects authentication activity to actions taken on devices. This cross-domain pivot is essential when tracing a compromised user's footprint.

  154. Question 154Perform threat hunting

    Which KQL operator would you use to add a calculated column, such as extracting the file extension, to each row of a result set?

    1. project-away
    2. extend Correct answer.
    3. distinct
    4. take

    Explanation

    extend creates new calculated columns from expressions evaluated per row, such as parsing a file extension from a path. project-away removes columns, take limits row count, and distinct deduplicates rows.

  155. Question 155Perform threat hunting

    An analyst wants to hunt for living-off-the-land binaries used for download. Which query is most targeted?

    1. Filter DeviceFileEvents by file size
    2. Search DeviceProcessEvents for processes such as certutil or bitsadmin with URL-related arguments Correct answer.
    3. Query DeviceInfo for the operating system build
    4. List all processes that ran on every device

    Explanation

    Living-off-the-land downloads typically abuse signed system utilities like certutil or bitsadmin with URL arguments, so filtering process command lines for those binaries and URL indicators is targeted. Broad process listings or unrelated tables produce noise without addressing the technique.

  156. Question 156Perform threat hunting

    In Sentinel, which capability allows a scheduled analytics rule to automatically create an incident and run a playbook in response?

    1. Workbooks
    2. Hunting bookmarks
    3. Watchlist updates
    4. Automation rules combined with a playbook Correct answer.

    Explanation

    Automation rules trigger when incidents are created or updated and can invoke a playbook through a Logic Apps connector. Bookmarks, workbooks, and watchlists support investigation and visualization but do not drive automated response.

  157. Question 157Perform threat hunting

    A hunter observes a spike in SMB connections from a workstation to many internal hosts. Which hypothesis is most consistent with this pattern?

    1. The workstation is performing normal software updates
    2. The workstation has a failing disk
    3. The workstation is syncing its clock with a time server
    4. The workstation may be conducting internal reconnaissance or lateral movement Correct answer.

    Explanation

    Many SMB connections to numerous internal hosts in a short window suggest scanning or lateral movement, such as credential-based propagation. Update traffic and clock sync typically target a small number of external or designated servers.

  158. Question 158Perform threat hunting

    Which statement best describes how advanced hunting differs from a scheduled custom detection?

    1. Advanced hunting only works on identity data, while custom detections only work on device data
    2. Advanced hunting runs queries interactively on demand, while custom detections run on a schedule and raise alerts Correct answer.
    3. Advanced hunting retains data longer than custom detections
    4. Advanced hunting requires a playbook, while custom detections do not

    Explanation

    Advanced hunting is an interactive query experience where the analyst runs queries and inspects results in the portal. A custom detection wraps a query so it runs automatically on a schedule and generates alerts when matches appear.

  159. Question 159Perform threat hunting

    An analyst needs to identify hosts that resolved a suspicious domain and then connected to a newly seen IP. Which sequence of tables best supports this hunt?

    1. DeviceInfo followed by DeviceTvmSoftwareInventory
    2. IdentityLogonEvents followed by IdentityQueryEvents
    3. EmailEvents followed by EmailAttachmentInfo
    4. DeviceEvents for DNS queries followed by DeviceNetworkEvents for connections Correct answer.

    Explanation

    DNS query telemetry in DeviceEvents reveals which hosts resolved the domain, and DeviceNetworkEvents then shows subsequent connections to the resulting address. Chaining these tables in time order reconstructs the resolution-to-connection sequence.

  160. Question 160Perform threat hunting

    In Microsoft Sentinel, which hunting artifact stores a query result row so an analyst can attach it to an incident as supporting evidence?

    1. Saved search
    2. Bookmark Correct answer.
    3. Workbook
    4. Watchlist

    Explanation

    A bookmark captures a specific row of hunting query output together with its column values and any analyst notes, and it can later be promoted into an incident as evidence. Watchlists store reference data for enrichment and filtering, not individual findings.

  161. Question 161Perform threat hunting

    Which advanced hunting table in Microsoft Defender XDR contains records of processes started on devices, including command lines and account context?

    1. DeviceNetworkEvents
    2. DeviceLogonEvents
    3. DeviceProcessEvents Correct answer.
    4. DeviceRegistryEvents

    Explanation

    DeviceProcessEvents records process creation and related details such as file name, command line, initiating account, and parent process. The other tables record network, registry, and logon activity respectively.

  162. Question 162Perform threat hunting

    Which KQL operator groups rows that share the same values in specified columns and computes aggregates over each group?

    1. project
    2. extend
    3. distinct
    4. summarize Correct answer.

    Explanation

    summarize aggregates rows by the columns named in the by clause and produces one output row per group. It is the standard operator for counting, averaging, or otherwise reducing telemetry into grouped results.

  163. Question 163Perform threat hunting

    An analyst wants to hunt for accounts that signed in successfully from a country they have never used before. Which approach best supports this hunt?

    1. Filter sign-ins to those originating from known corporate IP ranges
    2. List every sign-in event where the result type equals zero
    3. Count all successful sign-ins per hour across the tenant
    4. Compare each user's sign-in country against their historical country baseline Correct answer.

    Explanation

    Building a per-user baseline of previously observed countries and then flagging first-time countries highlights anomalous travel or credential misuse. Comparing against each user's own history reduces noise from legitimately global workforces.

  164. Question 164Perform threat hunting

    What is the primary purpose of entity mapping when configuring a Sentinel analytics rule?

    1. To encrypt incident data at rest
    2. To link accounts, hosts, and IPs from results to incident entities Correct answer.
    3. To schedule the rule at fixed intervals
    4. To convert query results into chart visualizations

    Explanation

    Entity mapping extracts identifiers such as account names, host names, and IP addresses from the rule's query output and attaches them to the incident as entities. Those entities then drive investigation graphs, entity pages, and automated playbook inputs.

  165. Question 165Perform threat hunting

    Which KQL operator filters a table to rows whose value in a column appears in another table or a dynamic array?

    1. in Correct answer.
    2. union
    3. lookup
    4. join

    Explanation

    The in operator tests membership, letting an analyst keep only rows whose column value exists in a supplied list or subquery. It is a concise way to filter telemetry against a set of indicators.

  166. Question 166Perform threat hunting

    Which Microsoft Sentinel component lets an analyst run an ad hoc hunting query on demand rather than on a schedule?

    1. Logs blade hunting queries Correct answer.
    2. Analytics rule
    3. Data connector
    4. Automation rule

    Explanation

    The hunting queries experience in the Logs area lets analysts execute queries interactively, review results, and create bookmarks. Scheduled detections and automated responses are separate features.

  167. Question 167Perform threat hunting

    A hunter wants to see how many distinct devices contacted each remote IP address in the past day. Which query shape produces that result?

    1. DeviceNetworkEvents | where Timestamp > ago(1d) | distinct RemoteIP
    2. DeviceNetworkEvents | where Timestamp > ago(1d) | extend Day = bin(Timestamp, 1d)
    3. DeviceNetworkEvents | where Timestamp > ago(1d) | project DeviceName, RemoteIP
    4. DeviceNetworkEvents | where Timestamp > ago(1d) | summarize dcount(DeviceId) by RemoteIP Correct answer.

    Explanation

    Grouping by RemoteIP and applying dcount to the device identifier yields the number of unique devices per destination address. This surfaces destinations contacted by many hosts, which may indicate shared infrastructure or scanning.

  168. Question 168Perform threat hunting

    An analyst wants to review the full command line used when a suspicious binary launched. Which field in DeviceProcessEvents provides it?

    1. FolderPath
    2. AccountName
    3. ProcessCommandLine Correct answer.
    4. InitiatingProcessFileName

    Explanation

    ProcessCommandLine stores the arguments and switches passed to the launched process, which often reveal encoded payloads or download URLs. This field is central to triaging suspicious executions.

  169. Question 169Perform threat hunting

    A hunter wants to find devices where a script interpreter spawned a command shell, a common pattern in malicious execution chains. Which query best expresses this?

    1. DeviceProcessEvents | where InitiatingProcessFileName == "cmd.exe"
    2. DeviceProcessEvents | summarize count() by DeviceName
    3. DeviceProcessEvents | where InitiatingProcessFileName in~ ("powershell.exe","wscript.exe") and FileName =~ "cmd.exe" Correct answer.
    4. DeviceProcessEvents | where FileName == "powershell.exe"

    Explanation

    Filtering on a parent process of a script interpreter and a child process of cmd.exe captures the interpreter-to-shell chain while excluding unrelated shell activity. The in~ and =~ operators make the comparison case-insensitive.

  170. Question 170Perform threat hunting

    Which statement describes the role of a Sentinel watchlist in an investigation?

    1. It automatically blocks IP addresses at the firewall
    2. It stores reference data that queries can join against for enrichment or filtering Correct answer.
    3. It archives raw logs for long-term retention
    4. It replaces the need for analytics rules

    Explanation

    A watchlist holds curated reference data, such as high-value assets or known indicators, that hunting queries and analytics rules can join against. This lets analysts apply organizational context without hardcoding lists in each query.

  171. Question 171Perform threat hunting

    An analyst wants to identify accounts that authenticated to many distinct hosts within a short window, suggesting possible lateral movement. Which query element is essential?

    1. A filter that keeps only failed authentications
    2. A join between sign-in logs and audit logs
    3. A summarize that counts distinct target hosts per account over a time bin Correct answer.
    4. A project that removes the account column

    Explanation

    Grouping by account and time bucket while counting distinct destination hosts reveals accounts touching an unusually broad set of machines quickly. That breadth is the core signal for suspected lateral movement.

  172. Question 172Perform threat hunting

    Which KQL operator is used to combine rows from two tables that share matching key values, enriching one result with columns from the other?

    1. parse
    2. mv-expand
    3. join Correct answer.
    4. union

    Explanation

    join matches rows across two tables on a specified key and returns columns from both, which is how analysts enrich telemetry with reference or asset data. The kind argument controls whether matches are inner, outer, or otherwise.

  173. Question 173Perform threat hunting

    A hunter is reviewing DeviceNetworkEvents and notices repeated connections to the same remote IP at nearly identical intervals over several hours. Which hypothesis does this pattern most directly support?

    1. The device is beaconing to command-and-control infrastructure Correct answer.
    2. The device has a failing network adapter
    3. The device is performing a routine DNS lookup
    4. The device is receiving a legitimate software update

    Explanation

    Highly regular, evenly spaced outbound connections are characteristic of implant beaconing, where malware checks in with command-and-control on a fixed sleep interval. Legitimate update or DNS traffic rarely shows such precise periodicity to a single destination.

  174. Question 174Perform threat hunting

    Which advanced hunting table would an analyst query to find registry modifications that establish persistence via a Run key?

    1. DeviceRegistryEvents Correct answer.
    2. DeviceImageLoadEvents
    3. DeviceEvents
    4. DeviceFileEvents

    Explanation

    DeviceRegistryEvents records registry key and value changes, including the key path and the value name, making it the right source for Run key persistence. Analysts filter on key paths containing Run to spot autostart abuse.

  175. Question 175Perform threat hunting

    An analyst wants to compare this week's process execution frequency against the prior four weeks for each process name. Which technique best supports this?

    1. Sorting the table by the account name
    2. Filtering to processes seen only once in the entire dataset
    3. Projecting only the device name and timestamp
    4. Binning time into weekly buckets and summarizing counts per process name Correct answer.

    Explanation

    Weekly binning combined with counts per process name produces comparable time series that can be pivoted to reveal processes whose volume changed markedly. Deviations from a stable baseline often flag newly introduced or abused binaries.

  176. Question 176Perform threat hunting

    What distinguishes a custom detection in Defender XDR from an ad hoc advanced hunting query?

    1. Ad hoc queries always generate incidents automatically
    2. Custom detections run on a schedule and can raise alerts and take response actions Correct answer.
    3. Custom detections can only be written in PowerShell
    4. Ad hoc queries cannot use the summarize operator

    Explanation

    A custom detection packages a hunting query with a schedule and alert definition so it runs continuously and can trigger alerts and automated response actions. An ad hoc query is executed manually and produces results only for the analyst running it.

  177. Question 177Perform threat hunting

    A hunter wants to find hosts that resolved a suspicious domain and shortly afterward connected to an IP address not previously seen in the environment. Which sequence of steps is most appropriate?

    1. Search DNS events for the domain, then correlate the same devices to network events involving newly observed IPs within a time window Correct answer.
    2. Search only for the domain and stop after listing matching devices
    3. Search file events for executables named after the domain
    4. Search all network events for the past year and sort by byte count

    Explanation

    The hunt requires two stages: identify devices that resolved the domain, then pivot on those devices to find subsequent connections to IPs absent from the historical baseline. Constraining the correlation to a short window after resolution keeps the results meaningful.

  178. Question 178Perform threat hunting

    Which KQL function extracts a substring matching a regular expression from a string column during a hunt?

    1. extract Correct answer.
    2. split
    3. tostring
    4. strcat

    Explanation

    extract applies a regular expression to a string and returns the captured group, which is useful for pulling domains, hashes, or encoded fragments out of command lines. The other functions convert types, concatenate, or split without regex capture.

  179. Question 179Perform threat hunting

    An analyst needs to find devices where an encoded PowerShell command was executed. Which filter is most precise?

    1. AccountName has "system"
    2. InitiatingProcessFileName =~ "explorer.exe"
    3. ProcessCommandLine has "-enc" Correct answer.
    4. FileName =~ "powershell.exe"

    Explanation

    Encoded PowerShell is invoked with switches such as -enc or -encodedcommand, so searching the command line for those tokens targets the behavior directly. Matching the binary name alone returns all PowerShell use, most of which is benign.

  180. Question 180Perform threat hunting

    Which Sentinel capability allows an analyst to automatically add a suspicious entity to a watchlist when an incident is created?

    1. A playbook triggered by an automation rule Correct answer.
    2. A data connector
    3. A retention policy
    4. A workbook template

    Explanation

    Automation rules can invoke playbooks in response to incident creation, and the playbook can call the watchlist API to append the entity. This closes the loop between detection and future enrichment.

  181. Question 181Perform threat hunting

    A hunter observes a workstation making SMB connections to dozens of internal hosts in a few minutes. Which hypothesis is most consistent with this behavior?

    1. The workstation is enumerating or moving laterally across the network Correct answer.
    2. The workstation is resolving external DNS names
    3. The workstation is backing up to a local disk
    4. The workstation is downloading Windows updates

    Explanation

    Rapid SMB connections to many internal hosts fit either network reconnaissance or lateral movement using stolen credentials. Benign causes such as inventory tools exist, but the breadth and speed are the key anomaly to validate against the asset baseline.

  182. Question 182Perform threat hunting

    An analyst wants to detect a rare parent-child process pair by comparing each pair's frequency against the total number of executions on the same device. Which approach is most appropriate?

    1. Filter to processes whose names contain the word update
    2. Count all processes per device and alert on the highest totals
    3. List every process where the account is a service account
    4. Compute the ratio of each parent-child pair's count to the device's total process count and filter for very low ratios Correct answer.

    Explanation

    Normalizing each pair's count by the device's overall process volume produces a relative rarity score, which highlights unusual lineage without being skewed by busier machines. Very low ratios combined with low absolute counts are strong candidates for review.

  183. Question 183Perform threat hunting

    During a hunt, an analyst finds that a device contacted an IP address that also appears in a threat intelligence indicator feed. Which enrichment step best increases confidence that the contact is malicious?

    1. Counting how many total connections the device made that day
    2. Reviewing the device's installed software inventory
    3. Listing all users who signed in to the device
    4. Confirming the indicator is active and checking whether the connection occurred during the indicator's validity window Correct answer.

    Explanation

    An indicator match is only meaningful if the indicator is unexpired and the observed connection falls within its validity period. Validating timing and status separates a genuine hit from a stale or coincidental match.

  184. Question 184Perform threat hunting

    A hunter wants to identify files written to disk by a process that was itself launched from a temporary directory. Which query pattern best captures this?

    1. DeviceProcessEvents | summarize count() by FileName
    2. DeviceFileEvents | project Timestamp, DeviceName
    3. DeviceFileEvents | where InitiatingProcessFolderPath has "temp" Correct answer.
    4. DeviceFileEvents | where FolderPath has "temp"

    Explanation

    Filtering file events on the initiating process folder path links the write action to a parent executing from a temporary location, a common staging pattern. This connects the dropped file to its suspicious origin rather than merely flagging temp paths.

  185. Question 185Perform threat hunting

    Which advanced hunting table in Microsoft Defender XDR records logon events such as successful and failed interactive or network sign-ins on devices?

    1. DeviceRegistryEvents
    2. DeviceFileEvents
    3. DeviceLogonEvents Correct answer.
    4. DeviceProcessEvents

    Explanation

    DeviceLogonEvents captures authentication activity on endpoints, including logon type, account name, and success or failure, which makes it the primary table for investigating credential access and lateral movement. The other tables record process creation, file activity, and registry changes rather than authentication events.

  186. Question 186Perform threat hunting

    An analyst wants to summarize how many process executions occurred per device per day during a hunt. Which KQL operator produces that grouped count?

    1. project
    2. extend
    3. distinct
    4. summarize Correct answer.

    Explanation

    The summarize operator aggregates rows into groups defined by a by clause and computes aggregate functions such as count() for each group. Project and extend only shape or add columns without aggregating, and distinct returns unique combinations rather than counts.

  187. Question 187Perform threat hunting

    A hunter wants to see the first and last time each account signed in to a device during the past week. Which summarize pattern returns those timestamps per account and device?

    1. where Timestamp > ago(7d) | take 10
    2. summarize count() by AccountName, DeviceName
    3. summarize StartTime=min(Timestamp), EndTime=max(Timestamp) by AccountName, DeviceName Correct answer.
    4. project AccountName, DeviceName, Timestamp

    Explanation

    Aggregate functions min() and max() applied to the Timestamp column, grouped by account and device, return the earliest and latest sign-in for each pair. Counting rows only gives volume, and project or take do not condense the timeline into first and last values.

  188. Question 188Perform threat hunting

    Which KQL operator removes duplicate rows from a result set based on specified columns during a hunt?

    1. join
    2. mv-expand
    3. union
    4. distinct Correct answer.

    Explanation

    The distinct operator returns unique combinations of the specified columns, which is useful for de-duplicating entities discovered during a hunt. Union combines tables, join correlates rows on keys, and mv-expand expands arrays into separate rows.

  189. Question 189Perform threat hunting

    Which KQL operator should an analyst use to convert a string timestamp column into a typed datetime value before comparing it with ago()?

    1. tostring()
    2. totimespan()
    3. todatetime() Correct answer.
    4. toint()

    Explanation

    todatetime() parses a string into the datetime type so time comparisons and ago() filters work correctly. tostring() converts in the opposite direction, totimespan() produces durations, and toint() produces integers, none of which support datetime comparison.

  190. Question 190Perform threat hunting

    A hunter wants to examine the parent process of each suspicious child process in DeviceProcessEvents. Which column pair should the query project to reveal that lineage?

    1. RegistryKey and RegistryValueName
    2. FileSize and FolderPath
    3. InitiatingProcessFileName and FileName Correct answer.
    4. RemoteIP and RemotePort

    Explanation

    DeviceProcessEvents stores the launching process in InitiatingProcessFileName and the launched process in FileName, so projecting both columns exposes parent-child lineage. The other pairs describe network connections, registry activity, and file attributes, which do not describe process ancestry.

  191. Question 191Perform threat hunting

    An analyst suspects beaconing and wants to measure the regularity of connections to a remote endpoint. Which approach best supports that hypothesis in a hunting query?

    1. Project the remote IP and device name only
    2. Filter to connections where the port equals 443
    3. Count the total number of connections per remote IP over the whole month
    4. Bucket connection timestamps per remote IP and compute the variance of the intervals between them Correct answer.

    Explanation

    Beaconing is characterized by regular timing, so the intervals between successive connections must be derived and their spread measured; low variance across many connections suggests automation. Total volume, projected columns, or a port filter alone cannot establish regularity of timing.

  192. Question 192Perform threat hunting

    A hunter wants to find devices that ran a process whose command line contains a suspicious keyword, then later wrote a file in the startup folder. Which KQL construct correlates those two events on the same device?

    1. project DeviceId from each table separately
    2. union of the process query and the file query without keys
    3. summarize count() by FileName over both tables
    4. join kind=inner on DeviceId between the process query and the file query Correct answer.

    Explanation

    A join keyed on DeviceId (optionally with a time bound) links the process execution to the later file write on the same host, forming a correlated pattern. Union merely stacks rows, summarize cannot relate the two event types, and separate projections never combine them.

  193. Question 193Perform threat hunting

    Which KQL operator lets a hunter create time buckets so that events can be counted per hour during an investigation?

    1. extract()
    2. split()
    3. bin() Correct answer.
    4. parse_json()

    Explanation

    The bin() function rounds a datetime value into fixed-size buckets, which allows counting or aggregating events per hour or other interval. split() divides strings, extract() pulls regex matches from text, and parse_json() interprets JSON, none of which create time buckets.

  194. Question 194Perform threat hunting

    An analyst wants to surface rare process names by comparing each process's execution count against the total executions on a device. Which combination of operators produces that ratio?

    1. project DeviceId, FileName, Timestamp
    2. summarize count() by DeviceId, FileName, then extend with the device total and divide Correct answer.
    3. distinct DeviceId, FileName
    4. where FileName has_any (known malicious names)

    Explanation

    Grouping counts by device and process, then joining or extending the per-device total and dividing gives a rarity ratio that highlights infrequent processes. The other options either hard-code names, list raw rows, or de-duplicate without any frequency measurement.

  195. Question 195Perform threat hunting

    A hunter wants to check whether any device communicated with an IP address that appears in an uploaded threat intelligence indicator table. Which operator returns only matching rows?

    1. join kind=leftouter ThreatIntel on RemoteIP
    2. where RemoteIP in (ThreatIntel | project Indicator) Correct answer.
    3. where RemoteIP has_any (ThreatIntel)
    4. union ThreatIntel

    Explanation

    The in operator tests each row's value against a subquery or dynamic set and keeps only rows whose value appears in that set, which directly answers the match question. has_any matches terms within a single string, leftouter join keeps unmatched rows, and union only appends rows.

  196. Question 196Perform threat hunting

    An analyst wants to review which accounts were used to run processes on a set of compromised hosts during a two-hour window. Which query best answers that question?

    1. DeviceProcessEvents | project FileName
    2. DeviceProcessEvents | summarize count() by FileName
    3. DeviceProcessEvents | where DeviceName in~ (hosts) and Timestamp between (datetime(a) .. datetime(b)) | summarize by AccountName Correct answer.
    4. DeviceProcessEvents | where Timestamp > ago(30d) | take 100

    Explanation

    Filtering to the specific hosts and the bounded time window, then summarizing by AccountName, returns the distinct accounts that executed processes in that scope. The other queries either ignore the host and time scope, drop the account column, or aggregate by process name.

  197. Question 197Perform threat hunting

    A hunter wants to detect a process that was launched by an unusual parent, where unusual means the parent-child pair occurs on fewer than five devices in the environment. Which query pattern implements that rarity threshold?

    1. summarize Devices=dcount(DeviceId) by InitiatingProcessFileName, FileName | where Devices < 5 Correct answer.
    2. summarize count() by FileName | where count_ < 5
    3. distinct InitiatingProcessFileName, FileName
    4. where InitiatingProcessFileName == "explorer.exe"

    Explanation

    Counting distinct devices per parent-child pair and filtering to pairs below the threshold isolates combinations that are rare across the estate. Counting only by child name, hard-coding a parent, or de-duplicating pairs does not measure how many devices exhibit each pair.

  198. Question 198Perform threat hunting

    A hunter must identify devices where a user opened an email attachment and a child process of the mail client started shortly afterward. Which correlation key and ordering constraint are essential to that hunt?

    1. Same RemoteIP and the same port
    2. Same DeviceId and the process start time falling within a short window after the attachment event Correct answer.
    3. Same FileName only, regardless of device or time
    4. Same registry key name across all devices

    Explanation

    The hypothesis links two event types on one host within a short interval, so the correlation must key on device identity and enforce temporal ordering with a bounded window. Matching on file name alone, network endpoints, or registry key names cannot establish that the attachment opening preceded the process launch on the same device.

  199. Question 199Perform threat hunting

    An analyst wants to hunt for password spraying by finding source IPs that produced failed sign-ins for many distinct accounts with few attempts per account. Which aggregation expresses that pattern?

    1. distinct IPAddress, AccountName
    2. summarize Attempts=count() by AccountName | where Attempts > 100
    3. summarize Accounts=dcount(AccountName), Attempts=count() by IPAddress | where Accounts > 10 and Attempts/Accounts < 3 Correct answer.
    4. where ActionType == "LogonFailed"

    Explanation

    Spraying spreads a small number of attempts across many accounts from one source, so counting distinct accounts per source IP and keeping a low attempts-per-account ratio captures that shape. Counting per account finds brute force against one account, a bare filter returns everything, and distinct lists pairs without measuring breadth.

  200. Question 200Perform threat hunting

    During a hunt an analyst finds a device that resolved an unusual domain, and later the same device connected to an IP that had never appeared in the environment before. Which conclusion is best supported before further validation?

    1. The sequence is a lead consistent with command-and-control but requires corroboration such as payload or process evidence Correct answer.
    2. The IP address is benign because it was never seen before
    3. The device is confirmed compromised and should be reimaged immediately without further checks
    4. The events are unrelated because DNS and network telemetry cannot be correlated

    Explanation

    A novel domain followed by a first-seen IP is a plausible command-and-control pattern, but a hunt produces hypotheses that must be corroborated with process, file, or payload evidence before concluding compromise. Treating the lead as proof, dismissing correlation, or assuming novelty means benign all misstate the evidentiary standard.

SC-200 flashcards

33 cards. Read the term and the definition here. The deck at the top of this page is optional.

Sentinel Reader role
Azure RBAC role granting read-only access to Sentinel data, incidents, and workbooks in a workspace. It cannot create or edit analytics rules or change incident status.
Sentinel Responder role
Role that can view and manage incidents, including changing status, assigning owners, and adding comments. It cannot create or modify analytics rules or automation rules.
Sentinel Automation Contributor
Role scoped to a resource group that permits Sentinel automation rules and playbooks to run against the workspace. It is required for playbook identities to act on incidents.
Query frequency vs lookback
Query frequency is how often an analytics rule runs; lookback is how far back each run searches. Lookback must be at least the frequency to avoid unexamined gaps.
Alert grouping by entities
Analytics rule setting that bundles alerts sharing selected mapped entities into one incident. Reduces incident noise when one actor generates repeated alerts across the same host or account.
Entity mapping in analytics
Maps query output columns to entity types such as Account, Host, or IP. Enables entity pages, entity-based grouping, and the investigation graph.
Automation rule order
Numeric sequence determining execution order when multiple automation rules match one incident trigger. Lower numbers run first, and later rules see prior changes.
Playbook region requirement
A Sentinel playbook is a Logic App that must reside in the same Azure region as the workspace. Cross-region playbooks cannot be attached to automation rules.
Watchlist alias function
KQL function _GetWatchlist('alias') returns rows from an uploaded CSV watchlist. Used to enrich queries with VIP lists, asset inventories, or known-bad indicators.
Data Collection Rule
Azure resource defining which data sources the Azure Monitor Agent collects and where it sends them. Used to route security events into a Sentinel workspace.
Incident close classifications
Options when closing an incident: True Positive, False Positive, Benign, and Undetermined. True Positive and False Positive require a written close reason.
Incident task purpose
Checklist item attached to an incident to track response steps with Open, Completed, or Deleted status. Records analyst actions rather than triggering automation.
Device isolation modes
Full isolation blocks all network traffic except the Defender service. Selective isolation additionally permits Outlook and Teams communication while blocking other traffic.
Live response basic commands
Commands available in a standard live response session, including cd, dir, getfile, putfile, and run. Advanced commands like remediate require the advanced capability enabled.
Mark user compromised
Defender XDR response action flagging an identity as high risk. It triggers additional detections for that account and can inform conditional access risk policies.
Force password reset action
Identity response action requiring the user to change their password at next sign-in. Used when credential compromise is suspected during incident triage.
Action center approvals
Defender XDR queue where pending automated investigation actions await analyst approval or rejection. Approving executes the remediation on the affected entity.
Evidence remediation status
Each entity in an automated investigation carries a verdict of Remediated, Not remediated, or Pending action. Pending action items require analyst approval in the Action center.
Custom detection rule
Defender XDR rule built from an advanced hunting query. Runs on a schedule, generates alerts, and can take automatic response actions on matching entities.
Restrict app execution
Endpoint response action limiting execution to Microsoft-signed binaries only. Blocks malware while allowing the operating system and Defender components to run.
Incident alert correlation
Process where Defender XDR merges alerts sharing entities or attack story into a single incident. Analysts can also manually merge related incidents.
Investigation package collection
Endpoint action gathering logs, registry keys, and memory artifacts into a downloadable archive. Used for offline forensic analysis after a suspected compromise.
KQL where operator
Filters a table to rows matching a boolean expression. Typically the first operator after the table reference to reduce data before projection or aggregation.
KQL summarize operator
Groups rows by one or more columns and computes aggregates such as count, dcount, make_set, or arg_max. Produces one output row per group.
KQL arg_max function
Aggregate returning the row with the maximum value of a column within each group. arg_max(TimeGenerated, *) retrieves the most recent row per entity.
KQL leftanti join
Join flavor returning left-side rows with no match on the right. Common hunting pattern for finding hosts or users absent from an expected baseline.
KQL innerunique default
Default join kind that deduplicates the left side on the join key before matching. Can silently drop rows; use inner when every left row must be preserved.
Hunting bookmarks
Saved rows or result sets from a hunting query in Sentinel. Bookmarks can be promoted into a new incident or linked to an existing one.
Livestream query
Sentinel hunting rule that runs continuously and creates an alert when results appear. Used to convert a validated hunting query into ongoing detection.
Defender XDR table prefixes
Advanced hunting tables are named by source: Device* for endpoint, Email* for mail, Identity* for identity, CloudApp* for SaaS, and Alert* for alert records.
TAXII threat intelligence feed
Standard protocol for importing STIX indicators into Sentinel via the Threat Intelligence solution. Imported indicators can match logs through TI matching rules.
MSTICPy notebooks
Python library used in Jupyter notebooks for hunting, enrichment, and visualization. Connects to Log Analytics and threat intelligence providers for investigation workflows.
UEBA behavior profiles
Sentinel feature building baseline behavior for users and hosts from logs and watchlists. Deviations appear as anomalies in entity pages and can drive custom detections.

SC-200 study guide

Manage a Security Operations Environment

What to know

This domain tests your ability to configure Microsoft Sentinel as a working SOC platform rather than just a log sink. Core concepts: workspaces and the Log Analytics data model, data connectors and ingestion (including the difference between the Azure Monitor Agent / AMA and the legacy Log Analytics agent), the Sentinel data lake and analytics rules, watchlists, automation rules versus playbooks, and role-based access control both at the workspace and at the Sentinel resource level.

Traps to expect

  • RBAC confusion. Sentinel has its own roles (Sentinel Reader, Sentinel Responder, Sentinel Contributor) in addition to Azure RBAC. Questions often ask for the least privilege needed for a task - e.g., an analyst who only triages incidents needs Sentinel Responder, not Contributor.
  • Automation rules vs. playbooks. Automation rules run on the incident/alert trigger and can be created in the portal without Logic Apps; playbooks are Logic Apps and are needed for actions like calling an external API. Questions frequently describe a scenario where the "no-code" answer is the automation rule.
  • Retention and cost. Analytics/security logs and the data lake have different retention and pricing behavior; don't assume interactive retention equals total retention.
  • Connector vs. DCR. Data collection rules define what the agent collects; the connector defines the table mapping. Mixing these up is a classic distractor.

Worked example

A question asks how to ensure only the SOC tier-1 team can view incidents but not edit analytics rules. Rule of thumb: assign Microsoft Sentinel Reader at the workspace scope to the tier-1 group, and reserve Sentinel Contributor for engineers. If the scenario mentions "run a playbook automatically when a high-severity incident is created," the answer is an automation rule with a playbook action, not a scheduled query rule.

Rule of thumb

When a question asks "who can do X," pick the narrowest built-in role that includes X; when it asks "how does X happen automatically," decide first whether the trigger is an incident (automation rule) or a query (analytics rule).

Respond to Security Incidents

What to know

This domain covers the incident lifecycle in Microsoft Sentinel and Microsoft Defender XDR: triage, investigation, evidence gathering, and remediation. Key concepts: incident grouping and entities (accounts, hosts, IPs, URLs), the incident investigation graph, bookmarks and comments, the difference between alerts and incidents, incident tasks, and automated response via automation rules and playbooks. You should also understand Defender XDR's automated investigation and response (AIR), the action center, and how to run advanced hunting queries from an incident.

Traps to expect

  • Alert vs. incident. An incident can contain many alerts; closing an incident does not automatically close every underlying alert, and questions often test which object you act on.
  • Entity mapping. For playbooks to work, analytics rules must map entities correctly; a missing entity mapping is a common reason an automated action fails.
  • Status and classification. Sentinel incidents have status (New, Active, Closed) and, on close, a classification (True Positive, False Positive, Benign, etc.). Questions ask for the correct classification semantics - "Benign Positive" means expected activity that still triggered, not a false alarm.
  • Playbook permissions. Playbooks run under a service account or managed identity; missing permissions is the usual reason a playbook fails silently.

Worked example

An incident shows a suspicious sign-in from a new country, and the analyst wants to confirm whether the account also sent mail externally. Rule of thumb: open the incident, use the investigation graph to expand the account entity, pivot to related alerts, then run an advanced hunting query (e.g., against EmailEvents) scoped to that account. Record findings as incident comments/bookmarks before closing with classification True Positive and the appropriate threat category.

Rule of thumb

Triage order: confirm scope (entities) → gather evidence (graph, hunting, bookmarks) → contain (playbook/device isolation) → close with the right classification. Never close as False Positive without documenting why the alert fired.

Perform Threat Hunting

What to know

Threat hunting in SC-200 centers on KQL (Kusto Query Language) in Microsoft Sentinel and Defender XDR advanced hunting. You must know the hunting workflow: form a hypothesis, query telemetry, validate findings, and promote results into detections. Core concepts: the difference between scheduled analytics rules and custom detections (Defender XDR), hunting queries and livestream, bookmarks to capture results, and search jobs for long-term data. You should be fluent in KQL operators: where, project, summarize, join, union, extend, parse, mv-expand, ago(), bin(), and make_set.

Traps to expect

  • Table names differ between portals. Sentinel uses Log Analytics tables (e.g., SecurityEvent, SigninLogs); Defender XDR advanced hunting uses schema tables like DeviceProcessEvents and IdentityLogonEvents. Questions test which table belongs where.
  • summarize vs project. summarize aggregates; project selects columns. A common distractor swaps them.
  • Time filtering. Use where TimeGenerated > ago(24h) in Sentinel; advanced hunting uses Timestamp. Mixing these is a frequent error.
  • Promote vs. save. Saving a hunting query does not create an alert; you must create an analytics rule or custom detection to alert.

Worked example

Hypothesis: unusual PowerShell encoded commands. In Sentinel, query DeviceProcessEvents | where Timestamp > ago(7d) | where ProcessCommandLine has "-enc" | summarize count() by DeviceName, AccountName. Review outliers, bookmark the results, then promote the query into a scheduled analytics rule with entity mapping so it generates incidents. Rule of thumb: a hunt that finds nothing is still useful - document the hypothesis so future hunts don't repeat it.

Rule of thumb

Always filter on time first, aggregate with summarize to spot outliers, and remember: hunting queries are silent - only analytics rules and custom detections create alerts.

SC-200 cheat sheet

Quick reference

Manage a security operations environment

  • Microsoft Sentinel workspace roles: Sentinel Reader can view incidents and data; Sentinel Responder can also manage incidents; Sentinel Contributor can create and edit analytics rules, workbooks, and automation; Sentinel Automation Contributor lets playbooks run in the resource group.

  • Data connectors ingest via the Logs Ingestion API, Azure Monitor Agent (AMA) with Data Collection Rules, or service-to-service connectors; AMA replaces the legacy Log Analytics agent and supports Windows and Linux forwarders.

  • Analytics rule scheduling has three parts: query, query frequency (how often it runs), and lookback/period (how far back each run queries); the lookback must be greater than or equal to the query frequency to avoid gaps.

  • Alert grouping settings: group all alerts into a single incident, group alerts into multiple incidents by selected entities, or disable grouping; incident creation can be suppressed and alerts left ungrouped.

  • Entity mappings map query output columns to entity types (Account, Host, IP, URL, FileHash, Process, CloudApplication); mapped entities enable entity pages, entity-based grouping, and investigation graph.

  • Automation rules run on incident creation, update, or close triggers and can assign owners, change severity or status, add tags, or run a playbook; they run in the order set by their order number.

  • Playbooks are Azure Logic Apps in the same region as the Sentinel workspace; the Logic Apps connector authenticates as a service principal or managed identity with Sentinel Responder or Automation Contributor permissions.

  • Workbook and hunting query permissions follow the underlying Log Analytics workspace; data retention defaults to 30 days interactive for Analytics tier, with long-term retention available for search jobs and restore.

  • Watchlists upload CSV data into a _GetWatchlist() function usable in analytics and hunting queries; watchlist aliases are referenced in KQL as _GetWatchlist('alias').

Quick reference

Respond to security incidents

  • Incident lifecycle statuses: New, Active, and Closed; closing classification is True Positive, False Positive, Benign, or Undetermined, and only True Positive or False Positive require a close reason field.

  • Incident tasks are checklist items tracked under an incident; they support status Open, Completed, or Deleted and are used to record response steps rather than to trigger automation.

  • Investigation (automated investigation) uses the entities mapped in the triggering alert to build an evidence graph and can trigger actions such as isolating a device or marking a user compromised.

  • Microsoft Defender XDR incident correlation merges related alerts across Defender products into one incident; manual incident creation and alert merging are supported in the Defender portal.

  • Live response in Defender for Endpoint requires the Live response capability enabled and an appropriate role; basic commands include cd, dir, getfile, putfile, run, and the advanced commands remediate, persist, and undo.

  • Device response actions: isolate device (full or selective with Outlook and Teams exceptions), restrict app execution, run antivirus scan, collect investigation package, and initiate automated investigation.

  • User response actions in Defender for Identity and XDR: force password reset, mark user as compromised, disable user, and confirm user as compromised or safe to reset risk state.

  • Evidence and entity verdicts in automated investigation are Pending action, Remediated, or Not remediated; approvals for pending actions are granted per action in the Action center.

  • Advanced hunting in Defender XDR uses tables such as DeviceEvents, DeviceProcessEvents, AlertInfo, and IdentityLogonEvents; results can be used to create custom detection rules that generate alerts and incidents.

Quick reference

Perform threat hunting

  • KQL core operators: where filters rows, project selects columns, extend adds computed columns, summarize aggregates with by grouping, join merges tables, and union combines result sets.

  • Time filters use ago(), between, and the TimeGenerated column; a hunting query should bound the time range explicitly rather than relying on portal defaults for reproducibility.

  • summarize with make_set, make_list, dcount, arg_max, and arg_min builds entity profiles; arg_max(TimeGenerated, *) returns the latest row per group.

  • join kinds: innerunique (default, deduplicates left keys), inner, leftouter, rightouter, fullouter, leftanti, and leftsemi; leftanti returns left rows with no match and is the standard for finding missing coverage.

  • Sentinel hunting: run built-in or custom queries in the Hunting blade, bookmark interesting rows, and promote a bookmark to an incident or create a livestream query that alerts when results appear.

  • Microsoft Defender XDR advanced hunting schema prefixes: Device* for endpoint, Email* for email, Identity* for identity, CloudApp* for SaaS, and Alert* for alerts; each table has a documented retention window.

  • Anomaly and entity behavior analytics: Sentinel UEBA builds behavior profiles from watchlists and logs; anomalies surface in the Entities and UEBA tabs rather than as standalone alerts unless a rule references them.

  • Threat intelligence matching: the Threat Intelligence solution uploads STIX indicators via TAXII or the upload API, and matching analytics rules join TI indicators to log data by IP, domain, URL, or file hash.

  • Notebooks in Sentinel use Jupyter with the MSTICPy library; they run on a compute resource such as Azure Machine Learning and authenticate to the workspace through a configured mssparkutils or MSTICPy connection.

SC-200 key terms

Microsoft Sentinel

A cloud-native security information and event management service in Azure that collects logs, detects threats with analytics rules, and supports investigation and automated response.

Related: Log Analytics workspace, Analytics rule, Data connector
Log Analytics workspace

The Azure storage and query container that holds ingested security data, where Sentinel stores tables and runs Kusto queries against them.

Related: Microsoft Sentinel, KQL, Data connector
Data connector

A Sentinel configuration that pulls logs from a source such as Microsoft 365, Azure activity, or a third-party product into the workspace for analysis.

Related: Microsoft Sentinel, Log Analytics workspace, Ingestion
KQL (Kusto Query Language)

The read-only query language used to search, filter, summarize, and join tables in Log Analytics, forming the basis of detections and hunting queries.

Related: Log Analytics workspace, Hunting query, Analytics rule
Analytics rule

A scheduled or near-real-time Sentinel rule that runs a query on a schedule and raises an alert when results match defined conditions.

Related: Incident, Alert, Entity mapping
Alert

A single detection event produced when an analytics rule, custom detection, or built-in protection matches suspicious activity in collected data.

Related: Incident, Analytics rule
Incident

A grouped collection of related alerts and evidence in Microsoft Sentinel or Defender that represents one case an analyst investigates and resolves.

Related: Alert, Incident severity, Playbook
Incident severity

A classification such as High, Medium, Low, or Informational that indicates the potential impact of an incident and drives triage priority.

Related: Incident, Triage
Triage

The initial review of an alert or incident to decide whether it is a true positive, its urgency, and what response steps are required.

Related: Incident severity, True positive
True positive

A detection result that correctly identifies real malicious or policy-violating activity, as opposed to a false positive or benign anomaly.

Related: Triage, False positive
False positive

An alert raised on activity that is actually benign, often caused by overly broad logic, missing exclusions, or expected administrative behavior.

Related: True positive, Tuning
Tuning

The process of adjusting detection logic, thresholds, and exclusions so rules produce fewer false positives while still catching real threats.

Related: False positive, Analytics rule
Entity mapping

Configuration in an analytics rule that tells Sentinel which fields represent accounts, hosts, IP addresses, or URLs so they become linked entities in incidents.

Related: Analytics rule, Entity
Entity

A discrete object in an investigation, such as a user account, device, IP address, file hash, or mailbox, that can be linked and explored.

Related: Entity mapping, Investigation graph
Investigation graph

A visual map in Microsoft Sentinel or Defender that shows entities and their relationships to help analysts explore how an incident unfolded.

Related: Entity, Incident
Playbook

An Azure Logic Apps workflow triggered manually or automatically from an incident to perform response actions such as notifications, blocking, or ticket creation.

Related: Automation rule, Incident
Automation rule

A Sentinel rule that automatically responds to created incidents by assigning owners, changing severity, adding tags, or running playbooks.

Related: Playbook, Incident
Hunting query

A saved KQL query used proactively to search for suspicious patterns that no current analytics rule detects, often run before promoting results to a detection.

Related: KQL (Kusto Query Language), Bookmark
Bookmark

A saved record in Microsoft Sentinel that preserves query results or evidence so an analyst can revisit them or attach them to an incident.

Related: Hunting query, Incident
Microsoft Defender XDR

The integrated suite that correlates signals across endpoints, identities, email, and cloud apps and produces unified incidents and advanced hunting data.

Related: Advanced hunting, Incident
Advanced hunting

The KQL-based query interface in Microsoft Defender XDR that lets analysts search raw, near-real-time telemetry across the suite's workloads.

Related: Microsoft Defender XDR, KQL (Kusto Query Language)
Custom detection

A Defender XDR rule built from an advanced hunting query that runs on a schedule and generates alerts or incidents when results are found.

Related: Advanced hunting, Analytics rule
Attack disruption

Automatic containment capability in Microsoft Defender XDR that blocks observed attacker activity in progress, such as disabling a compromised account or containing a device.

Related: Microsoft Defender XDR, Automated investigation
Automated investigation

A Defender capability that examines alerts and entities, determines verdicts, and can apply remediation actions with or without analyst approval.

Related: Attack disruption, Playbook
MITRE ATT&CK

A public knowledge base of adversary tactics and techniques used to categorize detections, structure threat hunting, and assess coverage gaps.

Related: Hunting query, Analytics rule
Watchlist

A Sentinel table of reference data such as VIP users, IP ranges, or threat indicators that queries and analytics rules can join against.

Related: Threat intelligence, KQL (Kusto Query Language)
Threat intelligence indicator

An observable such as an IP address, domain, URL, or file hash with known malicious associations that can be imported and matched against logs.

Related: Watchlist, Data connector
Workbook

A customizable Sentinel dashboard built on Azure Monitor workbooks that visualizes query results, trends, and operational metrics.

Related: Log Analytics workspace, KQL (Kusto Query Language)
Role-based access control (RBAC)

The Azure and Sentinel permission model that assigns roles such as reader, responder, or contributor to control who can view or act on data.

Related: Microsoft Sentinel, Log Analytics workspace
Data retention

The configured period during which ingested security logs remain queryable in a workspace before archival or deletion, affecting investigation history.

Related: Log Analytics workspace, Ingestion
Ingestion

The process of collecting and loading log data from connected sources into the workspace, where cost and latency depend on volume and method.

Related: Data connector, Log Analytics workspace
Identity protection signal

Risk detections from Microsoft Entra ID Protection, such as anonymous IP use or leaked credentials, that feed alerts and incidents for identity threats.

Related: Incident, Entity
Attack surface reduction rule

A Defender for Endpoint control that blocks specific behaviors commonly used by malware, such as Office child processes or script-based execution.

Related: Microsoft Defender XDR, Custom detection
Live response

A Defender for Endpoint remote shell that lets analysts run commands, collect files, and investigate a device directly during an incident.

Related: Automated investigation, Incident
Indicator of compromise (IoC)

Artifact evidence of a security breach, such as a malicious hash, domain, or IP, used to detect and block known threats across defenses.

Related: Threat intelligence indicator, Watchlist
Indicator of attack (IoA)

Behavioral evidence that an intrusion is underway, such as unusual privilege escalation or lateral movement, focused on intent rather than static artifacts.

Related: Indicator of compromise (IoC), MITRE ATT&CK
Anomaly detection

Analytics that learn normal baseline behavior and flag statistically unusual activity, such as rare sign-ins or abnormal data volumes.

Related: Hunting query, Analytics rule

SC-200 study plan

8 weeks · About 6 hours per week

Week 1

Manage a security operations environment

  • Map every Microsoft Defender portal blade (incidents, alerts, hunting, advanced hunting, settings) to the SOC task it supports, writing a one-line purpose for each.

  • Configure role-based access control in Microsoft Defender XDR by assigning a custom role to a test user and verifying the resulting permissions.

  • Enable and tune at least three alert policies, documenting the severity and threshold you changed and why.

  • Sketch the data connectors feeding Microsoft Sentinel for a sample tenant and label which log sources are native versus via AMA or Codeless Connector Framework.

Your checkpoint

A one-page portal-and-permissions map covering at least 12 blades, 3 tuned alert policies, and the connector inventory, saved as a personal reference sheet.

Week 2

Manage a security operations environment

  • Configure Microsoft Sentinel onboarding for a test workspace, including enabling the Microsoft 365 and Azure Activity data connectors.

  • Build two analytics rules from scratch (one scheduled, one near-real-time) and validate each by generating a matching test event.

  • Create an automation rule that assigns an incident to a group and applies a tag, then confirm the behavior on a triggered incident.

  • Design a watchlist and upload a CSV so a KQL query can join against it.

Your checkpoint

A working Sentinel workspace with 2 validated analytics rules, 1 automation rule, and 1 populated watchlist, evidenced by screenshots or exported rule JSON.

Week 3

Respond to security incidents

  • Triage a simulated incident end to end: classify, assign, set status, and record evidence in incident comments.

  • Author a playbook in Logic Apps that enriches an incident with device risk and posts the result to a Teams channel.

  • Define an incident severity matrix that maps business impact and scope to P1-P4 and justify each tier.

  • Configure a manual attack disruption or containment action and document its preconditions and rollback path.

Your checkpoint

A documented incident response runbook with the severity matrix, a working enrichment playbook, and a completed triage walkthrough of one simulated incident.

Week 4

Respond to security incidents

  • Execute containment for a compromised identity: revoke sessions, reset password, and confirm sign-in risk returns to clean.

  • Isolate a test device through Defender for Endpoint live response and collect a forensic package.

  • Write a post-incident review template covering timeline, root cause, detection gaps, and follow-up actions.

  • Automate a phishing-submission workflow that extracts URLs and submits them for detonation.

Your checkpoint

A completed incident case file for a simulated identity-plus-device compromise, including containment steps taken, evidence collected, and a filled post-incident review.

Week 5

Perform threat hunting

  • Write ten advanced hunting queries in KQL spanning sign-in anomalies, process creation, and network connections.

  • Convert one hunting query into a custom detection rule and verify it fires on replayed data.

  • Use the hunting schema reference to identify which tables hold identity, endpoint, and email telemetry and note retention differences.

  • Correlate two data sources in a single query to surface a behavior neither source shows alone.

Your checkpoint

A personal hunting query library of 10 documented KQL queries, with at least one promoted to a custom detection and validated.

Week 6

Perform threat hunting

  • Hunt for a living-off-the-land technique using command-line telemetry and document the hypothesis, query, and findings.

  • Build a Sentinel workbook that visualizes hunting results over time.

  • Perform threat intelligence matching by importing an indicator feed and writing a query that joins it to sign-in or process events.

  • Create a scheduled hunting routine with defined hypotheses and a triage path for positive hits.

Your checkpoint

A threat hunt report for one hypothesis, including the KQL used, the workbook visualization, and a documented decision on whether to promote the detection.

Week 7

Manage a security operations environment & Respond to security incidents

  • Re-run a full mock incident from alert to closure under a 45-minute timer to test speed and completeness.

  • Audit your Sentinel and Defender configuration against least-privilege principles and fix at least two gaps.

  • Review every analytics rule you built for false-positive rate using historical data and tune thresholds.

  • Practice explaining an incident timeline aloud as if briefing a stakeholder.

Your checkpoint

A timed mock-incident scorecard plus a remediation log listing at least two configuration fixes and the tuning changes made.

Week 8

Respond to security incidents & Perform threat hunting

  • Complete a full-length timed practice assessment and log every missed objective by domain.

  • Re-study the two weakest objectives until you can explain them without notes.

  • Rehearse the end-to-end flow from hunt hypothesis to incident closure in a single continuous exercise.

  • Finalize a one-page quick-reference card of KQL patterns, portal paths, and severity rules for exam-day recall.

Your checkpoint

A practice-assessment score report with a written remediation plan for each missed objective and a finished one-page quick-reference card.

Milestones

Week 2: Can independently onboard a Sentinel workspace, connect two data sources, and get a custom analytics rule to fire without referring to documentation.

Week 4: Can contain a compromised identity and isolate a device, then produce a post-incident review that names root cause and at least one detection gap.

Week 6: Can state a hunting hypothesis, write the KQL to test it, and decide whether to promote the result to a detection, all within one sitting.

Week 8: Scores at or above 80 percent on a full-length timed practice assessment with no domain below 70 percent.

SC-200 exam day

Your checklist

Government-issued photo ID

Bring the exact ID required by the testing provider (typically a valid passport or government photo ID). Confirm the accepted forms and name-match rules with the provider before test day; if your ID name differs from your registration name, resolve it in advance.

Appointment confirmation and test-taker ID

Have your registration confirmation and any test-taker ID or candidate number available. Save a screenshot or printout in case email access is unavailable at the test center.

Know your test delivery format and platform

Confirm whether you are taking the exam at a test center or via online proctoring, and which platform hosts it. Review that platform's system requirements and check-in steps in advance.

Run the online-proctoring system check (if applicable)

If testing remotely, install any required secure browser or proctoring software and complete the equipment check ahead of time. Confirm webcam, microphone, and internet stability meet the provider's requirements.

Arrive or check in early

Plan to arrive at the test center or begin online check-in well before your appointment time. Allow extra time for security screening, ID verification, and workstation setup. Confirm the exact arrival window with the provider.

Review the exam's domain weighting and format

Re-read the official skills outline for SC-200 and note the approximate weight of each domain so you can allocate study time and flag weak areas. Do not rely on memorized brain dumps; use the published outline only.

Prepare a one-page summary of key concepts

Condense high-value material: Microsoft Sentinel analytics rules, automation rules and playbooks, incident and investigation workflows, KQL query patterns, Microsoft Defender XDR components, and connector/ingestion concepts. Use this for final review, not as a crutch during the exam.

Practice hands-on tasks in a lab or sandbox

If you have access to a Microsoft 365 or Azure sandbox, rehearse common tasks: writing KQL queries, creating analytics rules, configuring automation, and triaging incidents. Confirm sandbox availability and permissions with your organization or provider.

Know the exam's question types and navigation

Review the provider's tutorial on question formats (multiple choice, case studies, drag-and-drop, or lab-style items, as applicable). Confirm whether you can flag and review questions before submitting.

Plan breaks and timing strategy

Decide in advance how you will pace yourself across the exam. Confirm with the provider whether scheduled or unscheduled breaks are allowed and how they affect your time; policies vary by delivery format.

Quiet, distraction-free environment (online testing)

For remote proctoring, clear your desk of unauthorized materials and ensure a private room with a closed door. Confirm the provider's rules on permitted items, room scans, and interruptions.

Backup plan for technical failure

Know the provider's support contact and procedure if your connection or platform fails. Have a phone available (if permitted) and note that proctoring rules may restrict phone use during the exam; confirm allowed exceptions with the provider.

Plan the day

Final 72 hours

Shift from new material to consolidation. Re-read the official SC-200 skills outline and map each domain to your confidence level. Do focused review of weak areas: KQL query construction, Microsoft Sentinel analytics and automation, incident investigation, and Microsoft Defender XDR workloads. Complete one or two timed practice sets under exam-like conditions if available, then review every wrong answer to understand the underlying concept. Avoid cramming new topics you have not studied; instead, reinforce what you already know.

Final 24 hours

Do a light review only: skim your one-page summary, key KQL operators, and common configuration steps. Confirm logistics: appointment time, location or online check-in link, ID requirements, and platform system check. Prepare your testing environment if remote. Get a full night's sleep and avoid last-minute schedule changes. Stop studying early enough to rest.

Morning of the exam

Eat a normal meal and hydrate. Re-check your ID, confirmation, and any permitted materials. Arrive at the test center or begin online check-in with buffer time. Do a brief, calm review of your summary sheet rather than deep-diving into new problems. Keep the pre-exam routine simple and avoid stressful conversations or rushed travel.

During the test

Read each question carefully and watch for qualifiers such as 'best', 'first', or 'least privilege'. For scenario or case-study items, identify the core requirement before evaluating options. Use the flag-and-review feature to mark uncertain questions and return to them if time allows. Manage your pace: note the number of questions and remaining time, and avoid spending too long on any single item. If a technical issue occurs, stay calm and follow the provider's support procedure; confirm the exact process with the proctor or provider.

After the test

If your score is reported at the end of the exam, note it and any domain-level feedback. If results are delayed, confirm with the provider when and how they will be delivered. Regardless of outcome, record which topics felt difficult so you can plan next steps.

Rules to check

  • Bring valid, unexpired government-issued photo ID that exactly matches your registration name. Confirm accepted ID forms and name-change procedures with the testing provider before your appointment.

  • Follow all proctor instructions and testing-center or remote-proctoring rules. Unauthorized materials, notes, devices, or communication during the exam can lead to score cancellation; confirm the permitted-items list with the provider.

  • Do not share, reproduce, or discuss actual exam content. Most providers require you to accept a non-disclosure agreement; violating it can result in score invalidation or other sanctions.

  • Understand the break policy before test day. Whether breaks are allowed, whether they are timed, and how they affect your remaining time varies by delivery format; confirm with the provider.

  • Know how scoring works: SC-200 uses a scaled score with a passing threshold set by the provider. Confirm the current passing score and score-report timing on the official certification page rather than relying on secondhand sources.

  • If you need to reschedule or cancel, follow the provider's policy and deadlines. Fees and windows vary; confirm the exact terms with the provider.

  • For online proctoring, test in a private, quiet room with a stable connection and a clear desk. Room scans and environment rules are enforced; confirm the specific requirements with the provider.

  • Report any technical problems or rule ambiguities to the proctor immediately. Do not attempt to resolve suspected platform issues on your own in ways that could be interpreted as unauthorized behavior.

SC-200 FAQ

How many SC-200 practice questions are available?

The practice set has 200 SC-200 questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many SC-200 flashcards are available?

The flashcard set has 33 SC-200 cards. Each card shows the term and its definition.

Which topics does the SC-200 study material cover?

The SC-200 study material covers Manage a Security Operations Environment, Respond to Security Incidents, and Perform Threat Hunting.

What format facts does the catalog list for the SC-200 exam?

The catalog lists a duration of 100 minutes and these item types: multiple choice and interactive components for the SC-200 exam.