SC-200 domain - 41% of the exam

Manage a Security Operations Environment

Manage a Security Operations Environment is 41% of the SC-200 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

121
Practice questions
8
Objectives
90
Medium
31
Hard

Where people go wrong

  • Confusing Sentinel analytics rule types

    The wrong answers swap Microsoft Sentinel analytics rule types that sound alike. A Microsoft security rule turns a connected product's alerts into incidents with no query, so it cannot match imported indicators or run custom logic. A threat intelligence rule matches indicators against ingested logs. Fusion uses machine learning to correlate multistage attacks, and the team cannot author it. A near-real-time rule runs the team's own query once per minute; a scheduled rule runs on a timer.

    See it in a sample question
  • Misreading device group automation levels

    The wrong answers choose an automation level that gates the wrong set of actions. Full remediates immediately with no approval step. Semi - require approval for any remediation queues every action until an analyst approves it. The core-folders variant of semi auto-approves actions outside core operating-system locations, so only some actions wait. No automated response applies and queues nothing. Each requirement turns on whether remediation is applied at once, held for approval, or never taken.

    See it in a sample question
  • Swapping the data collection rule and endpoint

    The wrong answers swap two Azure Monitor resources. A data collection rule defines what the Azure Monitor Agent collects: the Syslog facilities and severities, or the Windows event tier of All, Common or Minimal, and it is associated with the target machines. A data collection endpoint only provides the regional ingestion URL the agent connects to. Using the endpoint to filter facilities, or the rule as the ingestion URL, reverses their roles.

    See it in a sample question
  • Treating table plans as interchangeable

    The wrong answers treat Sentinel table plans as the same cost lever. The Analytics plan carries the highest ingestion cost and supports scheduled analytics rules and frequent interactive queries. Basic cuts ingestion cost for verbose, occasionally queried data while keeping interactive KQL. Auxiliary is the cheapest, built for high-volume data held long and searched rarely through search jobs and summary rules. Archive is a retention state, not a plan, and needs a search job or restore before it can be queried.

    See it in a sample question
  • Picking the wrong built-in Sentinel role

    The wrong answers pick a Sentinel role one step too wide or too narrow. Reader is read-only. Responder adds incident management, including status, owners and running playbooks, but no rule authoring. Contributor adds authoring of analytics rules and workbooks, which exceeds a triage or audit need. Playbook Operator runs playbooks but gives no incident management, and attaching a playbook to a rule also needs Logic App Contributor on the resource group.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleManage a Security Operations Environmenthard

A security operations team in Microsoft Sentinel must alert on a specific privileged sign-in pattern with the lowest possible detection latency, evaluating events almost as soon as they arrive in the workspace rather than waiting for the next scheduled run. The detection logic queries a single table and needs no enrichment from other tables. Which analytics rule type meets this requirement?

  • AA scheduled analytics rule configured with the shortest supported query interval and lookback period
  • BA Microsoft security analytics rule that creates incidents from connected Defender product alerts
  • CA near-real-time (NRT) analytics rule that runs once per minute against incoming events Correct
  • DA Fusion rule that correlates multistage activity into a single high-fidelity incident
Recognise that near-real-time analytics rules deliver the lowest detection latency for single-table Microsoft Sentinel detections that need no cross-table enrichment. Near-real-time rules are purpose-built to evaluate events about once a minute as they arrive, minimising the gap between ingestion and detection. Scheduled rules always wait for their next timer-driven run, so they cannot match NRT latency for a single-table pattern.

Why A is wrong: A scheduled rule runs on a fixed timer, so even the shortest interval still introduces minutes of delay and cannot match the near-real-time evaluation the requirement demands.

Why B is wrong: A Microsoft security rule only forwards alerts already raised by Defender connectors into incidents; it does not run custom Kusto Query Language detection logic against a table.

Why C is correct: An NRT rule evaluates events roughly every minute as they ingest, giving the lowest detection latency for a single-table query that needs no cross-table enrichment.

Why D is wrong: Fusion uses machine learning to stitch multistage attacks across many signals; it is not a low-latency single-pattern detector and its logic cannot be authored by the team.

Free sampleManage a Security Operations Environmenthard

An organisation runs automated investigation and response (AIR) in Microsoft Defender for Endpoint. For a device group containing servers that host a sensitive line-of-business application, the security team wants AIR to investigate alerts and queue every recommended remediation, but each remediation must wait for an analyst to approve it before it is applied. Which automation level should the team set on that device group?

  • AFull - remediate threats automatically, so that AIR investigates each alert on the servers and applies all of its recommended remediation actions without waiting for any analyst approval.
  • BNo automated response, so that AIR does not run on the device group at all and analysts manually investigate every alert and decide on remediation for the sensitive servers themselves.
  • CSemi - require approval for core folders remediation, so that actions in operating-system core folders need approval while remediations elsewhere on the servers are applied automatically by AIR.
  • DSemi - require approval for any remediation, so that AIR investigates and queues all of its recommended actions on the servers and holds each one in the pending-actions queue until an analyst approves it. Correct
Use the semi-require-approval-for-any-remediation automation level so AIR investigates and queues actions but applies none until an analyst approves each. Automated investigation and response automation is configured per device group. The automation level controls whether AIR applies its recommended remediations automatically, holds some for approval, or holds all of them. The semi level that requires approval for any remediation lets the investigation run end to end while parking every proposed action in the pending actions queue, so a human approves each one before it touches the sensitive servers. Full applies everything automatically and No automated response stops AIR running at all.

Why A is wrong: Full automation applies remediation actions automatically with no approval step, which is the opposite of the requirement that every action wait for an analyst, so it would act on the sensitive servers without the sign-off the team wants.

Why B is wrong: Setting no automated response stops AIR from investigating, but the team still wants the automated investigation to run and to queue the recommended actions; this level removes the investigation entirely rather than holding actions for approval.

Why C is wrong: This semi-automation variant only gates remediations that target core operating-system folders and auto-applies the rest, so actions outside those folders would still run without approval, failing the requirement that every remediation be approved first.

Why D is correct: This level runs the full automated investigation and proposes remediations but applies none of them until an analyst approves each from the pending actions queue, which matches the need to investigate yet gate every action on the sensitive servers.

Free sampleManage a Security Operations Environmentmedium

You have deployed the Azure Monitor Agent to a group of Linux web servers to collect Syslog into Microsoft Sentinel. The application owners now insist that only authentication-related facilities be ingested to control cost, while the existing kernel and cron facilities must stop flowing. You must change what is collected without reinstalling the agent. Which component should you modify to adjust which Syslog facilities the agent forwards?

  • AThe data collection endpoint bound to the workspace, narrowing its ingestion scope so only the authentication facilities are accepted from the Linux web servers.
  • BThe data collection rule associated with the agent, editing its Syslog facilities and severities so only the authentication facilities are forwarded into the workspace. Correct
  • CThe Syslog via AMA connector page itself, toggling the connector off and on so the refreshed connector definition forwards only the authentication facilities.
  • DThe local rsyslog configuration on each web server, rewriting its rules so the daemon stops emitting the kernel and cron facilities to the agent.
Edit the data collection rule, not the endpoint or connector toggle, to control which Syslog facilities and severities the Azure Monitor Agent forwards. A data collection rule is the authoritative definition of what the Azure Monitor Agent gathers. For Syslog it lists the facilities and the minimum severity per facility. Updating the rule reconfigures the running agent through its association, so collection changes take effect without reinstalling the agent, which is why the rule is the correct surface to edit.

Why A is wrong: A data collection endpoint provides the regional ingestion URL the agent connects to and does not contain any facility or severity filter, so changing it cannot restrict which Syslog facilities are collected.

Why B is correct: The data collection rule defines which Syslog facilities and minimum severities the Azure Monitor Agent collects, so editing the rule changes the collected facilities immediately without touching the agent installation.

Why C is wrong: Toggling the connector does not store any per-facility selection; the connector only enables the integration, and the actual facility and severity filtering lives in the data collection rule it creates.

Why D is wrong: Editing rsyslog on each host could reduce local logging, but it is a per-server change outside Microsoft Sentinel and is not the workspace-side control that governs what the Azure Monitor Agent ingests through its data collection rule.

Free sampleManage a Security Operations Environmentmedium

You ingest a high-volume, verbose firewall log into a custom table in Microsoft Sentinel. The records are needed only for occasional troubleshooting and bulk export, are never used in scheduled analytics rules, and must be stored as cheaply as possible. The table is currently on the Analytics plan. Which table plan change best fits this usage while keeping the data queryable?

  • AMove the table to the Archive tier immediately so the verbose records are retained at the lowest cost and remain available for occasional troubleshooting queries.
  • BKeep the table on the Analytics plan but shorten its interactive retention to the minimum so the lower retention period reduces the per-gigabyte ingestion charge.
  • CCreate a summary rule that aggregates the firewall log into a smaller summarised table and delete the verbose source records as soon as the aggregation runs.
  • DSwitch the table to the Basic logs plan, which lowers ingestion cost for high-volume troubleshooting data while still allowing interactive queries against the table. Correct
Choose the Basic logs table plan for high-volume, occasionally queried troubleshooting data to cut ingestion cost while keeping records interactively queryable. Microsoft Sentinel and Log Analytics offer per-table plans. The Basic logs plan targets verbose, high-volume data that is searched only occasionally and not used in scheduled analytics, charging a lower ingestion rate while still permitting interactive queries, which fits a firewall log used only for troubleshooting and export rather than archiving it out of reach.

Why A is wrong: Archived data is retained cheaply but is not interactively queryable; reaching it requires a search job or restore, so it does not keep the records directly queryable for the ad hoc troubleshooting the scenario calls for.

Why B is wrong: Shortening retention reduces how long data is kept but does not lower the Analytics-plan ingestion price per gigabyte, so a verbose firewall log would still be charged at the more expensive analytics rate.

Why C is wrong: A summary rule produces useful aggregates, but discarding the verbose source records removes the detailed lines that troubleshooting and bulk export depend on, so it does not satisfy the need to keep the raw data queryable.

Why D is correct: The Basic logs plan is designed for high-volume, verbose data that is queried occasionally; it cuts ingestion cost and still supports interactive queries against the single table, matching troubleshooting and bulk-export usage that never feeds scheduled rules.

Free sampleManage a Security Operations Environmentmedium

An engineer must let an automation specialist attach and detach playbooks from Microsoft Sentinel automation rules and analytics rules, so that Sentinel can trigger those Logic Apps as part of incident automation. The specialist already holds Microsoft Sentinel Responder on the workspace, yet attaching a playbook to a rule keeps failing with a permissions error on the Logic App. Which additional role should you grant to resolve this while keeping privilege scoped?

  • AMicrosoft Sentinel Contributor on the workspace, because elevating the specialist to Contributor includes every Sentinel permission and therefore clears the playbook attachment error.
  • BLogic App Contributor on the resource group containing the playbooks, because Sentinel needs that level of Logic App rights to attach and trigger the playbooks from the rules. Correct
  • CMicrosoft Sentinel Playbook Operator on the workspace, because that role is specifically designed to grant the ability to attach playbooks to automation and analytics rules.
  • DOwner on the subscription, because granting subscription Owner guarantees the specialist has every permission needed across Sentinel and the Logic Apps at once.
Granting Logic App Contributor on the playbooks' resource group lets a user attach and run Sentinel playbooks without over-privileging the workspace or subscription. Microsoft Sentinel playbooks are Azure Logic Apps, so the permission to attach a playbook to an automation or analytics rule and to run it lives in Azure role-based access control on the Logic App, not in the Sentinel roles. A Responder can manage incidents but lacks Logic App rights, which is why attachment fails. Granting Logic App Contributor scoped to the resource group that holds the playbooks supplies exactly those rights while keeping the grant narrow, unlike workspace Contributor, Playbook Operator alone, or subscription Owner.

Why A is wrong: Contributor would let the specialist edit Sentinel content but it does not by itself grant the Logic App permissions needed to run a playbook, and it over-grants rule authoring beyond the stated task, so it neither cleanly fixes the error nor respects least privilege.

Why B is correct: Attaching a playbook to a Sentinel rule requires permissions on the underlying Logic App, and Logic App Contributor on the resource group holding the playbooks gives the specialist the rights to manage and run them, resolving the permissions error with scope limited to those resources.

Why C is wrong: Playbook Operator lets a user run playbooks on demand, but managing and attaching them to rules depends on Logic App permissions, so adding only Playbook Operator does not clear an attachment failure caused by missing Logic App rights.

Why D is wrong: Subscription Owner would technically work but it grossly over-grants access across all resources in the subscription, violating least privilege when a resource-group-scoped Logic App role is sufficient for the task.

Other domains in this exam

See also the SC-200 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.