SC-200 exam at a glance
Microsoft Certified: Security Operations Analyst Associate · Intermediate level
Status: Active. The current skills measured took effect July 28, 2026. Microsoft will update the English-language exam on October 21, 2026.
| Exam code | SC-200 |
|---|---|
| Certification | Microsoft Certified: Security Operations Analyst Associate |
| Level | Intermediate |
| Duration | 100 minutes |
| Passing score | 700 or greater |
| Delivery | Proctored; scheduled through Pearson VUE |
| Exam cost | Price is based on the country or region in which the exam is proctored |
| Languages | English, Japanese, Chinese (Simplified), Korean, French, German, Spanish, Portuguese (Brazil), Chinese (Traditional), Italian |
| Certification validity | 1 year; renewable at no cost by passing the online renewal assessment before expiration |
| Retake policy | After the first failed attempt, wait 24 hours. A 14-day waiting period applies between subsequent attempts, up to five attempts within 12 months from the first attempt. Retakes require payment when applicable. |
This certification is intended for security operations analysts who reduce organizational risk by performing triage, responding to incidents, hunting for threats, and engineering detections across multi-cloud and on-premises environments. Candidates should 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.
Skills measured and their weighting
| Skill area | Weight |
|---|---|
| Manage a security operations environment | 40–45% |
| Respond to security incidents | 35–40% |
| Perform threat hunting | 20–25% |
Source: learn.microsoft.com — official SC-200 certification and exam page. Figures were checked against Microsoft’s official SC-200 study guide and credential policies. Confirm current details there before booking.
The full bank covers every domain, with timed mode and per-domain scoring.
SC-200 Practice Questions By Domains
3 domains covered1. Manage a security operations environment
23 free questions available
2. Respond to security incidents
5 free questions available
3. Perform threat hunting
2 free questions available
Practice the full exam, not a sample
Unlock the full bank and practise every domain end to end.
Unlock all 293 questionsMicrosoft SC-200 Practice Test
The Microsoft SC-200 practice test helps candidates check whether they can investigate, respond to, and hunt for security threats across Microsoft environments. It is most valuable when it tests practical reasoning rather than simple product definitions. You can View the full mock-exam library while creating a study plan that combines official Microsoft Learn material, hands-on practice, and regular knowledge checks. This guide explains the official SC-200 domains in clear language and shows how to use practice questions to find weak areas before the certification assessment.
SC-200 is aligned with the work of a Microsoft Security Operations Analyst. This role monitors threats, performs triage, investigates incidents, supports remediation, builds detections, and hunts for suspicious activity. The role can involve Microsoft Defender XDR, Microsoft Sentinel, Microsoft Entra ID, Microsoft Purview, and Microsoft Defender for Cloud workload protections. Kusto Query Language, usually called KQL, is also important because analysts use it to search and investigate security data.
What Does the Microsoft SC-200 Assessment Measure?
SC-200 measures whether a candidate can work through common security-operations tasks in Microsoft environments. The focus is broader than one portal or product. A realistic incident may begin with an identity alert, include activity on an endpoint, appear as a correlated incident in Defender XDR, and require further investigation in Microsoft Sentinel.
Microsoft describes the target candidate as someone who reduces organizational risk by triaging findings, responding to incidents, hunting for threats, and engineering detections. The analyst monitors multi-cloud and on-premises environments and works with other security and business roles to improve the organization’s security posture.
For practice purposes, your knowledge should work at three levels:
- Identify: Recognize the correct Microsoft security tool, data source, table, rule, or response action.
- Apply: Choose an appropriate configuration or investigation step for a scenario.
- Troubleshoot: Determine why data, detection, automation, or response did not behave as expected.
Microsoft updates role-based exams as technologies and job requirements change. The English SC-200 blueprint includes an update effective October 21, 2026. Candidates testing before or after an update should compare their appointment date with the official Microsoft SC-200 study guide. The main domain names and published weighting ranges remain the clearest way to organize preparation.
Official SC-200 Domains and Weightings
The Microsoft Learn study guide organizes the current published skills into three domains.
The percentages show relative emphasis, not a reason to ignore a smaller domain. Threat hunting supports investigation and detection engineering, while data ingestion and platform configuration affect everything an analyst can see. Study the domains separately first, then practise scenarios that connect them.
Domain 1: Manage a Security Operations Environment (40–45%)
This is the largest domain. It covers the environment analysts depend on: notifications, endpoint security configuration, automation, Microsoft Sentinel, data connectors, and detection rules.
Configure automation for Microsoft Defender XDR and Microsoft Sentinel
Automation helps a security team handle common tasks consistently and quickly. Learn how Defender XDR notifications, automated investigation and response, automatic attack disruption, Microsoft Sentinel automation rules, and Sentinel playbooks serve different purposes.
Start with the workflow rather than memorizing product screens:
- A security signal or alert is created.
- A rule evaluates the signal or incident.
- An automated process starts.
- Investigation or response actions occur.
- The analyst reviews the result and any remaining risk.
Microsoft Sentinel automation rules can change incident properties, assign owners, add tags, close incidents under defined conditions, or run playbooks. Playbooks are based on Azure Logic Apps and can perform multi-step workflows. In practice questions, identify whether the requirement is simple incident management or a broader workflow involving external actions.
Defender XDR automated investigation and response can collect evidence, examine affected entities, and recommend or perform remediation actions according to configuration. Automatic attack disruption is designed to contain active attacks by using correlated signals. Do not assume these features are identical. Look at the outcome requested in the scenario.
The published outline also includes email and alert notifications, alert tuning, suppression, correlation, device groups, permissions, and automation levels. These controls affect who sees information and how much automated action the platform can take.
Configure Microsoft Defender for Endpoint
Candidates should understand Defender for Endpoint advanced features, rule settings, custom data collection, and security policies such as attack surface reduction rules. Focus on the reason for each configuration.
Attack surface reduction rules help block or limit behaviors that attackers commonly abuse. Device groups support organization and role-based access. Automation levels control how investigation and remediation operate for grouped devices. Custom data collection can support a particular investigation or monitoring need.
A practice scenario may describe devices with different business sensitivity. Ask whether those devices need separate grouping, permissions, policy, or automation behavior. The best answer should meet the requirement while following least-privilege and controlled-response principles.
Configure the Microsoft Sentinel SIEM and platform
Microsoft Sentinel provides SIEM capabilities for collecting, analyzing, detecting, investigating, and responding to security information. Study Sentinel roles and the principle of assigning only the access required for a person’s responsibilities.
The updated blueprint also includes data retention across Microsoft Sentinel and XDR-related storage tiers, workbooks, and platform optimization. Learn why retention requirements differ. Frequently queried security data, long-term investigation data, and lower-cost archived information may not need the same treatment.
Workbooks provide interactive visualizations. They are useful for monitoring and analysis, but they do not replace analytics rules or incidents. When a question asks for a visual operational view, consider a workbook. When it asks to generate a security detection, consider an analytics or custom detection rule.
SOC optimization recommendations help teams identify opportunities to improve coverage, efficiency, and value. Study the purpose of recommendations rather than treating them as automatic proof that every suggested change is suitable.
Ingest data into Microsoft Sentinel
An analyst cannot investigate data that was never collected. Data ingestion is therefore a central SC-200 skill. Learn to select connectors according to the source and operational requirement.
The Microsoft outline includes:
- Windows Security Events through Azure Monitor Agent
- Data collection rules
- Windows Event Forwarding
- Syslog through Azure Monitor Agent
- Common Event Format through Azure Monitor Agent
- Azure activity logs
- Azure Policy and diagnostic settings
- Threat indicators
- Custom log tables
For Windows security events, understand the relationship among devices, the Azure Monitor Agent, data collection rules, and the destination. Windows Event Forwarding can help centralize events before collection. For Linux and network-security sources, Syslog or CEF may be appropriate depending on the format and integration.
Practice questions often include more than one technically possible connector. Choose based on the data source, supported method, required fields, and management approach. Also think about cost and noise. Collecting everything without a purpose can make analysis harder.
Configure detections
Detection engineering converts data into actionable security findings. The SC-200 outline includes custom detection rules in Defender XDR and several Microsoft Sentinel analytics-rule types, including scheduled, near-real-time, threat-intelligence, and machine-learning rules.
Use these simple distinctions:
- A scheduled rule runs a query at defined intervals.
- A near-real-time rule is intended for faster detection with a shorter delay.
- A threat-intelligence rule uses indicators to identify relevant activity.
- A machine-learning rule applies Microsoft-provided analytical logic.
- A custom detection in Defender XDR can turn an Advanced Hunting query into ongoing detection logic.
Learn how query results map to alerts and entities. A query that returns rows is not automatically a useful detection. It must identify meaningful activity and provide enough context for investigation.
The MITRE ATT&CK matrix helps analysts assess attack-technique coverage. Microsoft also lists configuring anomalies in Sentinel. In scenario questions, determine whether the requirement is to detect a specific known pattern, improve broad coverage, or find unusual behavior.
Domain 2: Respond to Security Incidents (35–40%)
This domain tests the analyst’s ability to move from an alert to a supported conclusion and an appropriate response. It spans several Microsoft security services because real attacks can cross identities, endpoints, email, applications, cloud workloads, and data.
Investigate incidents in Microsoft Defender XDR
Defender XDR correlates signals across supported Microsoft security products. Correlation can reduce separate alerts into a connected incident, helping analysts understand the possible attack story.
When approaching an incident, use a repeatable process:
- Review incident severity, status, alerts, and affected entities.
- Study the timeline and attack story.
- Check users, devices, mailboxes, applications, and other connected evidence.
- Determine whether the activity is malicious, benign, or still uncertain.
- Contain affected assets when necessary.
- Remediate the cause, not only the visible alert.
- Document the decision and verify that the threat no longer remains.
Practice questions may present many facts. Identify the affected entity and earliest confirmed malicious activity before choosing an action.
Respond across Microsoft security products
The official outline includes investigation and remediation involving several services:
- Microsoft Defender for Office 365: Email, collaboration threats, malicious messages, links, attachments, campaigns, and related entities.
- Microsoft Purview: Compromised entities and risks connected to data, audit, and compliance-related signals.
- Microsoft Defender for Cloud: Alerts involving Azure, hybrid, and multi-cloud workloads.
- Microsoft Defender for Cloud Apps: Application activity, risky cloud use, sessions, users, and connected applications.
- Microsoft Entra ID: Risky users, risky sign-ins, and compromised identity indicators.
- Microsoft Defender for Identity: Identity-related alerts and suspicious activity involving on-premises identity infrastructure.
- Microsoft Sentinel: Incidents created from collected and analyzed data across connected sources.
Do not learn these products as isolated lists. Create a map of the entities each service observes. When a question mentions a risky sign-in, mailbox message, endpoint process, cloud resource, or application session, use the entity to narrow the correct investigation tool.
Investigate complex and multi-stage attacks
The current outline specifically includes multi-stage, multi-domain, and lateral-movement attacks. These scenarios test whether you can connect evidence instead of treating each alert separately.
Build a timeline. Start with the initial access, then follow identity use, endpoint activity, privilege changes, remote connections, persistence, data access, and any attempted impact. Ask which event is a cause, which is a consequence, and which may be unrelated noise.
Entity relationships matter. A compromised account can authenticate to a device, start activity on another system, access a cloud application, and trigger data alerts. The incident view and hunting tools help analysts understand that chain.
Use agentic AI and embedded Microsoft Security Copilot
Microsoft’s published update includes investigating incidents with agentic AI, including embedded Microsoft Security Copilot. Candidates should understand AI assistance as a way to accelerate investigation, summarize evidence, or support workflows—not as a replacement for analyst judgment.
Validate generated conclusions against the original evidence. A useful exam mindset is that the analyst remains responsible for the decision. If a scenario asks how to reduce investigation effort while preserving context, an embedded AI capability may help, but any critical action should still be supported by verified findings and organizational policy.
Manage cases
Case management helps security teams coordinate investigation work. Learn the value of status, ownership, classification, comments, tasks, evidence, and documentation. Good case management allows another analyst to understand what happened, what was checked, and what remains open.
When a practice question includes collaboration or handoff, look beyond the technical remediation. The correct response may also require updating ownership, recording evidence, or changing incident status.
Respond in Microsoft Defender for Endpoint
Defender for Endpoint supports detailed device investigation and response. Study device timelines, evidence and entity investigation, live response, investigation packages, and actions that can be taken on a device.
A device timeline helps reconstruct what occurred. Live response provides a controlled remote investigation capability. An investigation package collects useful forensic information. Response actions may include containing a device or addressing a file, process, or other affected entity.
Choose the least disruptive action that safely meets the requirement. If evidence is still needed, collect it before taking an action that could remove or alter that evidence—unless immediate containment is necessary to reduce active harm.
Automatic attack disruption also appears in endpoint-focused response objectives. Be able to investigate what the feature detected and verify the remediation or containment result.
Investigate Microsoft 365 activity
The skills outline includes Microsoft Purview Audit, Content search in Microsoft Purview eDiscovery, and Microsoft Graph activity logs.
Audit helps analysts review actions performed by users and administrators. Content search supports finding relevant content across supported Microsoft 365 locations for an investigation. Microsoft Graph activity logs can provide visibility into Microsoft Graph-related requests and application activity.
The scenario determines the correct source. If you need a record of an administrative action, think about auditing. If you need to locate messages or files matching investigation criteria, consider content search. If the concern involves calls made through Microsoft Graph, activity logs may be the relevant evidence.
After reviewing incident-response topics, View questions for Microsoft certifications and compare your results across identity, endpoint, email, cloud, Sentinel, and Microsoft 365 investigations.
Domain 3: Perform Threat Hunting (20–25%)
Threat hunting is a proactive search for activity that existing alerts may not have fully identified. SC-200 candidates need to understand KQL, hunting data, Advanced Hunting, threat analytics, graph-based investigation, notebooks, and newer Sentinel data-lake capabilities.
Select the correct table
A strong query starts with the right data. Learn the purpose of common Advanced Hunting and Sentinel tables rather than trying to memorize every column. Think in terms of entity and activity:
- Device process activity
- Device network connections
- File activity
- Registry activity
- Logon events
- Email events
- Identity activity
- Cloud application activity
- Sentinel security events and custom data
If a scenario asks which process contacted a suspicious address, begin with process and network evidence. If it asks about a message delivery and attachment, begin with email-related tables. Table selection should follow the investigation question.
Build and interpret KQL queries
KQL allows analysts to filter, transform, summarize, join, and visualize security data. A learner-friendly query-building sequence is:
- Select the table.
- Set a useful time range.
- Filter for the relevant condition.
- Keep or project the fields needed for analysis.
- Summarize when looking for trends or repeated activity.
- Sort the result.
- Join or enrich only when the investigation requires more context.
Practise common operators such as where, project, extend, summarize, sort, join, and time functions. Understand what each stage changes. A long copied query is less useful than a short query you can explain and modify.
Use Advanced Hunting and custom detections
Advanced Hunting in Defender XDR lets analysts search security data across supported domains. Use it to test a hypothesis, trace an entity, review suspicious behavior, or create a repeatable detection.
Before converting a query into a custom detection, confirm that it reliably identifies the intended behavior. Review false positives and ensure that required fields are present. A query that is useful for one investigation may need changes before it is suitable for continuous detection.
Interpret threat analytics
Threat analytics provides Microsoft analysis about active threats, techniques, affected products, and possible detection or mitigation steps. Learn how an analyst can use this information to understand exposure and prioritize hunting.
Threat intelligence does not prove that a specific environment is compromised. Use it to form a hypothesis, identify indicators and behaviors, and search the organization’s data for relevant evidence.
Use hunting graphs and Sentinel Graph
The updated outline includes hunting graphs, blast radius, and analyzing entity relationships with Sentinel Graph. Graph-based views help analysts understand connections among users, devices, resources, addresses, alerts, and other entities.
Blast radius refers to the potential reach or impact around a compromised entity. If one account is affected, the analyst may need to check connected devices, sessions, privileges, applications, and resources. A graph can reveal relationships that are difficult to see in a flat list.
Hunt in Microsoft Sentinel
Microsoft Sentinel supports hunting queries that analysts can create, run, and monitor. A hunting query is designed to explore a security hypothesis rather than automatically create an incident every time it returns a result.
Document the hypothesis and expected evidence. If the hunt finds a reliable malicious pattern, consider whether it should become a detection. If it finds benign but unusual behavior, record the explanation so future analysts do not repeat the same work.
Work with KQL jobs, summary rules, and notebooks
Microsoft’s updated outline includes KQL jobs in the Sentinel data lake, summary-rule tables, and notebooks. KQL jobs can help run queries over data-lake information. Summary rules can create summarized data that is easier and more efficient to query for repeated analytical needs.
Notebooks support deeper or repeatable investigations using code, data analysis, and visualization. They are useful when a hunt requires more than an interactive portal query. The blueprint also mentions connection to the Sentinel MCP Server, so candidates should follow the current Microsoft Learn documentation for supported notebook and agent-assisted workflows.
Choose the simplest suitable tool. A short interactive question may need only KQL. A repeatable, multi-step analysis involving enrichment and visualization may be better suited to a notebook.
What You Get When You Prepare With Us
A structured SC-200 practice process gives students a clear way to move from reading to measurable improvement. The purpose is to identify which skills are ready and which need more work.
Preparation can include:
- Domain-based questions aligned with Microsoft’s published SC-200 blueprint
- Scenario-style practice across Defender XDR, Sentinel, Entra ID, Purview, and Defender for Cloud
- Clear explanations that focus on why an answer fits the requirement
- KQL-focused checks for table choice, filtering, summarization, and investigation logic
- Incident-response scenarios that connect alerts, evidence, containment, and remediation
- Progress tracking that separates scores by domain
- Mixed practice sessions for connecting data ingestion, detection, investigation, automation, and hunting
Practice material should supplement Microsoft Learn, official documentation, labs, and real experience. It should not promise a result or replace hands-on work. Find more exam resources on Edurely while organizing a balanced plan based on learning, application, testing, and review.
How to Use an SC-200 Practice Test Productively
Take a diagnostic test first
Start with a short mixed test before intensive revision. Record the result under the three official domains. Mark answers you guessed correctly because they still represent uncertain knowledge.
The diagnostic should answer a practical question: what should you study next? It is not a final judgment of readiness.
Keep an error log
For each missed question, record:
- The official skill being tested
- The key clue in the scenario
- Why your answer did not meet the requirement
- The correct tool, data source, or workflow
- An official Microsoft Learn page or lab to review
Repeated patterns will become clear. You may understand Defender XDR incidents but struggle with Sentinel ingestion, or you may write basic KQL but choose the wrong table.
Turn mistakes into lab tasks
If you miss a question about automation rules, create a safe lab example that changes an incident property. If data connectors are weak, trace how a selected source reaches Sentinel. If hunting is difficult, write a small query and explain each operator.
This closes the gap between recognition and application.
Practise under time pressure later
Use untimed sessions while learning. Add timed mixed tests after your domain scores become stable. Timed practice helps you read efficiently, notice constraints, and avoid spending too long on one complex scenario.
Explain the answer before reading the explanation
After choosing an option, describe why it is correct in your own words. Then compare your reasoning with the explanation. This reveals whether your knowledge is transferable or tied to familiar wording.
A Four-Week SC-200 Study Plan
Week 1: Build the operations environment
Study Defender XDR and Defender for Endpoint settings, notifications, device groups, automated investigation, attack disruption, Sentinel roles, workbooks, retention, and SOC optimization. Complete short practice sets after each major objective.
Week 2: Master ingestion and detection
Review Azure Monitor Agent, data collection rules, Windows Event Forwarding, Syslog, CEF, Azure activity logs, threat indicators, and custom tables. Then study Defender XDR custom detections, Sentinel analytics rules, MITRE ATT&CK coverage, and anomalies.
Week 3: Practise investigation and response
Work through incidents spanning endpoints, identities, email, cloud apps, cloud workloads, Microsoft 365, and Sentinel. Follow a repeatable investigation method and document evidence, containment, remediation, and verification.
Week 4: Hunt and connect the domains
Practise KQL, Advanced Hunting, threat analytics, hunting queries, graphs, notebooks, KQL jobs, and summary rules. Finish with mixed scenarios that begin with data collection and end with detection, investigation, response, or hunting.
If you have limited Microsoft security experience, extend the plan. SC-200 is easier when you can navigate the tools and understand their relationships rather than remembering product names alone.
Common SC-200 Preparation Mistakes
Studying only one product
SC-200 spans several services. Defender XDR and Sentinel are central, but identity, endpoint, email, cloud, Microsoft 365, and data-protection evidence can all contribute to an investigation.
Memorizing KQL without understanding the data
A syntactically correct query can still search the wrong table or answer the wrong question. Begin with the investigation goal and identify the relevant entity and event type.
Confusing visualization with detection
A workbook presents information. An analytics rule creates detections. A hunting query explores a hypothesis. Learn the outcome of each feature.
Automating an unclear process
Automation should follow reliable logic. Confirm the trigger, required data, permissions, action, and verification step before choosing a playbook or automated response.
Responding before preserving necessary evidence
Immediate containment can be necessary, but some actions change the system. Understand when to collect investigation information and when active risk requires quick isolation.
Repeating the same questions too soon
Memorizing answer positions creates false confidence. Review the skill, complete a lab, and later use a different question that tests the same objective.
Frequently Asked Questions
Who should use an SC-200 practice test?
It is useful for candidates preparing for the Microsoft Security Operations Analyst role, especially learners studying Defender XDR, Microsoft Sentinel, incident response, threat hunting, detection engineering, and KQL.
What are the three SC-200 domains?
The published domains are Manage a security operations environment at 40–45%, Respond to security incidents at 35–40%, and Perform threat hunting at 20–25%.
Why should I check the official study guide?
Microsoft updates exams to reflect changing products and job tasks. The English assessment has an update published for October 21, 2026. Check the official guide against your scheduled test date.
Is KQL important for SC-200?
Yes. Candidates need to select suitable tables, create and interpret hunting queries, use Advanced Hunting, and work with Sentinel hunting and data-lake capabilities.
Should I focus more on Defender XDR or Microsoft Sentinel?
You need both. Defender XDR supports cross-domain detection and response across Microsoft security products, while Sentinel adds SIEM, ingestion, analytics, automation, hunting, and broader data integration capabilities.
How can I improve my incident-response skills?
Use a consistent workflow: validate the alert, identify affected entities, build a timeline, collect evidence, determine scope, contain the threat, remediate the cause, and verify the result.
Can practice tests replace hands-on labs?
No. Practice tests reveal gaps and reinforce decision-making. Labs develop the navigation, query, configuration, investigation, and troubleshooting skills needed for applied questions.
When am I ready for mixed practice?
Move to mixed tests when you can explain the main tools in each domain and your topic-level scores are becoming consistent. Continue reviewing errors rather than relying only on the total score.