Courseiva

Microsoft Security Operations Analyst SC-200 (SC-200) — Questions 601–675

1303 questions total · 18 pages · All types, answers revealed

Page 8

Page 9 of 18

Page 10
601
MCQmedium

A security analyst is creating a custom detection rule in Microsoft 365 Defender using Advanced Hunting. The rule should alert when a user signs in from an IP address that is not in the company's approved IP range (192.168.0.0/16). Which KQL function should be used to compare the sign-in IP against the approved range?

A.ipv4_is_in_range(SigninIP, '192.168.0.0/16')
B.has_any(SigninIP, dynamic(['192.168.0.0/16']))
C.ipv4_is_private(SigninIP)
D.SigninIP startswith '192.168.'
AnswerA

The ipv4_is_in_range function parses both the IP address and the CIDR range, then performs a proper bitwise comparison of the network prefix based on the specified prefix length. It returns true only when the SigninIP falls within the exact 192.168.0.0/16 address space, correctly handling subnet boundaries. This is the recommended KQL approach for testing IP membership in a specific CIDR range and is both reliable and efficient.

Why this answer

The correct KQL function is `ipv4_is_in_range()` because it is specifically designed to check whether an IPv4 address falls within a given CIDR range. In this scenario, the function compares the `SigninIP` field against the company's approved range `192.168.0.0/16` and returns `true` if the IP is within that range, enabling the rule to alert on out-of-range sign-ins. This function handles subnet mask calculations natively, ensuring accurate and efficient IP range matching without manual parsing.

Exam trap

The trap here is that candidates may choose `ipv4_is_private()` thinking it covers all internal ranges, but it does not account for custom or non-RFC 1918 ranges, and it misses the requirement to match a specific CIDR block like 192.168.0.0/16.

How to eliminate wrong answers

Option B is wrong because `has_any()` is a string-matching operator that checks if any substring from a dynamic array exists in a field; it does not perform CIDR range calculations and would incorrectly treat the CIDR notation as a literal string. Option C is wrong because `ipv4_is_private()` only checks if an IP belongs to any private address space (RFC 1918), not whether it falls within a specific custom range like `192.168.0.0/16`; it would also match other private ranges (e.g., 10.0.0.0/8, 172.16.0.0/12), causing false positives. Option D is wrong because `startswith` performs a simple prefix match on the string representation of the IP, which fails for IPs like `192.168.255.255` (correctly in range) but also fails to exclude IPs like `192.169.0.1` (outside the /16 range) because it only checks the first three octets.

602
MCQmedium

Your organization uses Microsoft Sentinel and Microsoft Defender XDR. You receive an alert about a suspicious sign-in from an IP address associated with a known malicious actor. The sign-in was for a privileged account. You need to immediately contain the incident. What should you do first?

A.Reset the user's password.
B.Disable the user account in Microsoft Entra ID.
C.Create a custom analytics rule in Sentinel to detect similar sign-ins.
D.Block the IP address in the firewall.
AnswerB

Disabling the account in Microsoft Entra ID immediately blocks further sign-ins and revokes the compromised privileged identity's access, containing the incident before deeper investigation. It directly addresses the need to contain a suspicious privileged sign-in fastest.

Why this answer

Disabling the user account in Microsoft Entra ID immediately stops the attacker from using the compromised credentials. Option A is wrong because resetting the password might not be fast enough if the attacker has an active session. Option C is wrong because creating an analytics rule does not contain the incident immediately; it only helps detect similar sign-ins in the future.

Option D is wrong because blocking the IP address in the firewall is reactive and may not be effective if the attacker uses a different IP.

603
MCQmedium

You are investigating repeated SQL injection alerts. The KQL query returns IP addresses with more than 5 alerts in the last 7 days. What is the purpose of the `summarize` and `where AlertCount > 5` lines?

A.To identify IPs with a high number of alerts, indicating a possible attack.
B.To correlate alerts with other data sources.
C.To remove duplicate alerts from the same IP.
D.To count the number of distinct IP addresses.
AnswerA

This query aggregates SQL injection alerts by source IP and ranks them by count, so the primary purpose is to surface the IP addresses that trigger the most alert activity. High counts over the selected time range are a strong indicator of an ongoing or repeated attack campaign, and this output directly supports triage, investigation, and potential blocking. The query does not need additional context to fulfill this goal because the aggregation itself is the intended result.

Why this answer

The `summarize` operator in KQL aggregates data by grouping on the IP address field and counting the number of alerts per IP. The `where AlertCount > 5` filter then retains only those IP addresses whose aggregated count exceeds 5. This combination directly serves to identify IPs that have triggered a high volume of SQL injection alerts within the 7-day window, which is a strong indicator of a sustained or automated attack attempt.

Exam trap

The trap here is that candidates may confuse `summarize` with `distinct` or think the `where` clause removes duplicates, when in fact the query is designed to surface high-frequency IPs as potential attack sources, not to deduplicate or count unique IPs.

How to eliminate wrong answers

Option B is wrong because the query does not join or correlate with any other data sources; it only filters and aggregates a single alert table. Option C is wrong because `summarize` with a count does not remove duplicates—it counts occurrences, and the `where` clause filters on that count, not on duplicate removal. Option D is wrong because the query counts alerts per IP, not the number of distinct IPs; a distinct count would use `dcount(IP)` or `distinct` without grouping by IP.

604
MCQmedium

An organization uses Microsoft 365 Defender. A security analyst is reviewing an incident that involves a user who clicked a phishing link in an email. The analyst wants to see the email's full timeline, including delivery, click, and any follow-up actions. Which section of the email entity page provides this information?

A.Detection details
B.Email timeline
C.Threat types
D.Investigation graph
AnswerB

The Email timeline in the Microsoft 365 Defender email entity page is the only view that arranges every associated action into a strict chronological order, including message intake, delivery and deferral events, URL detonation results, user click attempts, reported states, and admin remediation steps. This layout lets an analyst trace exactly when each event occurred relative to others, proving whether an email arrived before a click or whether a block was applied after delivery. It is specifically designed to answer 'what happened, and in what order,' making it the correct choice for viewing the full sequence of events for a single email.

Why this answer

The Email timeline section on the email entity page in Microsoft 365 Defender provides a chronological view of the email's lifecycle, including delivery, user clicks on the phishing link, and subsequent remediation actions such as soft delete or quarantine. This directly meets the analyst's need to see the full sequence of events for the incident.

Exam trap

The trap here is that candidates often confuse the Investigation graph (which shows entity relationships) with the Email timeline (which shows chronological events), leading them to select the graph option when they need a sequential log of actions.

How to eliminate wrong answers

Option A is wrong because Detection details only show the specific detection technologies (e.g., anti-malware, anti-phishing) that flagged the email, not the chronological sequence of delivery, click, and follow-up actions. Option C is wrong because Threat types categorize the email by threat classification (e.g., phishing, malware) but do not provide a timeline of events. Option D is wrong because Investigation graph is a visual representation of related entities and alerts, not a dedicated timeline for a single email's lifecycle.

605
MCQeasy

You are threat hunting for indicators of compromise related to a known malware family. Which data source in Microsoft Defender XDR would provide the most direct evidence of malware execution on endpoints?

A.EmailEvents
B.DeviceProcessEvents
C.IdentityLogonEvents
D.DeviceNetworkEvents
AnswerB

DeviceProcessEvents captures process creation events, which directly indicate malware execution.

Why this answer

DeviceProcessEvents captures process creation events, which directly indicate malware execution. Option A is incorrect because EmailEvents only covers email data, not execution events. Option C (IdentityLogonEvents) focuses on authentication events, not process execution.

Option D (DeviceNetworkEvents) shows network connections that may occur after execution, but does not directly show execution itself.

606
MCQmedium

A threat hunter is investigating a potential malware outbreak in Microsoft Defender for Cloud Apps. The hunter notices that multiple users have installed a new app with high permissions that accesses their email. The app was not requested by IT. What is the most effective way to hunt for all instances of this app across the organization?

A.Review Conditional Access app control policies for any block rules
B.Check Microsoft 365 Defender alerts for malicious OAuth apps
C.Query the Microsoft 365 Defender advanced hunting table 'CloudAppEvents' for app installation events and then use 'AppGovernance' to list all apps
D.Use the Cloud App Security activity log to search for 'Install app' events and then review the 'App governance' dashboard for all instances
AnswerD

In Microsoft Defender for Cloud Apps, the activity log is the authoritative source for operational events, and filtering for the activity type 'Install app' directly surfaces when an OAuth app was introduced to the tenant. After identifying these installation events, the App governance dashboard provides a unified inventory of all app instances, including permissions, publisher, and usage, enabling the hunter to scope the outbreak. This sequence—find the installation event, then pivot to the governance inventory—matches the intended workflow for OAuth app threat hunting.

Why this answer

The activity log in Cloud App Security provides a comprehensive record of app installation events, and the App Governance dashboard aggregates all instances for review, making it the most effective hunting approach. Option A (conditional access policies) is reactive and not suitable for proactive hunting. Option B (Microsoft 365 Defender alerts) only surfaces known malicious apps, not all instances.

Option C (CloudAppEvents table and AppGovernance) can be used, but the activity log is more direct and complete for hunting all installations, as CloudAppEvents may not capture every installation event or may require complex queries.

607
MCQhard

A SOC analyst wants to detect when a user signs in from a device that has never been used by that user before. The analyst plans to use Microsoft Sentinel with the SigninLogs table. Which KQL approach correctly identifies sign-ins from devices not previously associated with the user within the last 30 days?

A.Join the SigninLogs table with itself to find the earliest sign-in per user and device, then filter for those that match the earliest timestamp
B.Use the _GetWatchlist function with a custom watchlist of known user-device pairs
C.Use the BehaviorAnalytics table which already identifies new devices
D.Apply the 'where DeviceId != '' and DeviceId startswith "device-"' filter to ensure the device is new
AnswerA

The correct logic is to derive the earliest sign-in timestamp for each user-device pair using `summarize arg_min(TimeGenerated, *) by UserId, DeviceId` and then join that summary back to the original SigninLogs table on the same user, device, and timestamp. This self-join effectively identifies only the first occurrence of a sign-in for that combination, so any row in the original table that matches the earliest timestamp for its pair is a new-device sign-in. This approach uses historical data already in the table and does not require external lists or pre-computed analytics, making it a fully self-contained and accurate detection.

Why this answer

It uses a self-join on the SigninLogs table to identify the earliest sign-in per user-device pair within the last 30 days. By filtering for rows where the sign-in timestamp matches the earliest timestamp, the query isolates sign-ins from devices that have never been used by that user before, effectively detecting first-time device usage.

Exam trap

The trap here is that candidates may assume a watchlist or pre-built table like BehaviorAnalytics is the easiest solution, but Microsoft Sentinel requires raw log analysis with KQL self-joins to dynamically detect first-time device usage without manual maintenance.

How to eliminate wrong answers

Option B is wrong because the _GetWatchlist function requires a pre-built watchlist of known user-device pairs, which is a manual, static approach that does not dynamically detect new devices within the last 30 days. Option C is wrong because the BehaviorAnalytics table provides pre-computed behavioral insights but does not directly contain raw sign-in logs or device-level data to identify new devices per user; it relies on underlying tables like SigninLogs for such analysis. Option D is wrong because filtering by DeviceId != '' and DeviceId startswith 'device-' does not identify new devices; it merely excludes empty or non-matching device IDs, and the prefix 'device-' is not a standard Azure AD device ID format.

608
MCQmedium

A security analyst in Microsoft 365 Defender needs to review all actions that were automatically taken by an investigation (e.g., isolating a device, deleting a file) that occurred during an incident. Where should the analyst find this list of executed actions?

A.Action center
B.Hunting queries
C.Incidents page
D.Alerts page
AnswerA

Action center is the centralized console in Microsoft 365 Defender that consolidates all automated and manual remediation actions taken during investigations. It provides a unified queue with detailed status (e.g., Pending, Completed, Failed), execution history, approval workflows for pending actions, and results for each operation such as quarantining a file, isolating a device, or blocking a sender. This makes it the authoritative location for reviewing both the actions themselves and their outcomes.

Why this answer

The Action center in Microsoft 365 Defender is the centralized location that records all manual and automated response actions taken during investigations, such as device isolation, file deletion, or process termination. This includes actions automatically executed by automated investigation and response (AIR) playbooks during an incident. The analyst can filter the Action center by 'Automated' to see only those actions taken without manual intervention.

Exam trap

The trap here is that candidates confuse the Incidents page (which shows the overall story) with the Action center (which is the specific repository for executed actions), leading them to select the Incidents page instead of the correct Action center.

How to eliminate wrong answers

Option B is wrong because Hunting queries are used for proactive threat hunting using Kusto Query Language (KQL) to search for raw telemetry and logs, not to review a list of already-executed response actions. Option C is wrong because the Incidents page shows the incident summary, timeline, and related alerts, but it does not provide a dedicated, filterable list of all executed actions; the Action center is the specific location for that. Option D is wrong because the Alerts page lists individual alerts triggered by suspicious activities, but it does not aggregate the automated response actions taken; those actions are recorded in the Action center after an alert triggers an investigation.

609
MCQeasy

You are configuring Microsoft Sentinel to send email notifications to the security team when high-severity incidents are created. Which feature should you use?

A.Automation rule
B.Watchlist
C.Analytics rule
D.Workbook
AnswerA

Automation rules in Microsoft Sentinel are designed to centralize and automate incident handling, and one of their primary actions is to run playbooks (Azure Logic Apps). A playbook can include a step that sends an email through a mail connector, such as Office 365 Outlook or SendGrid, allowing a notification to be dispatched immediately after certain conditions are met. Because automation rules are the only construct among these choices that can directly trigger a playbook that performs an external action like email, this is the correct mechanism for configuring email notifications.

Why this answer

Automation rules in Microsoft Sentinel allow you to define automated responses to incidents, including sending email notifications to specified recipients when incidents meet certain criteria, such as high severity. This feature directly supports the requirement to notify the security team when high-severity incidents are created, without requiring additional logic or manual steps.

Exam trap

The trap here is that candidates often confuse analytics rules with automation rules, assuming that analytics rules can directly send notifications, when in fact they only create alerts/incidents and require automation rules or playbooks for notification actions.

How to eliminate wrong answers

Option B is wrong because watchlists are collections of data (e.g., IP addresses, usernames) used for correlation and enrichment in analytics rules, not for triggering actions like email notifications. Option C is wrong because analytics rules generate alerts and incidents based on query results, but they do not natively send email notifications; they rely on automation rules or playbooks for that purpose. Option D is wrong because workbooks are visualization tools that display data from queries and logs, not mechanisms for sending notifications or triggering automated responses.

610
MCQeasy

You are a Microsoft Security Operations Analyst. Your organization recently deployed Microsoft Defender for Cloud Apps. You need to ensure that alerts generated by Defender for Cloud Apps are automatically forwarded to Microsoft Sentinel. What should you configure?

A.In Microsoft Sentinel, create an analytics rule with a query that pulls data from Defender for Cloud Apps API.
B.In Microsoft Defender for Cloud Apps, configure SIEM integration.
C.In Microsoft Sentinel, configure a playbook to retrieve alerts from Defender for Cloud Apps.
D.In Microsoft Sentinel, add the Microsoft Defender for Cloud Apps data connector.
AnswerD

The Microsoft Defender for Cloud Apps data connector is the Microsoft-supported method for ingesting cloud app alerts, Cloud Discovery logs, and other security events directly into Microsoft Sentinel's Log Analytics workspace. This connector automatically streams data using the underlying Microsoft 365 Defender or standalone Defender for Cloud Apps APIs, making the information immediately available for analytics rules and workbooks. It provides the native schema and ensures proper correlation with other security data sources in Sentinel.

Why this answer

The Microsoft Defender for Cloud Apps data connector in Microsoft Sentinel is the native integration that automatically forwards alerts and cloud discovery logs from Defender for Cloud Apps into Sentinel. This connector uses the Microsoft Graph Security API to ingest alerts without requiring additional configuration in Defender for Cloud Apps, enabling seamless correlation and investigation within Sentinel.

Exam trap

The trap here is that candidates confuse the generic SIEM integration in Defender for Cloud Apps (which uses syslog or REST for third-party SIEMs) with the purpose-built Microsoft Sentinel data connector, leading them to select Option B.

How to eliminate wrong answers

Option A is wrong because creating an analytics rule with a query that pulls data from the Defender for Cloud Apps API is not a supported method for automatic ingestion; analytics rules analyze data already in Sentinel, not pull external data. Option B is wrong because configuring SIEM integration in Defender for Cloud Apps is used to forward alerts to generic SIEMs via syslog or REST API, not to Microsoft Sentinel, which requires the dedicated data connector. Option C is wrong because a playbook is an automated response workflow triggered after data is already in Sentinel, not a mechanism to retrieve alerts from Defender for Cloud Apps.

611
MCQeasy

Your organization uses Microsoft Sentinel. An incident has been identified as a false positive. What is the recommended action to prevent similar false positives in the future?

A.Delete the analytics rule
B.Close the incident and set the classification to 'False positive'
C.Modify the analytics rule to reduce false positives
D.Mark the incident as 'False positive' and add a comment
AnswerC

Modifying the analytics rule is the correct action because it directly addresses the root cause of the false positives by adjusting the rule's query logic, threshold, or entity-specific filters. For example, you can add exclusions for known benign IP addresses, increase the aggregation window count, or refine the KQL query to be more context-aware. This persistent tuning prevents recurrence, reduces alert noise, and maintains security coverage for real threats.

Why this answer

Modifying the analytics rule addresses the root cause of the false positive by adjusting the rule's query logic, thresholds, or entity mappings to reduce noise. In Microsoft Sentinel, analytics rules define the conditions that generate incidents; tuning these rules (e.g., changing frequency, lookback period, or adding exclusion filters) directly prevents similar false positives from recurring. Simply closing or classifying incidents does not prevent future occurrences, and deleting the rule would remove all detection capability.

Exam trap

The trap here is that candidates confuse incident management actions (closing/classifying) with rule optimization, assuming that marking an incident as false positive automatically suppresses future similar alerts, when in fact it only affects the current incident's audit trail.

How to eliminate wrong answers

Option A is wrong because deleting the analytics rule removes all detection for that scenario, which is overly aggressive and could miss real threats; the goal is to reduce false positives, not eliminate detection entirely. Option B is wrong because closing an incident with classification 'False positive' only documents the current incident and does not modify the underlying rule to prevent future false positives. Option D is wrong because marking the incident as 'False positive' and adding a comment is a manual documentation step that has no effect on the analytics rule's behavior or future incident generation.

612
MCQhard

A security analyst in your company uses Microsoft Defender XDR to investigate an incident involving a user who received a malicious email. The analyst needs to block the sender's email address across all tenants in the organization. What is the most efficient way to achieve this?

A.In the Microsoft 365 Defender portal, use the action center to block the sender's email address across all tenants.
B.From the Microsoft 365 Defender portal, go to Email & collaboration > Exchange admin center and block the sender.
C.In Microsoft Purview, create a data loss prevention policy to block the sender.
D.In Microsoft Entra ID admin center, create a conditional access policy to block the sender.
AnswerA

The Microsoft 365 Defender action center aggregates manual and automated remediation actions across Defender for Office 365 and other workloads, and in multi-tenant environments it allows a global operation such as blocking a sender’s email address to be applied to all affected tenants simultaneously. This action is enforced at the transport layer, ensuring malicious mail is intercepted before delivery. It is the designed workspace for centralized threat containment, unlike per-tenant management portals.

Why this answer

Microsoft Defender XDR allows you to take action on entities like email senders. Using the action center, you can block the sender's email address globally, which applies to all tenants. Option C is correct.

Option A is wrong because Exchange admin center works per tenant and is not as efficient for cross-tenant blocking. Option B is wrong because Microsoft Entra ID admin center manages identities, not email blocking. Option D is wrong because Microsoft Purview is for compliance, not email threat protection.

613
MCQhard

You are reviewing a scheduled analytics rule in Microsoft Sentinel. What does the suppressionDuration setting affect?

A.It groups alerts into a single incident within that time window.
B.It delays the execution of the query by that amount of time.
C.It determines how often the query runs.
D.It stops the rule from creating new alerts for that duration after an alert is generated.
AnswerD

When suppression is enabled, after the rule successfully generates an alert, Sentinel will not create any new alerts for the configured duration, even if subsequent query executions return matching results. This is a post-detection quiet period designed to avoid alert fatigue from repeated identical findings. The suppression timer resets only when a new alert is actually created, and the rule continues to run queries but suppresses their alerts until the duration lapses.

Why this answer

The suppressionDuration setting in a Microsoft Sentinel scheduled analytics rule stops the rule from creating new alerts for a specified period after an alert is generated. This prevents alert fatigue by suppressing duplicate alerts from the same rule when the same conditions persist, allowing analysts to focus on unique incidents.

Exam trap

The trap here is confusing suppressionDuration with incident grouping or query frequency settings, as candidates often think it controls how alerts are merged or how often the rule runs, rather than its actual purpose of temporarily halting alert creation after an alert fires.

How to eliminate wrong answers

Option A is wrong because grouping alerts into a single incident within a time window is controlled by the 'Grouping' settings (e.g., 'Group all events into a single alert' and 'Group alerts into a single incident'), not by suppressionDuration. Option B is wrong because delaying the execution of the query is not a function of suppressionDuration; query execution timing is determined by the 'Run query every' and 'Lookup data from the last' settings. Option C is wrong because how often the query runs is set by the 'Run query every' interval, not by suppressionDuration, which only affects alert creation after an alert is generated.

614
MCQmedium

A large enterprise uses Microsoft Defender for Cloud with all enhanced security plans (e.g., Defender for Servers, Defender for SQL) enabled on a management group. The security team wants to automatically enable these plans on new Azure subscriptions that are created under this management group. Which approach is the most efficient and scalable?

A.Use an Azure Policy definition that enforces the Microsoft Defender for Cloud pricing tier (Standard) at the management group scope.
B.Manually enable the plans for each new subscription when it is created.
C.Create an Azure Automation runbook that runs on a schedule and enables plans for all subscriptions under the management group.
D.Use Azure Blueprints to define the Defender for Cloud settings in the blueprint definition.
AnswerA

Azure Policy's built-in 'Configure Microsoft Defender for Cloud plans to be enabled' definition, assigned at the management group, uses the DeployIfNotExists effect to update the pricing tier of every subscription under that scope. Because policy inheritance is evaluated continuously, any subscription created later is non-compliant until remediated, and the policy engine will automatically enable the Defender plans without human intervention. This provides declarative, continuous enforcement that scales across the entire enterprise.

Why this answer

Azure Policy can be assigned at the management group scope to enforce the 'Standard' pricing tier for Microsoft Defender for Cloud on all current and future subscriptions. This ensures that when a new subscription is created under that management group, the policy automatically evaluates and remediates the subscription to enable the required Defender plans, providing a fully automated, scalable, and governance-driven approach without manual intervention or custom scripting.

Exam trap

The trap here is that candidates often confuse Azure Blueprints (which apply settings only at deployment time) with Azure Policy (which provides continuous enforcement and automatic remediation), leading them to choose the Blueprints option despite its lack of ongoing compliance and scalability for new subscriptions.

How to eliminate wrong answers

Option B is wrong because manually enabling plans for each new subscription is not scalable, introduces human error, and violates the principle of automated governance at scale. Option C is wrong because an Azure Automation runbook running on a schedule introduces latency, requires custom code and credential management, and does not provide real-time enforcement or compliance reporting like Azure Policy does. Option D is wrong because Azure Blueprints are deprecated in favor of deployment stacks and do not provide continuous enforcement of Defender for Cloud pricing tiers; they only apply settings at deployment time and do not automatically remediate drift or new subscriptions after the blueprint assignment.

615
MCQmedium

A SOC team uses Microsoft Sentinel. They need to correlate syslog events from on-premises firewalls with Microsoft Entra ID sign-in logs to detect VPN-based intrusions. The correlation requires joining two tables (Syslog and SigninLogs) on a common field (IP address) and running on a 10-minute schedule. Which type of analytics rule should the analyst configure?

A.Scheduled query rule
B.Near-real-time (NRT) rule
C.Fusion rule
D.Anomaly rule
AnswerA

Scheduled query rules are the correct choice for correlating Syslog with other data sources because they accept fully custom KQL queries that can join, union, or aggregate multiple tables. You can schedule the query to run at any interval and define alert logic that matches your correlation criteria, such as joining Syslog and CommonSecurityLog on hostname or source IP. The alert generated includes the full query results, enabling analysts to investigate both sides of the correlation directly from the incident.

Why this answer

A scheduled query rule is correct because the requirement involves joining two tables (Syslog and SigninLogs) on a common field (IP address) and running on a 10-minute schedule. Scheduled query rules are designed for complex, multi-table correlations that run at fixed intervals (e.g., every 10 minutes) and can aggregate or join data across tables, making them ideal for this VPN intrusion detection scenario.

Exam trap

The trap here is that candidates often confuse NRT rules with scheduled rules, but NRT rules cannot perform multi-table joins, which is explicitly required by the question's correlation of Syslog and SigninLogs.

How to eliminate wrong answers

Option B is wrong because near-real-time (NRT) rules run every minute with a 1-minute lookback and cannot join multiple tables; they only support a single table query. Option C is wrong because Fusion rules are based on Microsoft's built-in machine learning correlation of multiple alert types, not custom user-defined joins on syslog and sign-in logs. Option D is wrong because anomaly rules use machine learning to detect unusual patterns in a single data source over time, not cross-table joins on a fixed schedule.

616
MCQhard

Your organization uses Microsoft Defender for Cloud Apps and Microsoft Sentinel. You need to ensure that anomalous behavior alerts from Defender for Cloud Apps are automatically converted to incidents in Sentinel. What should you configure?

A.Enable the Microsoft Defender for Identity data connector in Microsoft Sentinel.
B.Enable the Microsoft 365 data connector in Microsoft Sentinel.
C.Create a playbook that triggers on Defender for Cloud Apps alerts and creates incidents in Sentinel.
D.Enable the Microsoft Defender for Cloud Apps data connector in Microsoft Sentinel.
AnswerD

The Microsoft Defender for Cloud Apps data connector is the native Microsoft Sentinel integration designed to ingest alerts from Defender for Cloud Apps, including impossible travel, activity from anonymous IP addresses, and suspicious cloud application usage. It uses the MDCA API to automatically pull these alerts and create corresponding incidents in Sentinel without requiring custom Logic Apps or playbook orchestration. Enabling this connector is the correct configuration to satisfy the requirement of having Defender for Cloud Apps alerts appear as Sentinel incidents.

Why this answer

The Microsoft Defender for Cloud Apps data connector in Microsoft Sentinel is specifically designed to ingest alerts and anomalies from Defender for Cloud Apps and automatically create SecurityIncident records in Sentinel. Enabling this connector ensures that anomalous behavior alerts are converted to incidents without requiring custom playbooks or additional logic.

Exam trap

The trap here is that candidates often confuse the purpose of data connectors—assuming any Microsoft security connector (like Defender for Identity or Microsoft 365) will ingest all security alerts, when in fact each connector is scoped to its specific product's data source.

How to eliminate wrong answers

Option A is wrong because the Microsoft Defender for Identity data connector ingests alerts from on-premises Active Directory signals, not from Defender for Cloud Apps. Option B is wrong because the Microsoft 365 data connector ingests logs from Office 365 services (e.g., Exchange, SharePoint) but does not process Defender for Cloud Apps alerts. Option C is wrong because while a playbook could manually create incidents, the native data connector provides automatic and seamless incident creation without the overhead of custom automation.

617
MCQeasy

During a threat hunt, you identify a suspicious process that spawned from Microsoft Word with a command-line argument containing ' -enc '. Which hunting technique is most appropriate to investigate this further?

A.Review the PowerShell script block logging
B.Initiate network traffic analysis for the host
C.Check the file hash against threat intelligence feeds
D.Decode the base64-encoded command-line argument
AnswerA

Reviewing PowerShell script block logging could provide additional context, but it is not the most direct way to investigate an encoded command. Decoding the '-enc' argument first yields the actual command.

Why this answer

The '-enc' argument is a well-known PowerShell parameter indicating a Base64-encoded command, often used by attackers to obfuscate malicious scripts. In Microsoft Defender for Endpoint and SC-200 hunting scenarios, the most appropriate technique is to review PowerShell script block logging (Event ID 4104), which records the decoded script block content and provides the actual PowerShell code executed. This allows the analyst to understand the intent and actions of the suspicious process without manually decoding the argument.

While manual decoding can be useful, script block logging is the standard hunting technique that surfaces the decoded command directly in the telemetry.

Exam trap

SC-200 often tests the misconception that the '-enc' argument itself must be manually decoded to investigate. In reality, PowerShell script block logging (Event ID 4104) captures the decoded script block content, making it the most appropriate hunting technique. Manual decoding is a fallback when logging is not configured or the event is missing.

How to eliminate wrong answers

Option A is wrong because while PowerShell script block logging would capture the decoded script if enabled, it may not be available or may not have logged the event, and the question asks for the most appropriate technique based on the given command line. Option B is wrong because network traffic analysis, though useful, does not directly address the encoded command line and would be a subsequent step after understanding the script's behavior. Option C is wrong because checking the file hash against threat intelligence is irrelevant here; the suspicious element is the command-line argument, not a file, and the hash of Word or PowerShell would not provide insight into the encoded command.

618
MCQmedium

Your organization uses Microsoft Defender XDR. The incident queue shows multiple alerts related to a single endpoint: malware detected, suspicious PowerShell execution, and data exfiltration attempts. The analyst needs to investigate the incident. Which tool should the analyst use to correlate these events?

A.Microsoft Defender for Office 365 Explorer.
B.Microsoft Defender for Cloud Apps activity log.
C.Advanced hunting in Microsoft Defender XDR.
D.Microsoft Sentinel incident workspace.
AnswerC

Advanced hunting in Microsoft Defender XDR lets you query raw telemetry across the entire Microsoft ecosystem—endpoints, emails, cloud apps, identities, and more—using Kusto Query Language (KQL). You can perform multi-table joins to correlate low-level events, like a suspicious PowerShell process on one device that contacted a malicious URL previously phished in an email. This unified schema is built specifically for proactive and reactive incident hunting and is the correct native tool for a cross-domain Defender XDR incident.

Why this answer

Advanced hunting in Microsoft Defender XDR allows the analyst to query across multiple data sources—including endpoint detection and response (EDR), identity, email, and cloud app data—using Kusto Query Language (KQL). This enables correlation of the malware detection, suspicious PowerShell execution, and data exfiltration alerts on the same device by joining tables such as DeviceEvents, DeviceProcessEvents, and DeviceNetworkEvents, providing a unified timeline of the attack chain.

Exam trap

The trap here is that candidates often confuse the purpose of Advanced hunting (a cross-domain query engine) with Microsoft Sentinel’s incident workspace (a SIEM incident management interface), leading them to choose Option D because they think a SIEM is always the best correlation tool, even though the question specifically asks for correlation within Defender XDR.

How to eliminate wrong answers

Option A is wrong because Microsoft Defender for Office 365 Explorer is designed for investigating email-based threats (phishing, malware in attachments/links) and does not ingest endpoint process or network events from Defender for Endpoint. Option B is wrong because Microsoft Defender for Cloud Apps activity log focuses on user and app activities in cloud applications (e.g., SharePoint, OneDrive, Azure AD sign-ins) and lacks endpoint-level process execution and network connection data. Option D is wrong because Microsoft Sentinel incident workspace is a SIEM/SOAR platform that aggregates alerts from multiple sources, but it is not the primary tool for performing cross-table endpoint event correlation within Defender XDR; Advanced hunting is the native query engine for that purpose.

619
MCQeasy

A security analyst is investigating a phishing incident in Microsoft 365 Defender. They need to view the original email's sender, delivery action, and any automated remediation steps taken. Which entity page should the analyst open?

A.User entity page
B.Device entity page
C.Email entity page
D.IP entity page
AnswerC

The email entity page is the definitive source for email-related investigation in Microsoft 365 Defender, offering the full message envelope: sender and recipient addresses, message ID, subject, and the deliver action—such as delivered, blocked, or quarantined—along with any automated remediation steps, including zero-hour auto purge (ZAP) or soft deletion. Because a phishing incident centers on the email itself, this page directly exposes the evidence needed to trace the message's path and confirm the incident's scope, making it the correct choice for such investigations.

Why this answer

The Email entity page in Microsoft 365 Defender (part of Microsoft Defender XDR) is specifically designed to provide a comprehensive view of an email message, including the original sender, delivery action (e.g., delivered, quarantined, blocked), and any automated remediation steps (e.g., zero-hour auto purge, soft delete). This page aggregates data from Exchange Online Protection (EOP) and Microsoft Defender for Office 365, making it the correct choice for investigating phishing incidents.

Exam trap

The trap here is that candidates may confuse the User entity page with email investigation because user accounts are often involved in phishing, but the User entity page lacks the specific email message-level details (sender, delivery action, remediation) that only the Email entity page provides.

How to eliminate wrong answers

Option A is wrong because the User entity page focuses on user-related activities, sign-ins, and alerts, but does not expose the original email's sender, delivery action, or remediation steps for a specific message. Option B is wrong because the Device entity page is used for investigating device-level threats, such as malware or suspicious processes, and has no context for email-specific attributes like sender or delivery action. Option D is wrong because the IP entity page provides information about network traffic and IP reputation, but it cannot show the original email's sender or automated remediation steps taken on a message.

620
Drag & Dropmedium

Arrange the steps to configure a Microsoft Sentinel playbook (automation) using Azure Logic Apps.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Playbooks are Logic Apps that automate responses; they must be created and then linked to Sentinel automation rules.

621
MCQmedium

Refer to the exhibit. The KQL query is used for threat hunting. What is the primary purpose of this query?

A.Identify devices where cmd.exe launched PowerShell and made outbound HTTPS connections.
B.Find devices where PowerShell was used to download files.
C.Detect lateral movement using remote services.
D.Identify cmd.exe running with high integrity.
AnswerA

The query correlates DeviceProcessEvents with DeviceNetworkEvents, joining on DeviceId and a time window to link cmd.exe spawning PowerShell with subsequent outbound HTTPS traffic. This satisfies the hunting objective of surfacing suspicious process-to-network chains, where a command shell launching PowerShell and beaconing externally indicates potential malicious activity.

Why this answer

The KQL query joins process creation events where `cmd.exe` is the parent and `powershell.exe` is the child with network events from the same device, filtering for outbound HTTPS (port 443) — this pattern identifies devices where a command shell spawned PowerShell that then made encrypted outbound connections, a common living-off-the-land technique. The join on DeviceId and time window is what ties the process chain to the network activity, which is the query's defining purpose.

Exam trap

SC-200 often tests whether candidates read the *join and filter* conditions rather than the surface process names — distractors like 'download files' or 'lateral movement' sound plausible but are not what the query's columns and port filter actually select for.

How to eliminate wrong answers

Option B is wrong because the query does not filter on file-download cmdlets (e.g., `Invoke-WebRequest`, `DownloadFile`) or file-write events — it only correlates process lineage with outbound connections. Option C is wrong because lateral movement detection would require remote service artifacts (SMB, WMI, PsExec, RDP) and authentication events, none of which appear in the query. Option D is wrong because integrity level is not referenced — the query does not filter on `IntegrityLevel` or token elevation, only on the parent-child process relationship and network port.

622
Multi-Selecthard

Which THREE actions should be taken when a phishing attack is detected in Microsoft Defender XDR?

Select 3 answers
A.Run a full antivirus scan on the user's device
B.Report the email as phishing in Microsoft Defender for Office 365
C.Reset the user's password
D.Block the sender's email address or domain
E.Delete the phishing email from the user's mailbox
AnswersB, D, E

Reporting submits the email to Microsoft for analysis, which updates the threat intelligence and improves automated detection for the whole organization. In MDO, this can be done via the User-reported messages report or the built-in Report Message add-in. This action also allows the security team to investigate the incident and potentially automate remediation policies.

Why this answer

Reporting the email as phishing in Microsoft Defender for Office 365 triggers automated investigation and remediation workflows, including tenant-level block actions and threat intelligence updates. This action directly supports the incident response process by enabling the security team to analyze the phishing attempt and prevent further delivery to other users.

Exam trap

The trap here is that candidates often confuse the immediate containment actions (block sender, delete email) with post-compromise remediation steps (password reset, antivirus scan), leading them to select options that are appropriate only after a confirmed credential theft or malware infection.

623
MCQmedium

The exhibit shows a partial playbook trigger configuration in Microsoft Sentinel. When will this playbook be triggered?

A.When an incident is updated with severity High.
B.When an alert is generated with severity High.
C.When an incident of severity High is created.
D.When any incident is created.
AnswerC

This is correct because the trigger explicitly references an incident creation event and includes a condition that checks the incident's severity equals High. Only new incidents that meet this severity requirement will activate the playbook; all other incidents will be ignored by this trigger. The condition is evaluated as part of the incident creation flow, so the playbook runs immediately when a High-severity incident is born.

Why this answer

The playbook trigger configuration shown in the exhibit specifies that the playbook runs when an incident is created, and it includes a condition that filters for incidents with a severity of High. In Microsoft Sentinel, playbook triggers can be set on incident creation or alert creation, and conditions like severity are evaluated at the time of the trigger event. Here, the trigger is explicitly set to 'When an incident is created' with a severity condition of 'High', so the playbook only fires when a new incident with High severity is created.

Exam trap

The trap here is that candidates often confuse the trigger event (creation vs. update) or overlook the severity condition, assuming the playbook runs on any incident creation when the exhibit clearly shows a filter for High severity.

How to eliminate wrong answers

Option A is wrong because the trigger is set to fire on incident creation, not on incident update; the condition 'When an incident is updated' would require a different trigger type in Sentinel. Option B is wrong because the trigger is configured for incidents, not alerts; alert triggers are separate and would use 'When an alert is generated' as the trigger type. Option D is wrong because the playbook includes a severity condition of 'High', so it does not trigger on all incidents—only those with High severity.

624
MCQmedium

Your organization uses Microsoft Sentinel in a hybrid environment with on-premises servers and Azure VMs. You need to ensure that all Windows servers forward their security events to Sentinel. The security team wants to use Windows Security Events via AMA connector. Windows servers are not domain-joined and are managed by a third-party RMM tool. What is the most efficient way to deploy the AMA agent?

A.Use Group Policy Objects (GPO) to push the agent installation.
B.Onboard the servers to Azure Arc and deploy the AMA agent via policy or script.
C.Use Microsoft Intune to deploy the AMA agent to all servers.
D.Manually install the agent on each server using the setup wizard.
AnswerB

Onboarding the servers to Azure Arc registers each physical or virtual machine as a first-class Azure resource, giving it an identity and the ability to be managed via Azure Policy. Once the AzureConnectedMachine agent is installed, you can use the built-in Azure Policy definition 'Configure Windows machines to run Azure Monitor Agent' to automatically deploy the AMA at scale, or invoke a script that uses the Azure portal-created install command. Because Arc works regardless of domain membership, this is the correct and recommended path for non-domain-joined servers in a hybrid scenario.

Why this answer

Azure Arc provides a control plane for non-Azure and on-premises servers, enabling them to be managed like Azure resources. Once onboarded to Azure Arc, you can deploy the Azure Monitor Agent (AMA) via Azure Policy or custom scripts, which is the most efficient method for non-domain-joined servers managed by a third-party RMM tool, as it avoids manual intervention and leverages Azure's centralized management.

Exam trap

The trap here is that candidates assume GPO or Intune are universal deployment tools, but the question's key constraint—'not domain-joined'—disqualifies GPO, and Intune requires Azure AD join or enrollment, which is not stated; Azure Arc is the correct answer because it specifically enables management of non-Azure, non-domain-joined servers via Azure policies.

How to eliminate wrong answers

Option A is wrong because Group Policy Objects (GPO) require Active Directory domain-joined computers; the servers are explicitly not domain-joined, so GPO cannot be applied. Option C is wrong because Microsoft Intune is designed for managing mobile devices and cloud-managed endpoints, not on-premises servers that are not enrolled in Intune or Azure AD joined; it cannot deploy agents to servers managed by a third-party RMM tool. Option D is wrong because manually installing the agent on each server is inefficient, error-prone, and does not scale, contradicting the requirement for the 'most efficient' deployment method.

625
Multi-Selectmedium

Which THREE components are required to collect syslog messages from a network appliance into Microsoft Sentinel using the Azure Monitor Agent?

Select 3 answers
A.A syslog daemon (e.g., rsyslog) on the log collector server to receive messages.
B.The Azure Monitor Agent installed on a log collector server.
C.The Log Analytics agent (MMA) installed on the appliance.
D.The Syslog data connector in Microsoft Sentinel.
E.A Data Collection Rule (DCR) specifying the syslog facilities and severities.
AnswersA, B, E

The syslog daemon (typically rsyslog) is the foundational listener that binds to UDP/TCP port 514 on the log collector server and receives raw syslog messages forwarded by network appliances. Without this daemon, incoming syslog packets would have no process to capture them, so the Azure Monitor Agent would have nothing to read and no data would reach Sentinel. The daemon must be configured to accept remote input and write messages to a local log file that the agent can monitor.

Why this answer

Syslog messages are sent over UDP (or TCP) by network appliances, and a syslog daemon like rsyslog must be running on the log collector server to listen on port 514 (or a custom port) and receive those messages. Without this daemon, the Azure Monitor Agent cannot ingest the raw syslog data, as the agent relies on the local syslog daemon to capture and forward the logs to its event pipeline.

Exam trap

The trap here is that candidates often confuse the Syslog data connector (a configuration blade in Sentinel) as a required component, when in fact it is just a UI helper; the actual collection relies on the syslog daemon, AMA, and a DCR, which are the three components explicitly tested.

626
MCQmedium

A SOC analyst wants to leverage Microsoft Sentinel's User and Entity Behavior Analytics (UEBA) to detect anomalous sign-in attempts where a user signs in from a country outside their typical pattern. The analyst needs to create an analytics rule that queries the necessary UEBA data. Which Sentinel table should the rule's KQL query primarily reference to evaluate geographic anomalies?

A.SigninLogs
B.BehaviorAnalytics
C.IdentityInfo
D.AADUserRiskEvents
AnswerB

BehaviorAnalytics is the dedicated table where Sentinel's UEBA writes the results of its ML-based behavioral modeling, including weekly baseline scores, geographic anomaly indicators, device trust levels, and time-activity patterns. It exposes rich columns such as UsersInsights, DevicesInsights, and ActivityInsights, each containing structured flags and confidence scores for anomalies like impossible travel or unusual geo-zone sign-ins. Because this table is purpose-built for enriched behavioral evidence, it is the correct target when an analyst needs geographic anomaly detection computed by UEBA.

Why this answer

The BehaviorAnalytics table in Microsoft Sentinel is specifically designed to store UEBA output, including normalized user behavior data such as historical geo-location patterns and anomaly scores. By querying this table, the analyst can directly access pre-computed anomalies for sign-in location deviations without needing to perform complex baseline calculations on raw SigninLogs.

Exam trap

The trap here is that candidates often assume raw sign-in logs (SigninLogs) are sufficient for UEBA-based detection, not realizing that Microsoft Sentinel's UEBA pre-processes and enriches the data into the BehaviorAnalytics table, which is the authoritative source for anomaly queries.

How to eliminate wrong answers

Option A is wrong because SigninLogs contains raw Azure AD sign-in events but lacks the pre-computed behavioral baselines and anomaly scores that UEBA provides, requiring the analyst to manually build and maintain a baseline for geographic patterns. Option C is wrong because IdentityInfo stores user profile and attribute data (e.g., job title, department) but does not contain sign-in activity or behavioral analytics. Option D is wrong because AADUserRiskEvents logs risk detections from Azure AD Identity Protection (e.g., leaked credentials, impossible travel) but does not expose the UEBA-derived geographic anomaly scores or the normalized behavior records found in BehaviorAnalytics.

627
MCQeasy

A security analyst receives an alert in Microsoft Defender for Cloud that an Azure virtual machine is running a process with a known indicator of compromise (IOC). The analyst wants to investigate the process details, including the command line and parent process. Which feature should the analyst use to gather this information from the VM?

A.Vulnerability assessment
B.Live response
C.Inventory of resources
D.Secure score
AnswerB

Live response is correct because it gives an analyst a remote interactive shell into a Windows or Linux VM, enabling built-in investigation commands such as process listing, network connection enumeration, and scheduled task review in real time. This directly matches the alert-handling need to inspect what a particular process executed on the host, and it also supports collecting forensic artifacts for further analysis.

Why this answer

Live Response in Microsoft Defender for Cloud provides a remote shell connection to the VM, allowing the analyst to run commands to inspect running processes, command-line arguments, and parent process details in real time. This is the correct feature for deep forensic investigation of an active IOC on the VM.

Exam trap

The trap here is that candidates confuse Live Response with Vulnerability Assessment or Inventory, thinking those can provide process-level details, but only Live Response offers interactive, real-time forensic access to the VM's operating system.

How to eliminate wrong answers

Option A is wrong because Vulnerability Assessment identifies missing patches and misconfigurations, not real-time process details. Option C is wrong because Inventory of Resources lists VM metadata (name, location, tags) but does not provide live process-level data. Option D is wrong because Secure Score is a compliance and posture metric, not a tool for investigating active threats on a VM.

628
MCQmedium

A security analyst receives an alert in Microsoft Defender XDR indicating a possible credential theft attempt from an external IP. The analyst wants to isolate the affected device immediately while preserving forensic data. What should the analyst do?

A.Use Microsoft Defender for Endpoint to 'contain device' from the device inventory.
B.Disable the user account in Microsoft Entra ID.
C.Initiate a live response session on the device and run the 'isolate device' command.
D.Reset the user's password and enforce sign-out.
AnswerC

Initiating a live response session and running the 'isolate device' command is the correct action because live response gives the analyst a remote shell on the endpoint, enabling collection of volatile evidence (processes, network connections, persistence artifacts) before the environment changes. The 'isolate device' command disconnects the device from the network and blocks inbound and outbound communication except for the connection to the Microsoft Defender for Endpoint service, which keeps management and forensic collection channels open. This combination contains the immediate threat by cutting off the attacker's network access while preserving forensically sound data needed for deeper investigation.

Why this answer

Initiating a live response session and running the 'isolate device' command in Microsoft Defender for Endpoint immediately disconnects the device from the network (both internal and external) while preserving forensic data on the endpoint. This action stops the ongoing credential theft attempt without destroying volatile evidence, which is critical for subsequent investigation.

Exam trap

The trap here is that candidates confuse 'contain device' (which only restricts communication with other managed devices) with full network isolation, leading them to choose Option A instead of the correct live response isolation command.

How to eliminate wrong answers

Option A is wrong because 'contain device' in Microsoft Defender for Endpoint only blocks communication with the device from other managed devices but does not fully isolate it from the network or external IPs, leaving the attack vector open. Option B is wrong because disabling the user account in Microsoft Entra ID prevents further authentication but does not stop the attacker from using an already established session or cached credentials on the device, and it does not preserve forensic data. Option D is wrong because resetting the user's password and enforcing sign-out does not isolate the device; the attacker may still have persistence mechanisms (e.g., scheduled tasks, backdoors) running on the endpoint, and it does not preserve volatile forensic data.

629
MCQhard

Refer to the exhibit. This JSON snippet is from an Azure Web Application Firewall (WAF) policy. What does this rule do?

A.Blocks traffic from the entire 10.0.0.0/24 subnet.
B.Blocks traffic originating from IP address 10.0.0.1.
C.Logs traffic from IP address 10.0.0.1 without blocking.
D.Allows traffic from IP address 10.0.0.1.
AnswerB

The rule's match condition uses RemoteAddr as the source operand, IPMatch as the operator, and the literal value '10.0.0.1', meaning it matches requests whose client IP is exactly 10.0.0.1. The action specified is 'Block', so any request from that source IP is denied. Consequently, it correctly blocks traffic originating from that single IP address.

Why this answer

The JSON snippet defines a WAF rule with a match condition that checks if the client IP address equals 10.0.0.1. The action is set to 'Block', meaning any request from that specific IP address will be denied. Option B correctly identifies this behavior.

Exam trap

The trap here is that candidates often confuse an exact IP match with a subnet match, assuming '10.0.0.1' implies the entire /24 range, or they misread the 'Block' action as 'Allow' or 'Log' due to familiarity with other WAF rule types.

How to eliminate wrong answers

Option A is wrong because the rule uses an exact IP match ('10.0.0.1'), not a CIDR range ('10.0.0.0/24'), so it does not block the entire subnet. Option C is wrong because the action is 'Block', not 'Log' (which would require an action like 'Log' or 'Allow' with logging enabled). Option D is wrong because the action is 'Block', not 'Allow', so traffic from 10.0.0.1 is denied, not permitted.

630
MCQhard

Refer to the exhibit. You are reviewing an analytics rule in Microsoft Sentinel. The rule is enabled but has not generated any alerts in the past 24 hours. What is the most likely cause?

A.The triggerThreshold is set to 0, which means no alerts will be generated
B.Suppression is enabled with a duration of 6 hours, which may be suppressing new alerts after the first one
C.The queryFrequency is 1 hour and the queryPeriod is 7 days, which is a mismatch
D.The query uses 'Location == Unknown' but the actual sign-in location is not 'Unknown'
AnswerD

The filter 'Location == Unknown' makes the rule alert only when the sign-in location is reported as Unknown, which is a data-quality attribute. If the actual sign-in location is, say, 'United States,' the query simply returns no records and the rule remains silent—this is the rule working as designed, not a misconfiguration. If you are expecting an alert for a known-location sign-in, this rule was never meant to cover it; and if unknown-location sign-ins did occur, suppression, not the location filter, would prevent duplicates.

Why this answer

The rule has generated no alerts because the query condition 'Location == Unknown' does not match any actual sign-in locations. Suppression only suppresses alerts after an initial alert has been generated; it does not prevent the first alert. With zero alerts, the most likely cause is that the query returns no results, not suppression.

Exam trap

Be careful: suppression does not stop the first alert from being generated; it only suppresses subsequent matching results for the configured duration. A rule with no alerts in the past 24 hours means the query likely returned no results or the rule isn't running, not that suppression is suppressing everything.

How to eliminate wrong answers

Option A is wrong because the triggerThreshold is set to 0, which in Microsoft Sentinel analytics rules means that an alert is generated for every query result (i.e., no minimum threshold), so alerts would be generated, not suppressed. Option C is wrong because a queryFrequency of 1 hour and a queryPeriod of 7 days is a valid and common configuration for rules that look back over a longer window to detect patterns, and this mismatch does not prevent alerts from being generated. Option D is wrong because the query condition 'Location == Unknown' is a filter that would only match sign-ins where the location is explicitly 'Unknown'; if no sign-ins with that location occurred, the query would return zero results, but this is a data issue, not a rule configuration issue, and the question asks for the most likely cause given the rule is enabled and has not generated alerts.

631
MCQeasy

A security analyst receives an alert from Microsoft Defender for Cloud Apps indicating that a user has signed in from a banned country. The analyst needs to block further access from that country for all users. What should the analyst configure?

A.Modify the device compliance policy in Microsoft Intune.
B.Configure a data loss prevention (DLP) policy in Microsoft Purview.
C.Create an IP range group for the country and configure a session policy to block it.
D.Create a conditional access policy in Microsoft Entra ID to block the country.
AnswerC

In Microsoft Defender for Cloud Apps, the correct approach is to create an IP address group that represents the country in question, using Defender for Cloud Apps' built-in country-based IP classification or by uploading custom ranges. Then, you configure a session policy with an access-control action set to 'Block' and a filter that matches the 'IP group' to the newly created group. When a session policy is active, Defender for Cloud Apps intercepts the session in real time and denies access from that country, providing granular, app-specific enforcement.

Why this answer

Microsoft Defender for Cloud Apps session policies can block access based on IP address geolocation. By creating an IP range group for the banned country and configuring a session policy to block traffic from that group, the analyst can enforce real-time blocking of all user sessions originating from that country, leveraging the reverse proxy architecture of Defender for Cloud Apps.

Exam trap

The trap here is that candidates often confuse the scope of conditional access policies (which block at the authentication level) with the session-level control provided by Defender for Cloud Apps, leading them to select option D instead of C.

How to eliminate wrong answers

Option A is wrong because device compliance policies in Microsoft Intune control device health and configuration (e.g., encryption, jailbreak detection) and cannot block access based on geographic location. Option B is wrong because data loss prevention (DLP) policies in Microsoft Purview are designed to prevent sensitive data from being shared or leaked, not to block sign-ins or sessions based on country of origin. Option D is wrong because while a conditional access policy in Microsoft Entra ID can block access from specific countries, it operates at the authentication level and does not provide the granular session-level control (e.g., monitoring or blocking specific app actions) that Defender for Cloud Apps session policies offer for cloud app usage.

632
MCQmedium

Your SOC team uses Microsoft Sentinel with multiple workspaces across regions. You need to implement a solution that allows analysts to query all workspaces from a single location without moving data. Which feature should you configure?

A.Use cross-workspace queries with workspace() expressions in KQL.
B.Export data to Azure Data Explorer and query there.
C.Create a single Log Analytics workspace and have all data sources send logs there.
D.Configure Azure Lighthouse to manage all workspaces.
AnswerA

The workspace() expression lets a single KQL query reference tables in other Microsoft Sentinel workspaces, returning results without ingesting or replicating data. This satisfies the requirement to query all regional workspaces from one location while leaving data resident in its original region.

Why this answer

Cross-workspace queries using the `workspace()` expression in KQL allow analysts to query multiple Log Analytics workspaces from a single query context without moving or centralizing the data. This is the native Microsoft Sentinel feature designed for multi-workspace environments, enabling seamless querying across regions while keeping data in its original workspace.

Exam trap

The trap here is that candidates often confuse Azure Lighthouse (cross-tenant management) with cross-workspace querying, but Lighthouse does not provide the KQL-level query capability needed to query data across workspaces from a single query.

How to eliminate wrong answers

Option B is wrong because exporting data to Azure Data Explorer requires moving data out of Log Analytics, which contradicts the requirement of querying without moving data, and adds latency and cost for data transfer. Option C is wrong because creating a single Log Analytics workspace would require all data sources to send logs to that one location, which violates the requirement of keeping data in multiple workspaces across regions. Option D is wrong because Azure Lighthouse provides cross-tenant management capabilities but does not enable querying across multiple workspaces from a single KQL query; it only allows managing resources across tenants, not querying data across workspaces.

633
Multi-Selecthard

Which THREE approaches are effective for hunting threats in Microsoft Defender XDR using advanced hunting? (Choose three.)

Select 3 answers
A.Using known indicators of compromise (IOCs) from threat intelligence feeds.
B.Establishing a baseline of normal behavior and hunting for deviations.
C.Reviewing all alerts generated by automated detection rules.
D.Searching for any single event that appears unusual.
E.Applying machine learning models to detect anomalous patterns.
AnswersA, B, E

Using known IOCs such as malicious file hashes, suspicious domains, attacker IPs, and email sender addresses from threat intelligence feeds is effective because it gives the hunt concrete, evidence-backed starting points from both external intelligence and internal incident knowledge. In Microsoft Defender XDR, a hunter can run KQL queries over Advanced Hunting tables (DeviceFileEvents, DeviceNetworkEvents, EmailEvents, etc.) to cross-reference these IOCs and pivot to related processes, users, and machines. This method works best when the hunter expands beyond simple hash matches to hunt for subtle variations that preserve the attacker's underlying tradecraft.

Why this answer

Effective hunting in Microsoft Defender XDR using advanced hunting involves proactive approaches: using known IOCs from threat intelligence (A) helps identify known threats; establishing a baseline of normal behavior and hunting for deviations (B) detects anomalies; applying machine learning models (E) leverages automated anomaly detection. Option C is incorrect because reviewing all alerts is reactive and not a hunting technique. Option D is incorrect because hunting looks for patterns, not isolated unusual events.

634
MCQmedium

A security analyst wants to identify all users who received a phishing email that contained a known malicious URL. The analyst has the URL. Which advanced hunting table should the analyst query first to find the emails that contained this URL?

A.EmailEvents
B.EmailUrlInfo
C.EmailAttachmentInfo
D.EmailPostDeliveryEvents
AnswerB

EmailUrlInfo is the correct table because it is specifically designed to store each URL extracted from an email, along with the corresponding NetworkMessageId. By filtering EmailUrlInfo on the known malicious URL, you obtain the NetworkMessageId(s) of all emails that contained that link, which can then be joined to EmailEvents to retrieve the recipient list. This table is the authoritative source for URL-to-email correlations in Advanced Hunting.

Why this answer

The EmailUrlInfo table in Microsoft Defender XDR contains records of URLs extracted from email messages, including the specific URL and the email's unique identifier (NetworkMessageId). By querying this table for the known malicious URL, the analyst can retrieve the NetworkMessageIds of all emails containing that URL, which can then be joined with the EmailEvents table to identify the recipients. This is the most direct and efficient first step because EmailUrlInfo is purpose-built to map URLs to email messages.

Exam trap

The trap here is that candidates often jump to EmailEvents thinking it contains all email details, but they forget that URL content is stored in a separate table (EmailUrlInfo) and must be queried first to identify the specific emails.

How to eliminate wrong answers

Option A is wrong because EmailEvents contains metadata about email delivery (sender, recipient, subject, delivery action) but does not include the actual URL content; it cannot be queried directly to find emails containing a specific URL. Option C is wrong because EmailAttachmentInfo stores information about email attachments (file names, hashes, sizes) and is used for malware or attachment-based threats, not for identifying URLs within the email body. Option D is wrong because EmailPostDeliveryEvents tracks actions taken on emails after delivery (e.g., user clicks, admin moves, ZAP actions) and does not contain the original URL content from the email.

635
MCQeasy

While threat hunting in Microsoft Sentinel, you want to create a hunting query that identifies all attempts to disable security controls. Which data table would be most appropriate to query for such activity?

A.Syslog
B.SecurityEvent
C.CommonSecurityLog
D.OfficeActivity
AnswerB

SecurityEvent captures Windows security auditing events, including modifications to security settings and attempts to disable controls such as Defender or audit policies. It is the appropriate table for hunting activity that weakens protective mechanisms across monitored machines.

Why this answer

The SecurityEvent table in Microsoft Sentinel contains Windows security events forwarded from agents, including Event ID 4688 (process creation) and events related to disabling security controls such as Windows Defender or audit policies. Threat hunting queries for control-disabling activity typically target SecurityEvent because it captures native Windows security log data. Other tables cover different log sources and would not contain these Windows security events.

Exam trap

The trap is confusing CommonSecurityLog (third-party CEF logs) with SecurityEvent (native Windows security logs); candidates often assume 'security' in the name means it holds all security events.

How to eliminate wrong answers

Option A is wrong because Syslog contains Linux/Unix syslog messages forwarded via the Log Analytics agent, not Windows Security event log entries. Option C is wrong because CommonSecurityLog holds CEF-formatted logs from third-party security appliances (firewalls, IDS/IPS), not native Windows security events. Option D is wrong because OfficeActivity contains Microsoft 365 audit logs (Exchange, SharePoint, Teams), which would not record local Windows security control changes.

636
MCQeasy

Your organization uses Microsoft Defender for Endpoint. You need to ensure that when a high severity alert is generated, an automated investigation is launched immediately. What is the correct configuration?

A.Create a custom indicator in Microsoft Defender for Endpoint.
B.Use advanced hunting to create a custom detection rule.
C.In Microsoft Defender for Endpoint, set up an alert suppression rule.
D.In Microsoft 365 Defender, configure automated investigation and response settings to automatically investigate alerts.
AnswerD

Configuring automated investigation and response in Microsoft 365 Defender directly satisfies the requirement to launch investigations on alerts. AIR settings let you toggle automatic investigation for specific alert severities, so high severity alerts trigger investigations immediately without manual intervention, unlike device groups or custom detections.

Why this answer

Microsoft 365 Defender's automated investigation and response (AIR) capabilities allow you to configure automatic investigation for alerts of specific severity levels. By enabling this setting for high severity alerts, Defender for Endpoint will immediately launch an investigation when such an alert is generated, without requiring manual intervention.

Exam trap

The trap here is that candidates often confuse custom detection rules (advanced hunting) or custom indicators with the ability to trigger automated investigations, when in fact the correct configuration is a simple toggle in the automated investigation and response settings within Microsoft 365 Defender.

How to eliminate wrong answers

Option A is wrong because custom indicators (IOCs) are used to define entities like files, IPs, or domains for detection, alerting, or blocking—they do not control automated investigation launch behavior. Option B is wrong because advanced hunting custom detection rules create custom alerts based on KQL queries, but they do not configure the automatic investigation trigger for existing high severity alerts. Option C is wrong because alert suppression rules are designed to suppress or hide alerts based on criteria, not to initiate automated investigations.

637
MCQmedium

Your organization has Microsoft Defender for Office 365 enabled. Users report that phishing emails are being delivered to their inboxes. You need to improve the filtering. What should you do first?

A.Increase the spam confidence level threshold.
B.Review phishing emails in Threat Explorer and adjust anti-phishing policies.
C.Disable third-party email connectors.
D.Enable the 'Secure by default' setting in Exchange Online.
AnswerB

Threat Explorer in Microsoft 365 Defender provides granular visibility into phishing detections, including message traces, delivery actions, sender/receiver details, and threat types, so you can identify whether legitimate mail was misclassified or real phishing evaded detection. Using that evidence, you can fine-tune anti-phishing policies to apply stronger impersonation protection, spoof intelligence, and mailbox intelligence for affected users and domains. This combines investigation and policy adjustment, which is the correct remediation workflow in Defender for Office 365.

Why this answer

Reviewing the Threat Explorer in Defender for Office 365 allows you to analyze detected phishing emails and understand why they were delivered, then adjust policies accordingly. Option A is wrong because increasing spam confidence level might block legitimate email. Option C is wrong because disabling third-party connectors doesn't help.

Option D is wrong because enabling secure by default is already enabled.

638
MCQhard

In Microsoft 365 Defender advanced hunting, an analyst is investigating a case where a user's device was compromised via a malicious base64-encoded PowerShell script. The analyst wants to find all processes that were created by this script by decoding the command line. Which KQL function should be applied to the ProcessCommandLine column in the DeviceProcessEvents table?

A.base64_decode_tostring(ProcessCommandLine)
B.parse_base64(ProcessCommandLine)
C.decode_base64(ProcessCommandLine)
D.convertstring(ProcessCommandLine, 'base64')
AnswerA

base64_decode_tostring(ProcessCommandLine) is a valid KQL function in Microsoft 365 Defender advanced hunting. It takes a base64-encoded string as its input and returns the decoded plain-text string. In PowerShell obfuscation, attackers frequently encode malicious command lines using base64, so applying this function reveals the actual command that was executed, enabling analysts to inspect the true intent and detect malicious behavior.

Why this answer

The correct KQL function to decode a Base64-encoded string into a readable text format in Microsoft 365 Defender advanced hunting is `base64_decode_tostring()`. This function takes a string column (like ProcessCommandLine) and returns the decoded plaintext, allowing the analyst to see the actual PowerShell commands executed. The other options are either invalid KQL functions or do not exist in the Kusto Query Language used in advanced hunting.

Exam trap

The trap here is that Microsoft tests whether candidates know the exact KQL function name `base64_decode_tostring()` versus common but incorrect variations like `decode_base64()` or `parse_base64()`, which are not part of the Kusto Query Language.

How to eliminate wrong answers

Option B is wrong because `parse_base64()` is not a valid KQL function; the correct function is `base64_decode_tostring()`. Option C is wrong because `decode_base64()` is not a recognized KQL function; Kusto uses `base64_decode_tostring()` for this purpose. Option D is wrong because `convertstring(ProcessCommandLine, 'base64')` is not a valid KQL syntax; the correct function for Base64 decoding is `base64_decode_tostring()`, and `convertstring()` is used for different encoding conversions like UTF-8 or ASCII.

639
MCQeasy

Your SOC uses Microsoft Defender for Office 365. You need to configure a policy that automatically moves malicious email attachments to quarantine before they reach user mailboxes. What should you configure?

A.Create an anti-phishing policy to detect phishing attempts.
B.Create an anti-spam policy with a high confidence spam filter.
C.Create an anti-malware policy in the Microsoft 365 Defender portal.
D.Create a Safe Attachments policy in the Microsoft 365 Defender portal.
AnswerD

A Safe Attachments policy in the Microsoft 365 Defender portal is the correct solution because it is specifically designed to handle email attachments by routing them through a detonation sandbox. When an email has an attachment that matches policy conditions, the attachment is opened in a virtualized environment to observe its behavior, and the verdict (malicious or benign) determines whether the message is delivered or quarantined. Safe Attachments provides zero-day protection against malware that traditional signature-based scanning misses, and it integrates with other Defender for Office 365 features like time-of-click protection. This policy directly addresses the requirement to quarantine malicious attachments.

Why this answer

Safe Attachments is a Microsoft Defender for Office 365 feature specifically designed to detonate email attachments in a virtual sandbox environment before delivery. By creating a Safe Attachments policy in the Microsoft 365 Defender portal, you can automatically quarantine malicious attachments, preventing them from reaching user mailboxes. This directly addresses the requirement to handle malicious attachments, not phishing or spam.

Exam trap

The trap here is that candidates often confuse anti-malware policies (which use static signatures) with Safe Attachments (which uses dynamic sandbox analysis), leading them to select Option C instead of D.

How to eliminate wrong answers

Option A is wrong because anti-phishing policies protect against deceptive email messages designed to steal credentials, not against malicious attachments; they do not perform attachment sandboxing. Option B is wrong because anti-spam policies filter bulk or unwanted email based on content and sender reputation, not on attachment malware analysis; high confidence spam filters do not quarantine attachments. Option C is wrong because while an anti-malware policy can detect known malware via signature-based scanning, it does not provide the advanced sandbox detonation and zero-day protection that Safe Attachments offers; anti-malware policies are more basic and may miss polymorphic threats.

640
MCQmedium

You are responding to an incident where a user's credentials were stolen via a phishing email. The attacker used the credentials to access Microsoft Entra ID and then tried to perform privileged role escalation. Which Microsoft Sentinel solution should you use to detect this type of attack?

A.Network Security Group flow logs
B.Syslog data connector
C.Threat intelligence connectors
D.UEBA (User and Entity Behavior Analytics)
AnswerD

UEBA (User and Entity Behavior Analytics) in Microsoft Sentinel builds individual baselines from historical sign-in patterns, role assignments, and user activities, then applies machine learning to detect anomalies such as unusual privilege escalation or impossible travel. Because it focuses on behavioral deviations rather than static rules, UEBA is specifically designed to surface the kind of account misuse associated with compromised credentials.

Why this answer

UEBA (User and Entity Behavior Analytics) is the correct solution because it uses machine learning to establish baseline behavioral patterns for users and entities, then detects anomalies such as a user logging in from an unusual location and immediately attempting privileged role escalation. This directly identifies the credential theft and privilege escalation chain described in the incident, whereas other options focus on network traffic, generic syslog ingestion, or threat intelligence matching, which would not catch the behavioral anomaly of a stolen credential being used for role escalation.

Exam trap

The trap here is that candidates often confuse UEBA with threat intelligence or network logs, mistakenly thinking that detecting credential theft requires matching known malicious IPs or analyzing raw network traffic, when in fact the attack relies on behavioral anomalies that only UEBA can identify.

How to eliminate wrong answers

Option A is wrong because Network Security Group flow logs capture IP traffic metadata (source/destination, ports, protocols) but do not analyze user authentication behavior or Entra ID role escalation attempts; they are designed for network-level troubleshooting and security group rule monitoring, not identity-based attack detection. Option B is wrong because the Syslog data connector ingests log data from on-premises or third-party devices (e.g., firewalls, Linux servers) in syslog format, but it does not natively parse Microsoft Entra ID audit logs or apply behavioral analytics to detect anomalous role escalation; it is a generic log ingestion pipeline, not a detection solution. Option C is wrong because Threat intelligence connectors ingest indicators of compromise (IOCs) like malicious IPs, domains, or hashes from external feeds, but the attack described uses a legitimate user's stolen credentials from a phishing email—there is no malicious IOC to match against; the detection relies on behavioral deviation, not known threat signatures.

641
MCQeasy

You are performing a threat hunt in Microsoft Sentinel. You want to identify devices that have been communicating with known malicious IP addresses. Which data source should you query?

A.SecurityEvent
B.CommonSecurityLog
C.DnsEvents
D.DeviceNetworkEvents
AnswerB

CommonSecurityLog is the Sentinel table that ingests normalized network traffic logs from firewalls and other security appliances using the Common Event Format (CEF). It records fields like source and destination IP addresses, ports, protocols, and the action taken (allow/deny), making it the go-to table for analyzing inter-host IP communication. For a hunt focused on direct network connections between two systems, this is the appropriate data source.

Why this answer

CommonSecurityLog is the correct data source because it aggregates logs from various security appliances (e.g., firewalls, proxies) using the Syslog or CEF format. These logs typically contain source and destination IP addresses, making them ideal for correlating internal devices with known malicious IPs during a threat hunt. SecurityEvent and DeviceNetworkEvents lack the necessary network-level IP communication data, while DnsEvents only logs DNS queries, not direct IP connections.

Exam trap

The trap here is that candidates often choose DnsEvents thinking DNS logs show all network communications, but they miss that DNS only resolves domain names to IPs and does not log the actual IP connections, which are captured in CommonSecurityLog from firewalls or proxies.

How to eliminate wrong answers

Option A is wrong because SecurityEvent collects Windows security audit logs (e.g., logon events, process creation) and does not include network communication records to external IPs. Option C is wrong because DnsEvents logs DNS query/response data (e.g., domain resolutions) but does not capture direct IP-to-IP communications with malicious addresses. Option D is wrong because DeviceNetworkEvents (from Microsoft Defender for Endpoint) records network connections on endpoints, but the question asks for a data source in Microsoft Sentinel, and CommonSecurityLog is the standard for aggregating firewall/proxy logs that show outbound connections to known bad IPs.

642
MCQmedium

A security analyst is investigating a potential malware outbreak using Microsoft 365 Defender advanced hunting. The analyst wants to find all devices where a file with a specific SHA256 hash was first created and then later deleted, which may indicate a cleanup attempt. Which query pattern on the DeviceFileEvents table is appropriate?

A.DeviceFileEvents | where SHA256 == "<hash>" | summarize Actions = make_set(ActionType) by DeviceId | where Actions has_all ("FileCreated", "FileDeleted")
B.DeviceFileEvents | where SHA256 == "<hash>" and ActionType == "FileDeleted" | project DeviceId
C.DeviceFileEvents | where FileHash == "<hash>" | summarize Actions = make_set(ActionType) by DeviceId | where Actions has "FileCreated"
D.DeviceFileEvents | summarize by DeviceId, ActionType | where ActionType in ("FileCreated", "FileDeleted")
AnswerA

This query correctly identifies devices by first filtering DeviceFileEvents to only rows where SHA256 equals the known malicious hash. The summarize operator then groups by DeviceId and uses make_set(ActionType) to build an array of every file action observed for that file on each device. The subsequent where clause with has_all ensures that both 'FileCreated' and 'FileDeleted' appear in that array, verifying the file was created and later deleted on the same device. This precisely matches the requirement to find devices exhibiting both lifecycle events for the same file hash.

Why this answer

It first filters by the specific SHA256 hash, then uses `make_set(ActionType)` to collect all actions per device, and finally checks that both 'FileCreated' and 'FileDeleted' appear in the set. This precisely identifies devices where the file was both created and later deleted, indicating a potential cleanup attempt.

Exam trap

The trap here is that candidates may confuse the column name `SHA256` with `FileHash` (which does not exist in DeviceFileEvents) or forget to filter by the specific hash before summarizing, leading to false positives from unrelated file operations.

How to eliminate wrong answers

Option B is wrong because it only looks for 'FileDeleted' events, missing the requirement that the file must have been first created on the same device. Option C is wrong because it uses `FileHash` instead of `SHA256` (the correct column name in DeviceFileEvents) and only checks for 'FileCreated', not both actions. Option D is wrong because it summarizes by DeviceId and ActionType without filtering by the specific hash, returning all devices with any create/delete actions rather than those related to the target file.

643
MCQmedium

You are investigating a potential ransomware incident detected by Microsoft Defender XDR. The incident shows multiple machines with suspicious encryption activity. You need to contain the threat immediately. What should you do first?

A.Reset the passwords of all users on the affected machines
B.Run a full antivirus scan on all endpoints
C.Initiate device isolation on affected machines from Microsoft Defender XDR
D.Disable the user accounts associated with the affected machines
AnswerC

Device isolation severs network connectivity while preserving Microsoft Defender XDR communication, immediately halting lateral spread and further encryption across affected endpoints. This containment satisfies the requirement to stop the threat first, before investigation or remediation, and is executed directly from the incident view.

Why this answer

In Microsoft Defender XDR, device isolation is the fastest containment action that stops lateral movement and further encryption while preserving the machine for investigation. Isolating affected devices immediately cuts off network communication except for the Defender connection, preventing ransomware from spreading. This is the recommended first step in the incident response containment phase for active ransomware.

Exam trap

SC-200 often tests the order of incident response actions, tricking candidates into choosing identity-based actions (password reset, disable account) instead of immediate endpoint containment.

How to eliminate wrong answers

Option A is wrong because resetting passwords does not stop active encryption or lateral movement and is a recovery/identity action, not containment. Option B is wrong because a full antivirus scan is a detection/remediation step that takes time and does not immediately stop an ongoing ransomware attack. Option D is wrong because disabling user accounts does not stop malware already running on the machines and may disrupt legitimate response efforts.

644
MCQmedium

An organization uses Microsoft 365 Defender. An automated investigation on a device has determined that a file is malicious and has been blocked. The analyst wants to verify that the file was blocked and see the action taken (e.g., block, allow). Which entity page provides this information?

A.File entity page
B.Device entity page
C.User entity page
D.Email entity page
AnswerA

The File entity page in Microsoft 365 Defender is the correct pivot because it aggregates the detection status and remediation actions taken on a specific file across every device in the organization. It surfaces the SHA-256 hash, prevalence, originating entity, and a timeline of automated or manual response actions such as 'Quarantine file' or 'Block file' invoked by automated investigation. This gives the SOC a single pane of glass to confirm whether the threat was fully contained.

Why this answer

The File entity page in Microsoft Defender XDR provides a centralized view of a file's reputation, detection details, and the specific actions taken (e.g., blocked, allowed, quarantined) during automated investigations. Since the analyst needs to confirm the block action on a specific malicious file, this page directly displays the investigation result and the applied remediation action.

Exam trap

The trap here is that candidates often confuse the Device entity page (which shows that an investigation ran) with the File entity page (which shows the specific action taken on the file), leading them to incorrectly select the Device page.

How to eliminate wrong answers

Option B is wrong because the Device entity page shows device-level alerts, investigations, and software inventory, but does not display the specific action taken on a file (e.g., block vs. allow) — it only indicates that an investigation occurred. Option C is wrong because the User entity page focuses on user-related alerts, sign-in logs, and compromised accounts, not file-level remediation actions. Option D is wrong because the Email entity page is specific to email messages, attachments, and phishing detections within Microsoft Defender for Office 365, not for file actions on endpoints.

645
MCQhard

Your organization uses Microsoft Defender for Cloud to monitor hybrid workloads. You need to ensure that security alerts from on-premises servers running Windows Server 2022 are forwarded to Microsoft Sentinel. The servers are not yet onboarded to Azure Arc. What should you do first?

A.Install the Azure Monitor Agent on the servers.
B.Deploy Azure Policy to enable Defender for Cloud on the servers.
C.Onboard the servers to Azure Arc and enable Defender for Cloud.
D.Install Microsoft Defender for Endpoint on the servers.
AnswerC

Azure Arc enrolment is the prerequisite: it projects the on-premises Windows Server 2022 machines into Azure as connected resources, which Defender for Cloud requires before its agent can stream security alerts into Microsoft Sentinel. Without Arc, the servers remain invisible to the connector.

Why this answer

On-premises servers must first be onboarded to Azure Arc to establish a management identity and connectivity with Azure. Without Azure Arc, Defender for Cloud cannot apply its security policies or forward alerts to Microsoft Sentinel. Enabling Defender for Cloud on the servers after Arc onboarding allows security alerts to be collected and forwarded to Sentinel.

Exam trap

The trap here is that candidates often assume installing an agent (AMA or MDE) is sufficient to forward alerts to Sentinel, but Microsoft requires Azure Arc as the foundational onboarding step to bring non-Azure servers into the Azure management plane before Defender for Cloud can generate and forward security alerts.

How to eliminate wrong answers

Option A is wrong because the Azure Monitor Agent (AMA) can collect telemetry but does not enable Defender for Cloud's security alert generation or forwarding to Sentinel; AMA is a data collection agent, not a prerequisite for Defender for Cloud integration. Option B is wrong because Azure Policy can enforce configurations only on resources already managed by Azure; without Azure Arc, the on-premises servers are not visible to Azure Policy. Option D is wrong because Microsoft Defender for Endpoint (MDE) provides endpoint detection and response but does not, by itself, forward security alerts to Sentinel; MDE integration with Sentinel requires the servers to be onboarded to Azure Arc or have a direct data connector configured.

646
MCQmedium

A SOC analyst needs to create a scheduled analytics rule in Microsoft Sentinel that detects when a user logs in from an IP address that is not in a predefined list of known corporate IP ranges. The list is maintained as a custom Sentinel watchlist and frequently updated. Which KQL function should the analyst use to reference the watchlist within the rule's query?

A.externaldata()
B._GetWatchlist()
C.lookup()
D.invoke()
AnswerB

_GetWatchlist() is the correct, built-in KQL function specifically designed to return the content of a Microsoft Sentinel watchlist by name. For example, _GetWatchlist('IPSAllowlist') returns a table with the watchlist's columns and rows, which you can then join with or filter against other data in the analytics rule query. This function is the native mechanism for operationalizing watchlists in scheduled rules and is preferred over generic operators because it handles the internal watchlist schema automatically.

Why this answer

The _GetWatchlist() function is the correct KQL function to reference a custom Sentinel watchlist within an analytics rule query. It retrieves the watchlist content as a table, allowing the analyst to join or filter login events against the known corporate IP ranges. This function is specifically designed for Sentinel watchlists and supports frequent updates without modifying the rule query.

Exam trap

The trap here is that candidates may confuse _GetWatchlist() with externaldata() or lookup(), thinking they can achieve the same result, but only _GetWatchlist() is designed for Sentinel watchlists and integrates seamlessly with analytics rules.

How to eliminate wrong answers

Option A is wrong because externaldata() is used to query external data sources like Azure Blob Storage or files, not Sentinel watchlists, and requires a direct URI reference. Option C is wrong because lookup() is a KQL operator for joining tables based on a key, but it does not directly retrieve watchlist data; it would require the watchlist to already be in a table format. Option D is wrong because invoke() is used to call a function or a machine learning model, not to access watchlist data, and is not relevant for referencing a watchlist in a query.

647
Multi-Selectmedium

Which TWO of the following are valid methods to initiate a threat hunting session in Microsoft Sentinel?

Select 2 answers
A.Create a custom analytics rule
B.Import a watchlist as a hunting query
C.Start from a specific detection rule
D.Use a predefined hunting query from the Microsoft Sentinel content hub
E.Enable live mode on a hunting query
AnswersC, D

Starting from a detection rule is a valid method because the rule's underlying KQL query exposes the same log data used for detection and can be run interactively in the Logs or Hunting blade to explore broader patterns. For example, you can right-click a rule, select 'Run query' to see its results, then refine the query to look for related activity. This pivot from a deterministic detection to a broader investigation is a recognized hunting entry point in Microsoft Sentinel.

Why this answer

Starting from a specific detection rule and using a predefined hunting query are both valid methods. Live mode is not a feature; custom analytics rules are for detection, not hunting; and watchlists are used for enrichment, not for initiating hunting.

648
MCQeasy

After a security incident, you need to preserve evidence from a compromised Microsoft 365 tenant. What is the best method to preserve data?

A.Take a backup of the entire tenant
B.Use Microsoft Purview eDiscovery to search and export
C.Export the data to a PST file and delete the original
D.Place the user's mailbox and OneDrive on litigation hold
AnswerD

Placing the mailbox and OneDrive on litigation hold preserves all existing and future content immutably, preventing deletion or alteration during investigation, which satisfies the evidence-preservation requirement. This retention mechanism operates independently of the user, unlike simple export or backup copies.

Why this answer

Placing the user's mailbox and OneDrive on litigation hold is the best method for preserving evidence because it preserves all data in its original state, preventing deletion or modification. Option A (backup of entire tenant) is excessive and not immediate. Option B (eDiscovery) is for search and export, not preservation.

Option C (export to PST and delete) destroys the original evidence, which is inadvisable.

649
MCQmedium

Your organization uses Microsoft Sentinel and Microsoft Defender for Cloud Apps to monitor cloud application usage. You have a custom analytics rule that detects multiple failed login attempts from different IP addresses for the same user within 5 minutes. This rule generates an incident. The security team wants to automatically suspend the user in Microsoft Entra ID (formerly Azure AD) when such an incident is created, but only if the user is not a member of the 'Emergency Access' group. You need to implement this automation. You have already created the analytics rule. What should you do next?

A.Modify the analytics rule to include a condition that checks the user's group membership using KQL.
B.Create an automation rule that suspends the user directly using a condition on the incident.
C.Create an automation rule that triggers on incident creation and runs a playbook that suspends the user.
D.Create a playbook that uses the Microsoft Entra ID connector to check if the user is a member of the 'Emergency Access' group. If not, suspend the user. Then create an automation rule that runs this playbook on incident creation.
AnswerD

A playbook performs the conditional group check and suspension, satisfying the requirement to exclude Emergency Access members. The automation rule triggers it on incident creation, since analytics rules alone cannot execute remediation actions or query group membership dynamically.

Why this answer

The requirement has two parts: conditional logic (check Emergency Access group membership) and an action (suspend the user). Playbooks are the only Sentinel component that can run arbitrary logic and call the Microsoft Entra ID connector to both check group membership and disable the account. The automation rule then binds that playbook to incident creation, giving the correct end-to-end flow.

Exam trap

SC-200 often tests the boundary between automation rules (which can only trigger playbooks or set incident metadata) and playbooks (which perform the actual API actions), so candidates wrongly pick an automation rule that 'suspends the user directly'.

How to eliminate wrong answers

Option A is wrong because KQL in an analytics rule can filter which events generate incidents but cannot query Entra ID group membership or perform a remediation action. Option B is wrong because automation rules can trigger playbooks or apply lightweight incident actions (severity, status, tags, assignment) but cannot directly call the Entra ID API to suspend a user. Option C is wrong because it omits the group-membership check, so it would suspend Emergency Access accounts and lock out the tenant.

Option D is correct because it combines the conditional check and the suspend action inside a playbook and wires it to incident creation via an automation rule.

650
MCQmedium

A SOC analyst receives an alert from Microsoft Defender for Cloud Apps indicating that a user downloaded 500 GB of data from SharePoint to an unmanaged device. The user has no history of such behavior. What is the best first step in the incident response process?

A.Run a full antivirus scan on the unmanaged device.
B.Contact the user to verify if the download was intentional.
C.Disable the user account in Microsoft Entra ID.
D.Create a detection rule for similar behavior in Microsoft Sentinel.
AnswerC

Disabling the user account in Microsoft Entra ID is the correct immediate containment action because it sets AccountEnabled to false, blocking the compromised identity from authenticating to Microsoft 365 and Defender services that host the data. This action directly interrupts the active download session and prevents the entity from initiating new requests, regardless of whether the device itself is managed, and it does so quickly enough to limit data loss. As a side benefit, it preserves the unmanaged device's source IP and activity logs for later forensic analysis without giving the attacker a warning.

Why this answer

The immediate priority in an incident response process for a potential data exfiltration scenario is to contain the threat. Disabling the user account in Microsoft Entra ID (formerly Azure AD) is the fastest way to revoke access to SharePoint and other cloud resources, preventing further unauthorized data transfer. This aligns with the 'containment' phase of the NIST incident response lifecycle, before any investigation or remediation steps.

Exam trap

The trap here is that candidates often choose 'Contact the user' (Option B) as a first step, confusing the 'identification' or 'verification' phase with the immediate containment priority required in a potential data exfiltration incident.

How to eliminate wrong answers

Option A is wrong because running a full antivirus scan on the unmanaged device is a remediation step that assumes malware is the cause, but the alert indicates a large download to an unmanaged device, which is a behavioral anomaly; scanning the device does not stop the ongoing exfiltration and may be impossible if the device is not under organizational control. Option B is wrong because contacting the user to verify if the download was intentional introduces a delay and risks tipping off a potential attacker if the account is compromised; the first step must be containment, not verification. Option D is wrong because creating a detection rule in Microsoft Sentinel is a proactive improvement step that should occur after the incident is contained and analyzed, not as the first response to an active alert.

651
MCQmedium

A phishing email was delivered to several users. The analyst wants to find all messages in the campaign, see delivery actions, and perform remediation from the Microsoft 365 Defender portal. Which tool should they use?

A.Threat Explorer.
B.Microsoft Secure Score.
C.Azure Activity log.
D.Microsoft Defender Vulnerability Management software inventory.
AnswerA

Threat Explorer is the primary hunting and investigation console in Microsoft Defender for Office 365 Plan 2, providing near-real-time and historical email records, message delivery status, and threat metadata. It allows an analyst to filter by sender, recipient, message ID, or detection technology to identify which users received a specific phishing message and then perform remediation actions such as soft-deleting the emails or purging malicious URLs. This makes it the correct tool for tracing and remediating an individual phishing campaign.

Why this answer

Threat Explorer (also known as Explorer) in Microsoft 365 Defender is the correct tool because it provides a comprehensive view of email threats, including phishing campaigns. It allows analysts to search for all messages in a campaign, review delivery actions (e.g., blocked, delivered to junk, or delivered), and perform remediation actions such as soft delete, hard delete, or move to quarantine directly from the portal.

Exam trap

The trap here is that candidates may confuse Threat Explorer with the general-purpose Activity log or Secure Score, assuming any security-related tool can handle email threats, but only Threat Explorer is designed for deep email threat hunting and remediation within Microsoft 365 Defender.

How to eliminate wrong answers

Option B is wrong because Microsoft Secure Score is a security posture measurement tool that assesses an organization's security configuration and recommends improvements; it does not provide message-level threat hunting, campaign visibility, or remediation capabilities for phishing emails. Option C is wrong because Azure Activity log records control-plane operations on Azure resources (e.g., creating VMs, modifying RBAC roles) and does not capture email delivery actions or phishing campaign data. Option D is wrong because Microsoft Defender Vulnerability Management software inventory focuses on identifying and managing software vulnerabilities on endpoints, not on email threat analysis or remediation.

652
Multi-Selecthard

Your organization uses Microsoft Defender XDR. You need to delegate incident management tasks to a team of analysts without granting full global admin permissions. Which THREE roles in Microsoft 365 Defender should you assign?

Select 3 answers
A.Security Administrator
B.Security Operator
C.Security Analyst
D.Security Reader
E.Compliance Administrator
AnswersA, B, D

Security Administrator is a privileged Microsoft Entra ID role that grants broad control over security settings in Microsoft 365 Defender, including the ability to modify threat policies, manage role groups, and read/respond to incidents. In Defender XDR, this role can triage, edit, and resolve incidents while also adjusting tenant-wide security configurations, making it a valid choice for the requirement. It goes beyond mere triage by allowing administrative changes to the security posture.

Why this answer

Security Administrator is correct because this role in Microsoft 365 Defender provides full access to incident management features, including the ability to investigate, respond to, and resolve incidents, while not granting full global admin permissions. It allows analysts to manage alerts, perform advanced hunting, and configure security settings within the Defender portal, making it suitable for delegated incident management tasks.

Exam trap

The trap here is that candidates may confuse the non-existent 'Security Analyst' role with the actual 'Security Operator' role, or incorrectly assume that 'Compliance Administrator' includes incident management permissions due to overlapping security and compliance concepts.

653
MCQhard

You are a SOC analyst at Contoso. The environment includes Microsoft Sentinel in a single workspace, Microsoft Defender XDR (including Defender for Endpoint, Defender for Office 365, Defender for Identity, and Defender for Cloud Apps), Microsoft Entra ID, and Microsoft Intune. You need to design a solution to automatically triage and respond to phishing incidents detected by Defender for Office 365. The requirements are: 1) When a phishing alert is generated with high confidence, an incident should be automatically created in Sentinel. 2) The incident should be assigned to the 'Phishing' team and have a severity of High. 3) A playbook should run that will send a Teams message to the Phishing team and also block the sender in Exchange Online. 4) The incident should be automatically closed if the playbook successfully executes. What should you do?

A.Use the Office 365 connector to ingest alerts, then create an analytics rule to generate incidents, and use automation rules to assign and run playbooks.
B.Enable the Microsoft 365 Defender connector to synchronize incidents, create an automation rule triggered on incident creation with conditions for 'Phishing' and high confidence, assigning to 'Phishing' team, running a playbook, and enabling auto-closure.
C.Use a Logic App to continuously poll Defender for Office 365 APIs for alerts, create incidents via the Sentinel API, and assign them.
D.Create a custom analytics rule with KQL to detect phishing in Defender for Office 365 logs, generate incidents, and use automation rules.
AnswerB

This is the recommended approach because the Microsoft 365 Defender connector synchronizes existing Defender for Office 365 incidents into Microsoft Sentinel as incidents. An automation rule can be configured to trigger on incident creation, with conditions for 'Phishing' and 'High' confidence, which assigns the incident to the Phishing team and runs a playbook for automated investigation. Enabling auto-closure ensures that incidents resolved in Defender are automatically closed in Sentinel, maintaining end-to-end fidelity.

Why this answer

It leverages the Microsoft 365 Defender connector to synchronize incidents from Defender for Office 365 into Microsoft Sentinel, which is the recommended approach for ingesting high-confidence phishing alerts. An automation rule triggered on incident creation with conditions for 'Phishing' and high confidence can assign the incident to the 'Phishing' team, run a playbook to send a Teams message and block the sender in Exchange Online, and enable auto-closure upon successful playbook execution.

Exam trap

The trap here is that candidates often confuse the Office 365 connector (which ingests raw alerts) with the Microsoft 365 Defender connector (which synchronizes incidents), leading them to choose Option A, which requires an extra analytics rule and does not natively support high-confidence phishing incident synchronization.

How to eliminate wrong answers

Option A is wrong because the Office 365 connector ingests raw alerts, not incidents, and requires an analytics rule to generate incidents, which adds unnecessary complexity and does not directly synchronize Defender for Office 365 incidents with high-confidence phishing detection. Option C is wrong because using a Logic App to continuously poll Defender for Office 365 APIs is inefficient, introduces latency, and bypasses the native incident synchronization provided by the Microsoft 365 Defender connector, which is the designed pattern for automated triage. Option D is wrong because creating a custom analytics rule with KQL to detect phishing in Defender for Office 365 logs is redundant and error-prone, as Defender for Office 365 already generates high-confidence phishing alerts that should be synchronized as incidents via the Microsoft 365 Defender connector, not re-detected through log queries.

654
MCQmedium

Your organization uses Microsoft Sentinel and has deployed multiple analytics rules. You need to evaluate the effectiveness of these rules by identifying which rules generate the most incidents and have the highest false positive rate. What should you use?

A.Incidents view in Microsoft Sentinel filtered by analytics rule
B.Hunting view in Microsoft Sentinel
C.MITRE ATT&CK view in Microsoft Sentinel
D.Entity behavior analytics view in Microsoft Sentinel
AnswerA

The Incidents view in Microsoft Sentinel is the dedicated operational workspace where alerts are grouped into incidents and linked back to their originating analytics rule. By filtering on a specific rule, you can directly see how many incidents that rule generated, their current status (new, in progress, resolved), and the classification assigned during triage, such as true positive, false positive, or benign positive. This is the authoritative place to review rule effectiveness because it reflects real detection outcomes and allows analysts to take corrective action on noisy or high-fidelity rules.

Why this answer

The Incidents view in Microsoft Sentinel allows you to filter incidents by analytics rule, enabling you to see the count of incidents generated per rule and assess their effectiveness. By reviewing the incident details, you can identify which rules produce the most incidents and, by analyzing the closed or resolved incidents, determine the false positive rate. This directly addresses the requirement to evaluate rule effectiveness based on incident volume and false positives.

Exam trap

The trap here is that candidates may confuse the Hunting view (used for proactive searches) with the Incidents view (used for post-detection analysis), or assume the MITRE ATT&CK view provides rule-level performance metrics when it only maps incidents to attack techniques.

How to eliminate wrong answers

Option B is wrong because the Hunting view is designed for proactive threat hunting using KQL queries to find suspicious activity, not for retrospective analysis of incident generation or false positive rates from analytics rules. Option C is wrong because the MITRE ATT&CK view maps incidents to MITRE techniques but does not provide a breakdown of incident counts or false positive rates per analytics rule. Option D is wrong because Entity behavior analytics view focuses on user and entity behavior anomalies (UEBA) to detect compromised entities, not on evaluating the performance of analytics rules in terms of incident volume or false positives.

655
MCQmedium

A security analyst is investigating an incident in Microsoft 365 Defender where a user's device is suspected to be compromised. The analyst wants to collect a copy of a specific suspicious file from the device for offline analysis without disrupting the user. Which action should the analyst initiate?

A.Initiate a Live Response session
B.Isolate the device from the network
C.Initiate an automated investigation
D.Run a full antivirus scan
AnswerA

Live Response is a Microsoft Defender for Endpoint capability that opens an authenticated, remote command-line shell to the device. Using commands like 'collectfile' or 'getfile', an analyst can retrieve a specific file copy without changing the system state or interrupting the user's session, making it ideal for preserving evidence and performing focused file collection.

Why this answer

A Live Response session allows the analyst to remotely connect to the device in real time, collect a specific suspicious file via commands like 'getfile', and download it for offline analysis without interrupting the user's workflow. This is the only action that provides targeted file collection while the device remains operational.

Exam trap

The trap here is that candidates confuse 'Live Response' with 'isolation' or 'automated investigation', thinking that any remediation action can collect files, but only Live Response provides the granular, non-disruptive file collection capability required for offline analysis.

How to eliminate wrong answers

Option B is wrong because isolating the device from the network disconnects it from all network communications, which disrupts the user and prevents file collection without additional steps. Option C is wrong because an automated investigation runs predefined playbooks to detect and remediate threats, but it does not allow the analyst to manually collect a specific file for offline analysis. Option D is wrong because a full antivirus scan scans for malware and may delete or quarantine the file, but it does not provide a copy of the file for offline analysis and can disrupt the user by consuming system resources.

656
MCQeasy

Your organization uses Microsoft Sentinel. You need to automatically assign incidents to the appropriate SOC tier based on severity. What should you create?

A.A data connector to Microsoft Teams
B.A scheduled analytics rule
C.A playbook in Microsoft Power Automate
D.An automation rule with an owner assignment action
AnswerD

Automation rules in Microsoft Sentinel trigger on incident creation and can execute an owner assignment action, setting the incident's owner to the relevant SOC tier. This directly satisfies the requirement to assign incidents automatically based on severity, using the severity condition within the rule's trigger criteria.

Why this answer

Automation rules in Microsoft Sentinel allow you to automatically assign incidents to specific owners based on conditions like severity, using the 'Assign owner' action. This directly meets the requirement to route incidents to the appropriate SOC tier without manual intervention, leveraging Sentinel's native incident management capabilities.

Exam trap

The trap here is that candidates often confuse automation rules with playbooks, assuming that any automated response requires a playbook, when in fact simple owner assignment is a native automation rule action that does not need a separate playbook or Power Automate workflow.

How to eliminate wrong answers

Option A is wrong because a data connector to Microsoft Teams is used to ingest collaboration data (e.g., chat logs) into Sentinel for analysis, not to automate incident assignment based on severity. Option B is wrong because a scheduled analytics rule generates alerts from log data based on a query schedule, but it does not perform post-incident actions like owner assignment; it only creates incidents or alerts. Option C is wrong because a playbook in Microsoft Power Automate (or Azure Logic Apps) can automate response actions, but it is typically triggered by an automation rule or analytics rule, not directly used for initial owner assignment; the native 'Assign owner' action in automation rules is the correct, simpler method for this specific requirement.

657
MCQeasy

Your organization uses Microsoft Sentinel and you have a playbook that sends an email notification when a high-severity incident is created. You want to ensure that the playbook only runs for incidents that are not already assigned to a user. What should you configure?

A.Set the playbook trigger to 'When an incident is created' and add a condition inside
B.Add a condition in the playbook to check if the incident is assigned
C.Configure the automation rule trigger to include a condition for 'Incident owner equals null'
D.Modify the analytics rule to only generate unassigned incidents
AnswerC

This is the correct approach because Microsoft Sentinel automation rules can be configured with trigger conditions based on incident properties, including the Incident owner field. By setting a condition such as 'Incident owner equals null', the automation rule will only execute when the incident is unassigned, ensuring that any associated playbook runs only for those incidents. This leverages Sentinel's native conditional logic, avoids unnecessary playbook executions, and is the recommended pattern for automating responses based on incident ownership status.

Why this answer

Automation rules in Microsoft Sentinel can include conditions that filter which incidents trigger a playbook. By configuring the automation rule with a condition for 'Incident owner equals null', the playbook will only run for incidents that are unassigned, ensuring that already assigned incidents are not processed. This approach is efficient and avoids unnecessary execution of the playbook.

Exam trap

The trap here is that candidates may think a condition inside the playbook is sufficient, but Microsoft Sentinel automation rules are designed to filter incidents before triggering the playbook, making the automation rule condition the correct and more efficient choice.

How to eliminate wrong answers

Option A is wrong because setting the playbook trigger to 'When an incident is created' and adding a condition inside the playbook would still cause the playbook to be triggered for every incident, including assigned ones, leading to unnecessary runs and potential performance issues; the condition should be applied at the automation rule level to filter before triggering. Option B is wrong because adding a condition inside the playbook to check if the incident is assigned does not prevent the playbook from being triggered for all incidents, which wastes resources and may cause unwanted email notifications for assigned incidents. Option D is wrong because modifying the analytics rule to only generate unassigned incidents is not feasible; analytics rules generate incidents based on detection logic, not assignment status, and assignment is a post-creation action.

658
Multi-Selecthard

Which THREE permissions are required for a user to manage Microsoft Sentinel playbooks using Azure Logic Apps? (Choose three.)

Select 3 answers
A.Microsoft Sentinel Contributor
B.Log Analytics Contributor
C.Global Administrator in Microsoft Entra ID
D.Reader on the Logic App
E.Contributor on the resource group containing the Logic App
AnswersA, B, E

Microsoft Sentinel Contributor is the primary role required to interact with Sentinel playbooks through the portal, APIs, or automation rules. It grants the ability to read and trigger playbooks, as well as view and manage Sentinel incidents and analytics rules. Without this role, the user would not be able to attach playbooks to detections or manually run them from the Sentinel interface, even if they have access to the underlying Logic App.

Why this answer

Microsoft Sentinel Contributor is required because it grants the necessary permissions to create, update, and delete playbooks within Microsoft Sentinel, which are built on Azure Logic Apps. This role allows the user to manage playbooks as part of the security operations environment, including assigning playbooks to automation rules and incident triggers.

Exam trap

The trap here is that candidates often assume Global Administrator is needed for any automation in Sentinel, but Microsoft specifically scopes playbook management to resource group-level Contributor roles to enforce least privilege and avoid granting tenant-wide admin rights.

659
MCQmedium

Your organization has recently deployed Microsoft Sentinel and wants to ensure that all critical Azure resources are monitored for security misconfigurations. You have already enabled Microsoft Defender for Cloud on all subscriptions. You need to configure a solution that will automatically create a Sentinel incident whenever a new security recommendation with severity 'High' is generated in Defender for Cloud. The incident should be assigned to the 'Infrastructure' team. Additionally, you want to run a playbook that will open a ticket in your IT Service Management (ITSM) tool. What should you do?

A.Use the Azure Activity connector to ingest recommendations, then create an analytics rule to generate incidents.
B.Enable the Defender for Cloud connector and create a workbook to monitor recommendations.
C.Create a custom analytics rule that queries the SecurityRecommendation table in the Log Analytics workspace.
D.Enable the Defender for Cloud connector, then create an automation rule that triggers on incident creation from the connector, assigns to 'Infrastructure', and runs a playbook.
AnswerD

Enabling the Defender for Cloud connector is the prerequisite to bring security recommendations and leading alerts into Sentinel as incidents through its built-in analytics rule. A subsequent automation rule that triggers when an incident is created can be configured to assign the incident to the Infrastructure team (using a specific owner or group) and run a playbook to automate the recommended remediation. This design fully satisfies the requirement: data is ingested, incidents are generated, and an automated response is applied based on the recommendation.

Why this answer

The Defender for Cloud connector in Microsoft Sentinel ingests security recommendations and alerts as incidents. By creating an automation rule that triggers on incident creation from this connector, you can automatically assign incidents to the 'Infrastructure' team and run a playbook to open a ticket in your ITSM tool, fulfilling all requirements without custom queries or workbooks.

Exam trap

The trap here is that candidates often think they need to write a custom analytics rule (Option C) or use the Azure Activity connector (Option A) to ingest Defender for Cloud data, when in fact the Defender for Cloud connector already provides incident creation and automation rules handle assignment and playbook execution natively.

How to eliminate wrong answers

Option A is wrong because the Azure Activity connector ingests operational logs (e.g., resource creation/deletion), not security recommendations from Defender for Cloud; it cannot generate incidents from recommendations. Option B is wrong because enabling the Defender for Cloud connector and creating a workbook only visualizes data—it does not automatically generate incidents or trigger playbooks. Option C is wrong because while the SecurityRecommendation table exists, creating a custom analytics rule to query it is unnecessary and less efficient; the Defender for Cloud connector already ingests these recommendations as incidents, and automation rules provide the required assignment and playbook execution without custom KQL.

660
Multi-Selecthard

Which THREE of the following are key considerations when designing a threat hunting program in Microsoft Defender XDR and Microsoft Sentinel? (Choose THREE.)

Select 3 answers
A.Understanding the data schema and available tables in the advanced hunting schema
B.Operational security (OpSec) to avoid tipping off adversaries during manual hunting
C.Implementing multi-factor authentication for all users
D.Using only built-in detection rules to identify threats
E.Data retention policies for logs in Microsoft Sentinel and Microsoft Defender XDR
AnswersA, B, E

A thorough understanding of the advanced hunting schema—including table names, column structure, and relationships—is essential for writing accurate and efficient KQL queries. Hunters must know, for example, that DeviceProcessEvents contains process creation data while IdentityLogonEvents holds authentication logs, and how to join these tables to trace lateral movement. Without this schema knowledge, analysts risk querying irrelevant tables, misinterpreting data, or missing critical evidence hidden in less obvious tables.

Why this answer

Option A is correct because effective threat hunting in Microsoft Defender XDR and Microsoft Sentinel requires knowing the advanced hunting schema — the exact table names (e.g., DeviceProcessEvents, DeviceNetworkEvents, EmailEvents, SigninLogs) and column/field types — so hunters can write precise KQL queries that surface relevant telemetry rather than guessing at data locations. Option B is correct because operational security (OpSec) matters during manual hunting: hunters must avoid actions that tip off adversaries, such as querying or interacting with compromised hosts in ways that generate detectable artifacts, since adversaries may monitor for reconnaissance and change their tactics, techniques, and procedures (TTPs) or go dormant. Option E is correct because data retention policies directly bound what a hunting program can investigate — Microsoft Sentinel's analytics and hunting queries can only search data within the configured retention period (interactive retention plus long-term retention tiers), and Defender XDR's advanced hunting is limited to its own retention window (typically 30 days), so retention must be planned to support historical hunting and incident reconstruction.

Option C is not correct here because, while MFA is a critical identity security control, it is a general security hardening measure rather than a specific design consideration for a threat hunting program. Option D is not correct because relying only on built-in detection rules contradicts the purpose of threat hunting, which is proactive, hypothesis-driven investigation beyond automated detections; hunters use custom KQL queries, not just out-of-the-box rules.

Exam trap

The trap is selecting general security controls like MFA as part of threat hunting design. Candidates must distinguish between foundational security hygiene and specific threat hunting program considerations.

661
MCQmedium

While hunting in Microsoft Sentinel, you find a KQL query that uses the `evaluate` operator with `bag_unpack` to expand JSON properties. The query runs slowly and times out. What is the best practice to optimize this query?

A.Increase the cluster's concurrency and nodes.
B.Remove the `evaluate` operator and use `extend` with `parse_json`.
C.Add a `where` clause to filter rows before applying `bag_unpack`.
D.Use the `materialize` function to cache the entire table before expansion.
AnswerC

Placing a `where` clause before `bag_unpack` reduces the number of rows entering the expansion, which is the most direct way to cut the CPU and memory cost of unpacking. Filtering on a non-computed column (or an indexed field) lets the engine prune data early, so `bag_unpack` operates on a minimal logical set and the query's overall runtime drops substantially.

Why this answer

The best practice for optimizing KQL queries that use bag_unpack is to filter rows with a where clause before applying the expansion. bag_unpack is expensive because it dynamically expands JSON properties into columns, so reducing the row set first minimizes the work. This is the correct optimization because it addresses the root cause: processing too many rows through an expensive operator.

Exam trap

SC-200 often tests the principle of filtering before expensive operators — candidates incorrectly choose scaling or materialize instead of reducing input rows before bag_unpack.

How to eliminate wrong answers

Option A is wrong because increasing cluster concurrency and nodes is a scaling action, not a query optimization; it may mask inefficiency but does not fix the query. Option B is wrong because replacing evaluate bag_unpack with extend parse_json is not equivalent — parse_json alone does not expand JSON into columns and may not improve performance. Option D is wrong because materialize caches intermediate results but does not reduce the cost of expanding a large table; it can even increase memory usage.

662
MCQmedium

A security administrator is configuring Microsoft Defender for Cloud's regulatory compliance dashboard. The organization needs to be compliant with the NIST SP 800-53 standard. Which built-in initiative should the administrator assign to the subscription to populate the dashboard with NIST controls?

A.Azure Security Benchmark
B.NIST SP 800-53 R5
C.CIS Microsoft Azure Foundations Benchmark
D.ISO 27001
AnswerB

NIST SP 800-53 R5 is a built-in compliance initiative within Microsoft Defender for Cloud that automatically assesses Azure resources against the National Institute of Standards and Technology's Special Publication 800-53 Revision 5 controls. This initiative maps Azure Policy definitions to NIST control families such as access control, audit, and risk assessment, providing a compliance score in the regulatory compliance dashboard. When a regulatory requirement calls for NIST SP 800-53, this is the correct built-in standard to enable.

Why this answer

The NIST SP 800-53 R5 built-in initiative is the correct choice because Microsoft Defender for Cloud includes a dedicated regulatory compliance policy initiative that maps directly to the NIST SP 800-53 standard's controls. Assigning this initiative to the subscription populates the regulatory compliance dashboard with the specific NIST controls and their compliance status, enabling the organization to track and report against that framework.

Exam trap

The trap here is that candidates often confuse the Azure Security Benchmark (a Microsoft best-practice framework) with a regulatory standard, assuming it covers NIST controls, when in fact it is a separate initiative that does not map to NIST SP 800-53.

How to eliminate wrong answers

Option A is wrong because the Azure Security Benchmark is a Microsoft-authored set of best practices for securing Azure workloads, not a regulatory standard like NIST SP 800-53, and it does not map to NIST controls. Option C is wrong because the CIS Microsoft Azure Foundations Benchmark is a community-driven benchmark for Azure configuration, not a NIST-specific standard, and its controls are unrelated to NIST SP 800-53. Option D is wrong because ISO 27001 is a separate international security standard with its own control set, and its built-in initiative would populate the dashboard with ISO controls, not NIST SP 800-53 controls.

663
MCQhard

A security analyst is using advanced hunting in Microsoft 365 Defender to detect lateral movement. The analyst wants to find all devices where a specific user account had an interactive logon, and then identify which of those devices subsequently initiated outbound Remote Desktop Protocol (RDP) connections to other internal IP addresses. Which KQL approach is most efficient for this investigation?

A.Use DeviceLogonEvents and DeviceNetworkEvents with a join on DeviceId and a time range
B.Use IdentityLogonEvents and DeviceNetworkEvents with a join on IP address
C.Use DeviceProcessEvents and DeviceNetworkEvents with a join on DeviceId
D.Use EmailEvents and DeviceLogonEvents with a join on RecipientEmail
AnswerA

DeviceLogonEvents records successful interactive and remote logons to a machine, including the target DeviceId, the authenticating account, and the source device/IP. DeviceNetworkEvents logs outbound connection attempts from that same device, with destination IP and port. By joining on DeviceId and filtering to the short time window after the logon record—especially while looking for destination port 3389 or other RDP ports—you can link the account that just logged on to an immediate outbound RDP connection from that device to another host, which is a classic lateral-movement indicator.

Why this answer

It uses DeviceLogonEvents to identify interactive logons for the specific user account on devices, then joins those results with DeviceNetworkEvents on DeviceId within a time range to find subsequent outbound RDP connections (destination port 3389) to internal IPs. This approach directly correlates the user's logon activity with network connections from the same device, which is the most efficient and precise method for detecting lateral movement via RDP.

Exam trap

The trap here is that candidates may confuse IdentityLogonEvents (cloud identity) with DeviceLogonEvents (device-level logon), leading them to choose Option B, but the correct approach requires device-specific logon data to correlate with network events on the same device.

How to eliminate wrong answers

Option B is wrong because IdentityLogonEvents captures cloud identity logons (e.g., Azure AD) rather than device-level interactive logons, and joining on IP address is unreliable due to NAT and shared IPs, making it ineffective for correlating a specific device's network activity. Option C is wrong because DeviceProcessEvents tracks process creation events, not interactive logons; while it could indirectly indicate logon activity, it is less direct and less efficient than using DeviceLogonEvents for the specific user account. Option D is wrong because EmailEvents deals with email delivery and recipient data, which is irrelevant to device logons or RDP network connections; joining on RecipientEmail has no bearing on lateral movement detection.

664
MCQmedium

Refer to the exhibit. An analyst runs Get-MpThreat on a device. Based on the output, what is the status of the threat?

A.The threat executed and is now inactive.
B.The threat was quarantined and is still active.
C.The threat is currently active on the device.
D.The threat was blocked and did not execute.
AnswerD

This is the correct conclusion because the Get-MpThreat output shows both DidThreatExecute is False and IsActive is False. DidThreatExecute=False confirms that the threat did not run, while IsActive=False confirms it is not currently present or running, which aligns with a blocked state. In Microsoft Defender, a threat that was blocked before execution typically has these exact field values, indicating the attack was prevented.

Why this answer

The output of Get-MpThreat shows the threat's state as 'Blocked' and its execution status as 'Not Executed'. This indicates that Microsoft Defender Antivirus successfully prevented the threat from running on the device. Therefore, the threat was blocked and did not execute, making D the correct answer.

Exam trap

The trap here is that candidates often confuse 'Blocked' with 'Quarantined' or assume any threat listed must have executed, but the 'ExecutionStatus' field explicitly clarifies whether the threat ran or was stopped pre-execution.

How to eliminate wrong answers

Option A is wrong because the threat's execution status is 'Not Executed', meaning it did not execute and become inactive. Option B is wrong because the threat was not quarantined; its state is 'Blocked', and it is not active. Option C is wrong because the threat is not currently active; it was blocked before execution.

665
MCQeasy

Refer to the exhibit. You have a Microsoft Sentinel playbook created as shown. When you test the playbook manually, it sends an email successfully. However, when an incident triggers the playbook via an automation rule, the email is not sent. What is the most likely cause?

A.The playbook does not have permission to read incidents.
B.The playbook uses an HTTP trigger instead of a Microsoft Sentinel trigger.
C.The email action is not configured correctly.
D.The Office 365 connection is not authorized.
AnswerB

Microsoft Sentinel automation rules can only invoke Logic Apps that start with a Microsoft Sentinel trigger—either the 'Microsoft Sentinel Incident' trigger or the 'Microsoft Sentinel Alert' trigger—because those triggers receive the incident/alert payload and register the playbook as a Sentinel playbook. The exhibit shows an HTTP trigger ('When a HTTP request is received'), which is a generic Logic Apps trigger; although it can be tested manually by sending an HTTP POST to the endpoint, it is not registered with Microsoft Sentinel as a playbook and therefore is not available for selection in an automation rule. Replacing the HTTP trigger with a Microsoft Sentinel Incident trigger would make the playbook eligible for automation-rule use.

Why this answer

The exhibit shows a playbook that begins with an HTTP trigger, not a Microsoft Sentinel trigger. When an incident triggers the playbook via an automation rule, Sentinel expects the playbook to start with a Microsoft Sentinel trigger (e.g., 'When a response to a Microsoft Sentinel incident is triggered'). An HTTP trigger requires an external HTTP request to start the playbook, which the automation rule does not provide, so the playbook never executes the email action.

Exam trap

The trap here is that candidates assume any playbook can be triggered by an automation rule, overlooking that the playbook must use the dedicated Microsoft Sentinel trigger connector, not a generic HTTP trigger.

How to eliminate wrong answers

Option A is wrong because the playbook successfully sends an email when tested manually, indicating it has sufficient permissions to read incidents; the issue is the trigger type, not permissions. Option C is wrong because the email action works correctly during manual testing, so the configuration is not the problem. Option D is wrong because the Office 365 connection is authorized and functional, as proven by the successful manual test.

666
MCQhard

You are a security operations analyst at a company that uses Microsoft Defender XDR and Microsoft Sentinel. You have configured a custom detection rule in Microsoft Defender XDR that uses a KQL query to detect suspicious PowerShell activity. The rule triggers an alert, but you want to automatically create an incident in Microsoft Sentinel and run a playbook that isolates the affected device. You have already set up the Microsoft Defender XDR connector in Sentinel and enabled incident creation from Defender XDR alerts. However, the playbook does not run automatically when a Defender XDR incident is created. You have verified that the playbook is properly configured and has the correct permissions. What should you do?

A.Create an automation rule in Microsoft Defender XDR to run the playbook.
B.Create an automation rule in Microsoft Sentinel that triggers on incident creation and runs the playbook.
C.Modify the Microsoft Defender XDR data connector in Sentinel to enable playbook execution.
D.Modify the custom detection rule in Defender XDR to include a 'run playbook' action.
AnswerB

Microsoft Sentinel's automation rules provide the exact trigger mechanism needed here: you define a rule that fires on incident creation and set an action to run the specified Azure Logic Apps playbook. When Sentinel ingests Defender incidents via the Microsoft Defender XDR connector, the automation rule evaluates the incident creation event and invokes the playbook with the relevant incident data. This is the supported, intended pattern for automating playbook execution when an incident is created in Sentinel, making this option correct.

Why this answer

In Microsoft Sentinel, automation rules are the mechanism to trigger playbooks automatically when incidents are created or updated. Since the Defender XDR connector is already enabled and creating incidents in Sentinel, the missing piece is an automation rule in Sentinel that runs the playbook on incident creation. The playbook itself is properly configured, so the automation rule bridges the gap between incident creation and playbook execution.

Exam trap

The trap here is that candidates may assume playbooks can be triggered directly from Defender XDR or via the connector settings, but Sentinel automation rules are the only way to automatically run a playbook when a Defender XDR incident is created in Sentinel.

How to eliminate wrong answers

Option A is wrong because Microsoft Defender XDR does not support automation rules to run playbooks; playbook execution is managed within Microsoft Sentinel. Option C is wrong because the Defender XDR data connector in Sentinel does not have a setting to enable playbook execution; its role is to ingest alerts and create incidents, not to trigger playbooks. Option D is wrong because custom detection rules in Defender XDR cannot include a 'run playbook' action; playbooks are a Sentinel concept and must be triggered via Sentinel automation rules.

667
MCQhard

Your SOC team uses Microsoft Sentinel and Microsoft Defender XDR. You have configured automated responses using playbooks. However, some playbooks fail to execute when triggered from Microsoft Defender XDR incidents. You need to ensure that the playbooks run successfully. What should you verify?

A.Confirm that the playbook is stored in the same resource group as Microsoft Sentinel.
B.Verify that the playbook is connected to Microsoft Teams for approval.
C.Ensure that the automation rule that triggers the playbook has the correct 'incident provider' set to 'Microsoft Defender XDR'.
D.Check that the service principal has global administrator role in Microsoft Entra ID.
AnswerC

The 'incident provider' condition in an automation rule filters which incidents can trigger the playbook. Incidents created from Microsoft Defender XDR alerts have their provider set to 'Microsoft Defender XDR', so the rule must explicitly include this provider in its condition; otherwise, the rule will silently skip those incidents. This setting is the most likely cause when Defender XDR incidents do not trigger the playbook while other incident providers, such as 'Azure Security Center' or 'Microsoft Sentinel', still work.

Why this answer

Microsoft Defender XDR incidents that are synchronized to Microsoft Sentinel include an 'incident provider' property. Automation rules in Sentinel must have the 'incident provider' set to 'Microsoft Defender XDR' to trigger playbooks specifically for those incidents. If this property is not configured correctly, the automation rule will not match the incoming incidents, causing the playbook to fail to execute.

Exam trap

The trap here is that candidates often assume playbook failures are due to permissions or resource location, but the SC-200 exam specifically tests the understanding that automation rules require the correct 'incident provider' filter to match incidents from Microsoft Defender XDR.

How to eliminate wrong answers

Option A is wrong because playbooks are Azure Logic Apps resources that can reside in any resource group; they do not need to be in the same resource group as Microsoft Sentinel. Option B is wrong because Microsoft Teams integration is not a prerequisite for playbook execution; it is an optional action within a playbook for manual approval steps. Option D is wrong because the service principal used for playbook authentication requires only the 'Microsoft Sentinel Contributor' role on the relevant resource group or subscription, not the global administrator role in Microsoft Entra ID.

668
MCQhard

A threat hunter is analyzing a potential advanced persistent threat (APT) that uses living-off-the-land binaries (LOLBins) like certutil.exe to download payloads. The hunter wants to find instances where certutil.exe was used to download files from the internet in the last week. Which KQL query in Microsoft Sentinel would be most effective?

A.DeviceProcessEvents | where TimeGenerated > ago(7d) | where FileName == "powershell.exe" | where ProcessCommandLine contains "-enc" | project Timestamp, DeviceName, ProcessCommandLine
B.DeviceProcessEvents | where TimeGenerated > ago(7d) | where FileName == "mshta.exe" | where ProcessCommandLine contains "http" | project Timestamp, DeviceName, ProcessCommandLine
C.DeviceProcessEvents | where TimeGenerated > ago(7d) | where FileName == "certutil.exe" | where ProcessCommandLine contains "-urlcache" or ProcessCommandLine contains "-split" | project Timestamp, DeviceName, ProcessCommandLine
D.DeviceProcessEvents | where TimeGenerated > ago(7d) | where FileName == "wscript.exe" | where ProcessCommandLine contains "http" | project Timestamp, DeviceName, ProcessCommandLine
AnswerC

DeviceProcessEvents captures process creation telemetry from Defender for Endpoint, so filtering FileName for certutil.exe and ProcessCommandLine for the -urlcache or -split switches isolates exactly the LOLBin download behaviour the hunter hypothesised, within the required seven-day window.

Why this answer

The query in option C correctly targets certutil.exe and filters for the specific command-line arguments '-urlcache' and '-split', which are commonly used by attackers to download files from the internet. This directly addresses the threat hunter's goal of finding certutil.exe download activity. The other options focus on different LOLBins (powershell.exe, mshta.exe, wscript.exe) that are not mentioned in the scenario.

Exam trap

SC-200 often tests the ability to distinguish between different LOLBins and their command-line arguments. Candidates might pick a query for a different LOLBin due to familiarity, but the question specifically mentions certutil.exe.

How to eliminate wrong answers

Option A is wrong because it looks for powershell.exe with encoded commands, not certutil.exe downloads. Option B is wrong because it targets mshta.exe, another LOLBin, but not the one specified. Option D is wrong because it targets wscript.exe, which is also not certutil.exe.

669
Multi-Selecthard

Which THREE of the following are capabilities of Microsoft Defender XDR's automated investigation and response (AIR) that can be enabled or configured by a security operations analyst? (Choose three.)

Select 3 answers
A.Automatically block an email message or attachment.
B.Automatically isolate a compromised device.
C.Automatically modify Data Loss Prevention policies.
D.Automatically suspend a user account.
E.Automatically create new analytics rules based on incident patterns.
AnswersA, B, D

Automated Investigation and Response (AIR) in Microsoft Defender for Office 365 can automatically remediate email-borne threats by soft-deleting or blocking malicious messages and attachments identified during an investigation. This is a core remediation action that stops phishing campaigns and malware delivery directly at the mailbox, without requiring manual intervention.

Why this answer

Microsoft Defender XDR's automated investigation and response (AIR) allows security operations analysts to configure automatic actions such as blocking an email message or attachment. This is a core capability of AIR, which uses playbooks to automatically remediate threats by applying actions like soft-delete or quarantine to malicious emails or attachments based on investigation results.

Exam trap

The trap here is that candidates often confuse the capabilities of Microsoft Defender XDR's AIR with those of Microsoft Sentinel's automation rules or other Microsoft 365 compliance features, leading them to select options like modifying DLP policies or creating analytics rules, which are not part of AIR's predefined action set.

670
Multi-Selectmedium

A SOC analyst is building a scheduled analytics rule in Microsoft Sentinel to detect when a user is added to a privileged Microsoft Entra ID role (e.g., Global Administrator). Which two tables must be included in the KQL query to capture the role assignment event and to retrieve user details? (Choose 2.)

Select 2 answers
A.AADAuditLogs
B.SigninLogs
C.AzureActivity
D.IdentityInfo
AnswersA, D

AADAuditLogs is the correct choice because it is the Microsoft Entra ID audit log that records every directory write operation, including role assignments. Activities such as "Add member to role," "Remove member from role," and PIM role activations are captured here, making it the authoritative table for detecting changes to privileged role membership. A scheduled analytics rule can query this table directly to alert on unexpected or high-risk role assignment events.

Why this answer

AADAuditLogs captures all directory audit events, including role assignment activities such as adding a user to a privileged Microsoft Entra ID role. This table is essential because it records the 'Add member to role' operation with details like the target user, role name, and initiating actor, which are required to detect the security event.

Exam trap

The trap here is that candidates often confuse SigninLogs (which only records authentication attempts) with AADAuditLogs (which records administrative changes), or they overlook IdentityInfo as a separate table needed for user details, assuming the audit log alone provides all necessary user attributes.

671
Multi-Selectmedium

Which TWO of the following are required to enable user and entity behavior analytics (UEBA) in Microsoft Sentinel?

Select 2 answers
A.Microsoft Entra ID diagnostic logs must be streamed.
B.Azure subscription diagnostic logs must be enabled.
C.Windows Security Events via AMA must be ingested.
D.Microsoft Defender XDR connector must be configured.
E.UEBA must be enabled in the Sentinel settings.
AnswersC, E

Windows Security Events collected via the Azure Monitor Agent are a core UEBA data source because they supply authentication, process, and privilege-use activity for on-premises users and computers. The AMA writes these events into the 'SecurityEvent' table, which the UEBA service queries to enrich entities and generate behavioral baselines. Without this ingestion, UEBA cannot monitor desktops or servers that participate in user behavior.

Why this answer

Windows Security Events ingested via the Azure Monitor Agent (AMA) provide the necessary user and entity activity data (e.g., logon events, process creation) that UEBA analyzes to establish behavioral baselines and detect anomalies. Without this data source, UEBA lacks the raw security events required for user and entity profiling.

Exam trap

The trap here is that candidates assume UEBA requires premium connectors like Microsoft Defender XDR or Entra ID diagnostic logs, when in fact the core requirement is enabling UEBA in settings and ingesting a supported data source such as Windows Security Events via AMA.

672
MCQhard

You are a threat hunter for a company that uses Microsoft Defender for Endpoint (now part of Microsoft Defender XDR). You need to investigate a potential privilege escalation attack. You have collected process creation events from endpoints and want to identify instances where a process with low integrity level spawned a process with high integrity level. The DeviceProcessEvents table includes fields: DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessIntegrityLevel, ProcessFileName, ProcessIntegrityLevel. You need to write an advanced hunting query that returns the top 10 devices where this escalation occurred most frequently in the last 7 days. Which query should you use?

A.DeviceProcessEvents | where Timestamp > ago(7d) | where InitiatingProcessIntegrityLevel == "Low" and ProcessIntegrityLevel == "High" | summarize count() by DeviceName | top 10 by count_
B.DeviceProcessEvents | where Timestamp > ago(7d) | where InitiatingProcessIntegrityLevel == "Medium" and ProcessIntegrityLevel == "High" | summarize count() by DeviceName | top 10 by count_
C.DeviceProcessEvents | where Timestamp > ago(7d) | where InitiatingProcessIntegrityLevel != ProcessIntegrityLevel | summarize count() by DeviceName | top 10 by count_
D.DeviceProcessEvents | where Timestamp > ago(7d) | where InitiatingProcessFileName != ProcessFileName | summarize count() by DeviceName | top 10 by count_
AnswerA

Filtering on InitiatingProcessIntegrityLevel "Low" and ProcessIntegrityLevel "High" isolates genuine low-to-high integrity transitions, the exact escalation pattern sought. Summarising count() by DeviceName then top 10 by count_ ranks the noisiest endpoints over the ago(7d) window, matching both the frequency and timeframe constraints.

Why this answer

The query must filter for a genuine privilege escalation, which in Windows integrity-level terms means a low-integrity process spawning a high-integrity process. Option A correctly compares InitiatingProcessIntegrityLevel == "Low" against ProcessIntegrityLevel == "High", then aggregates by DeviceName and uses top 10 by count_ to surface the devices with the most escalation events in the last 7 days. This matches the stated requirement exactly.

Exam trap

SC-200 often tests whether candidates confuse integrity-level escalation (Low to High) with any integrity-level change or with user privilege elevation, causing them to pick the != or Medium-to-High filter.

How to eliminate wrong answers

Option B is wrong because Medium-to-High is a normal, expected transition (e.g., a user-launched process spawning an elevated process) and does not represent the low-to-high escalation the hunter was asked to find. Option C is wrong because != simply finds any integrity-level change, including legitimate de-escalations (High to Low) and Medium-to-Low transitions, producing massive false positives rather than privilege escalation. Option D is wrong because comparing process file names has nothing to do with integrity levels; different executables are spawned constantly during normal operation and this filter would return irrelevant noise.

673
MCQmedium

Refer to the exhibit. A Microsoft Sentinel scheduled rule is configured as shown. The rule generates an alert, but the incident created contains only the first alert, and subsequent alerts do not update the incident. What is the most likely cause?

A.The triggerOperator and triggerThreshold are misconfigured.
B.The KQL query is missing a join to include more data.
C.The severity is set to High, which prevents incident updates.
D.The rule does not have incident grouping enabled.
AnswerD

The rule does not have incident grouping enabled, which means each time the scheduled query fires and creates an alert, Sentinel provisions a brand-new incident instead of attaching the alert to an already open incident. In the analytics rule's Incident settings, the 'Group related alerts into a single incident' option is either unchecked or set to 'do not group,' resulting in a one-to-one alert-to-incident relationship. Consequently, the second brute-force attempt generates a new incident rather than updating the existing one, exactly as described in the exhibit. Enabling grouping with an appropriate entity (e.g., target username) and time window would cause subsequent alerts to update the original incident.

Why this answer

The exhibit shows the rule is configured to create a single incident from alerts grouped by entities, but the 'Grouping' settings are not enabled. Without incident grouping enabled, each alert generates a separate incident, and subsequent alerts do not update the existing incident. Enabling incident grouping allows alerts matching the same grouping criteria to be merged into the same incident, ensuring updates occur.

Exam trap

The trap here is that candidates often confuse alert grouping (which controls incident creation) with query logic or severity, assuming that a high severity or a missing join would cause the incident not to update, when in fact the root cause is the disabled grouping setting.

How to eliminate wrong answers

Option A is wrong because triggerOperator and triggerThreshold control the alert generation frequency (e.g., how many query results trigger an alert), not how alerts are grouped into incidents. Option B is wrong because the KQL query's structure does not affect incident grouping; the query only defines the data that generates alerts. Option C is wrong because severity settings do not prevent incident updates; severity is a property of the incident, not a grouping or update mechanism.

674
MCQhard

Your organization uses Microsoft Sentinel and has deployed the Microsoft Sentinel Solution for Microsoft Defender XDR. You need to correlate alerts from Microsoft Defender for Endpoint with Microsoft Defender for Office 365 in a single incident. What is the recommended approach?

A.Ingest alerts from both products separately and use a KQL query in an analytics rule to correlate them.
B.Use the Microsoft 365 Defender connector to ingest unified incidents from Microsoft 365 Defender, which already correlates alerts from both products.
C.Create a workbook that displays alerts from both products side by side.
D.Use a Microsoft Sentinel fusion rule to correlate the alerts.
AnswerB

The Microsoft 365 Defender connector ingests already-correlated incidents from the Microsoft 365 Defender portal, which automatically fuses alerts from Microsoft Defender for Endpoint and Microsoft Defender for Office 365 into a single incident. This native correlation consolidates the attack story, affected entities, and automated investigation state so security operations can manage one unified event instead of chasing separate alert streams. The connector also synchronizes incident status and updates from Microsoft 365 Defender back to Sentinel, keeping investigation actions consistent. This is the recommended approach because it leverages Microsoft's built-in correlation and eliminates the need for custom detection logic.

Why this answer

The Microsoft 365 Defender connector ingests unified incidents from Microsoft 365 Defender, which natively correlates alerts from Microsoft Defender for Endpoint and Microsoft Defender for Office 365 into a single incident. This is the recommended approach as it leverages the built-in correlation engine in Microsoft 365 Defender, eliminating the need for custom analytics rules or manual correlation.

Exam trap

The trap here is that candidates may think a fusion rule is the best way to correlate alerts from different sources, but the Microsoft 365 Defender connector is the recommended and more efficient approach because it ingests pre-correlated incidents from the unified XDR platform.

How to eliminate wrong answers

Option A is wrong because ingesting alerts separately and using a KQL query in an analytics rule to correlate them is inefficient and not recommended; it introduces latency and complexity, and Microsoft 365 Defender already provides native correlation. Option C is wrong because creating a workbook that displays alerts side by side does not correlate them into a single incident; workbooks are for visualization, not incident creation or correlation. Option D is wrong because a Microsoft Sentinel fusion rule is designed to correlate alerts from multiple sources into a single incident, but it is not the recommended approach when the Microsoft 365 Defender connector is available, as the connector provides pre-correlated incidents with higher fidelity and lower overhead.

675
MCQmedium

Your organization uses Microsoft Sentinel. You need to create an incident response playbook that automatically isolates a compromised device when a high-severity incident is created. The playbook should only run during business hours (9 AM - 5 PM local time). How should you configure this?

A.Configure the analytics rule to only create incidents during business hours
B.Add a condition in the playbook to check the current time
C.Use a workbook to schedule the playbook
D.Create an automation rule with a condition on the incident creation time
AnswerB

A time-based condition inside the playbook logic evaluates the current time before triggering isolation, satisfying the business-hours constraint. However, Microsoft Sentinel playbooks are Logic Apps, so this check must use a built-in date/time expression or condition action, and the recurrence trigger still fires around the clock.

Why this answer

Microsoft Sentinel automation rules cannot evaluate conditions based on the time of day (e.g., creation hour). The appropriate method is to add a condition in the playbook itself (Azure Logic Apps) to check the current time and proceed only during business hours. This approach gives you full control over the playbook's execution schedule without relying on unsupported automation rule conditions.

Exam trap

The trap here is that candidates may assume automation rules can filter by time of day, similar to conditions on other incident fields. However, automation rules cannot evaluate temporal conditions like 'created between 9 AM and 5 PM'. The correct approach is to embed a time condition directly in the playbook logic.

How to eliminate wrong answers

Option A is wrong because analytics rules create incidents based on detection logic, not time windows; configuring an analytics rule to only create incidents during business hours would miss threats detected outside those hours, which is not a supported or intended configuration. Option B is wrong because adding a condition in the playbook to check the current time would still trigger the playbook for every incident, wasting resources and potentially causing unintended actions if the time check fails; the playbook should not be invoked at all outside business hours. Option C is wrong because workbooks are visualization tools, not scheduling or automation mechanisms; they cannot trigger playbooks or enforce time-based execution.

Page 8

Page 9 of 18

Page 10