Courseiva

Microsoft Security Operations Analyst SC-200 (SC-200) — Questions 376–450

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

Page 5

Page 6 of 18

Page 7
376
Multi-Selecteasy

Your organization plans to implement Microsoft Sentinel. Which THREE components are required for a basic deployment? (Choose three.)

Select 3 answers
A.User and Entity Behavior Analytics (UEBA) enabled.
B.Analytics rules to generate incidents.
C.At least one data connector enabled.
D.Bookmarks for incident investigations.
E.A Log Analytics workspace.
AnswersB, C, E

Analytics rules are the core detection mechanism in Microsoft Sentinel that turn raw alerts into actionable incidents. To generate incidents, you must configure at least one analytics rule with incident creation enabled, using a KQL query to match threats. Without these rules, even with data ingested, Sentinel cannot automatically create security incidents.

Why this answer

Analytics rules are required to generate incidents from the data ingested into Microsoft Sentinel. Without analytics rules, the raw log data remains unprocessed and no security incidents are created, making the deployment non-functional for detection and response.

Exam trap

The trap here is that candidates often mistake optional advanced features like UEBA or bookmarks as required components, when in fact only the workspace, a data connector, and analytics rules are necessary to establish a basic, functional Sentinel deployment.

377
MCQhard

The analyst notices that the rule does not fire for a user who has 12 sign-ins from the same IP address, but all are low risk. The expected behavior is to alert when a single user has more than 10 sign-ins from the same IP with at least one high-risk sign-in. What is the issue?

A.The join should be on UserPrincipalName only, not IPAddress.
B.The join should be leftouter to include sign-ins without high risk.
C.The threshold is set to 10, but the user has 12 sign-ins, so it should fire.
D.The query requires a high-risk sign-in from the same IP, but none exist, so no match.
AnswerD

The default inner join in KQL returns only rows where both UserPrincipalName and IPAddress match between the sign-in dataset and the high-risk dataset. If this user has no high-risk sign-in that originated from the same IP, the join output is empty and the subsequent aggregation returns no result. Therefore the rule correctly does not fire, because the core condition—a high-risk event at the same source IP—is not satisfied.

Why this answer

The KQL query uses an inner join on UserPrincipalName and IPAddress, which only returns rows where a high-risk sign-in exists from the same IP. Since all 12 sign-ins from that IP are low risk, the join produces no matching rows, and the rule does not fire. The threshold of 10 is irrelevant when the join condition fails to produce any results.

Exam trap

The trap here is that candidates focus on the numeric threshold (10 vs. 12) and overlook the join logic, assuming the rule should fire because the count exceeds the threshold, when in fact the join condition is the root cause of the failure.

How to eliminate wrong answers

Option A is wrong because joining only on UserPrincipalName would incorrectly match sign-ins from different IPs, potentially firing the rule when a user has 10 sign-ins from one IP and a high-risk sign-in from a different IP. Option B is wrong because a leftouter join would include all sign-ins from the user even if no high-risk sign-in exists from that IP, causing the rule to fire when the threshold is met without any high-risk sign-in, violating the requirement. Option C is wrong because the threshold of 10 is not the issue; the rule does not fire due to the join condition failing, not because the count is below the threshold.

378
MCQeasy

In Microsoft Sentinel, an incident is created from a Fusion rule that correlates multiple alerts. The incident has a high severity. What should the analyst do first?

A.Run an automated playbook to contain the threat
B.Close the incident as false positive
C.Triage the incident by reviewing the evidence
D.Escalate the incident to senior management
AnswerC

Triage by reviewing the evidence is the mandatory first action for any Fusion-generated incident in Microsoft Sentinel, as it confirms whether the correlated alerts represent a genuine security threat and establishes the appropriate severity and priority. Analysts examine the incident's alerts, entities, and timeline to understand the attack chain and decide on next steps. This initial assessment ensures that subsequent actions—whether investigation, containment, or escalation—are based on accurate and complete information.

Why this answer

The first step in incident response within Microsoft Sentinel is to triage the incident by reviewing the evidence. A Fusion rule correlates multiple alerts into a single incident, and the analyst must examine the correlated alerts, entities, and timeline to validate the incident's legitimacy and understand the scope before taking any action. Automated playbooks or escalations should only occur after triage confirms the incident is a genuine threat.

Exam trap

The trap here is that candidates may assume a high-severity incident automatically requires immediate containment or escalation, but Microsoft Sentinel's incident response process mandates triage first to validate the correlation and avoid acting on false positives.

How to eliminate wrong answers

Option A is wrong because running an automated playbook to contain the threat should only occur after triage confirms the incident is a real threat; premature automation could disrupt legitimate operations or waste resources on a false positive. Option B is wrong because closing the incident as a false positive without reviewing the evidence violates the incident response process and could miss a genuine attack that the Fusion rule correctly identified. Option D is wrong because escalating to senior management is premature before triage; escalation should happen only after the analyst has assessed the incident's severity and impact.

379
MCQeasy

An incident in Microsoft Sentinel has been classified as a true positive. According to the incident response process, what should the analyst do next?

A.Contain the incident to prevent further damage.
B.Perform a root cause analysis.
C.Create a new analytic rule to detect similar activity.
D.Document the incident in a detailed report.
AnswerA

Once a Sentinel incident is confirmed as a true positive, the immediate objective is to stop the attacker's ability to cause additional harm. In the NIST 800-61 incident response lifecycle, containment follows detection and analysis, preceding eradication and recovery. In practice, this means initiating actions such as disabling the compromised account, isolating the asset via Microsoft Defender for Endpoint's device isolation, or blocking malicious IOCs in Microsoft Sentinel or Microsoft Defender. Delaying containment to perform deeper analysis risks lateral movement, data exfiltration, and destructive actions, which is why this is the unequivocal first step.

Why this answer

After classifying an incident as a true positive in Microsoft Sentinel, the immediate next step in the incident response process is to contain the incident to prevent further damage or lateral movement. This aligns with the NIST SP 800-61 incident response lifecycle, where containment follows identification and classification. In Sentinel, containment actions might involve disabling compromised accounts, blocking IPs via Azure Firewall, or isolating affected resources using Microsoft Defender for Cloud or Azure policies.

Exam trap

The trap here is that candidates often confuse the order of incident response phases, mistakenly thinking root cause analysis or documentation should come immediately after classification, when containment is the critical next step to stop active harm.

How to eliminate wrong answers

Option B is wrong because performing a root cause analysis is part of the eradication and recovery phases, which occur after containment has been completed. Option C is wrong because creating a new analytic rule to detect similar activity is a post-incident improvement task, not an immediate action after classification. Option D is wrong because documenting the incident in a detailed report is part of the lessons learned phase, which happens after containment, eradication, and recovery are finished.

380
MCQhard

You are a security operations architect for a company that uses Microsoft Sentinel in a hybrid environment with multiple workspaces. The company has a central SOC team that needs to view incidents from all workspaces in a single pane of glass. Each workspace belongs to a different business unit and has its own retention and access policies. You need to design a solution that provides centralized incident management without duplicating data or requiring users to switch workspaces. You also need to ensure that the SOC team can perform actions on incidents across workspaces. What should you do?

A.Create a playbook that copies incidents from all workspaces to a central workspace.
B.Use Microsoft Sentinel incident multi-view to connect all workspaces.
C.Use the Microsoft Sentinel data connector to connect all workspaces to a central workspace.
D.Create a new Log Analytics workspace that ingests data from all workspaces via diagnostic settings.
AnswerB

Microsoft Sentinel incident multi-view natively connects all workspaces by allowing a single dedicated workspace to display incidents from every workspace in a resource scope through the Incidents interface. This provides a centralized incident queue without moving or duplicating log data; analysts can triage and assign incidents across the enterprise while maintaining the original workspace context. It is the correct approach for centralized incident management in a distributed Sentinel deployment.

Why this answer

Microsoft Sentinel incident multi-view allows SOC teams to view and manage incidents across multiple workspaces from a single interface without duplicating data. This feature provides a centralized pane of glass while respecting each workspace's independent retention and access policies, and it enables cross-workspace incident actions without requiring users to switch contexts.

Exam trap

The trap here is that candidates often confuse data connectors or workspace aggregation with incident-level cross-workspace management, failing to realize that incident multi-view is the only native feature that provides a single pane of glass without data duplication or policy compromise.

How to eliminate wrong answers

Option A is wrong because creating a playbook to copy incidents duplicates data, increases storage costs, and violates the requirement to avoid data duplication; it also introduces latency and complexity. Option C is wrong because the Microsoft Sentinel data connector ingests log data into a central workspace, which duplicates data and merges retention/access policies, contradicting the requirement for each workspace to maintain its own policies. Option D is wrong because creating a new Log Analytics workspace that ingests data via diagnostic settings duplicates all log data, incurs additional ingestion and storage costs, and does not provide native incident management capabilities across workspaces.

381
MCQhard

An organization uses Microsoft Defender XDR. During an incident investigation, the security team needs to determine if a specific file was executed on any devices in the organization over the past 30 days. They have the file hash. What is the most efficient way to get this information?

A.Use the action center to search for the file
B.Use advanced hunting to query for file execution events
C.Review the incident timeline for the file
D.Check the device inventory for the file
AnswerB

Advanced hunting is the correct tool because it uses Kusto Query Language (KQL) to directly query raw telemetry tables such as DeviceProcessEvents and DeviceFileEvents across all onboarded devices. You can filter by SHA256 file hash to retrieve every execution event, including device, user, command line, and parent process details. This enables a comprehensive, time-bound search for file execution across the entire environment, which aligns with the need to locate all affected systems.

Why this answer

Advanced hunting in Microsoft Defender XDR provides a Kusto Query Language (KQL) interface to query raw event data across all workloads, including DeviceProcessEvents, DeviceFileEvents, and DeviceEvents. By querying for the specific file hash (e.g., SHA256) in process creation events over the past 30 days, the team can efficiently determine if and where the file executed. This is the most direct and scalable method for historical, organization-wide file execution searches.

Exam trap

SC-200 often tests the misconception that the action center or device inventory can be used for historical event searches, when in fact advanced hunting is the only tool designed for proactive, organization-wide threat hunting using raw telemetry.

How to eliminate wrong answers

Option A is wrong because the action center only shows remediation actions taken by Defender, not a searchable log of file executions. Option C is wrong because the incident timeline is limited to the scope of a specific incident and does not provide a global, 30-day execution history. Option D is wrong because device inventory lists installed software and devices, not execution events, and does not support searching by file hash for execution.

382
MCQhard

During an incident response, you need to collect a memory dump from a compromised Windows 10 device managed by Microsoft Defender for Endpoint. Which action should you take in the Microsoft Defender XDR portal?

A.Run a custom detection script
B.Initiate a Live Response session and run the 'memdump' command
C.Execute a Power Automate flow to collect memory
D.Start a full antivirus scan
E.Submit the device for automated investigation
AnswerB

Initiate a Live Response session in Microsoft Defender for Endpoint to get a remote shell on the device, allowing you to execute built-in commands such as memdump. The memdump command captures a full copy of the system's physical memory, which is essential for analyzing in-memory threats like process injection and credential theft. This is the correct method for on-demand memory acquisition.

Why this answer

To collect a memory dump from a compromised Windows 10 device managed by Microsoft Defender for Endpoint, you must initiate a Live Response session and run the 'memdump' command. Live Response provides a remote shell that allows forensic commands like 'memdump' to capture the full memory contents of the target machine, which is essential for analyzing volatile data during incident response. Other options, such as custom detection scripts or automated investigations, do not directly support memory acquisition.

Exam trap

The trap here is that candidates often confuse 'Live Response' with 'automated investigation' or 'custom detection scripts', assuming those can perform memory collection, when in fact only the explicit 'memdump' command within a Live Response session achieves this forensic task.

How to eliminate wrong answers

Option A is wrong because custom detection scripts are designed to run custom queries or actions based on detection logic, not to collect a full memory dump; they lack the direct memory capture capability. Option C is wrong because Power Automate flows can orchestrate actions but cannot natively execute a memory dump command on a remote endpoint; they would require a Live Response session as a prerequisite. Option D is wrong because a full antivirus scan only checks for malware signatures and does not capture volatile memory data needed for forensic analysis.

Option E is wrong because submitting the device for automated investigation triggers Microsoft's automated response playbooks, which may include memory collection only if specifically configured, but it is not a direct or guaranteed method to obtain a memory dump on demand.

383
MCQmedium

Your organization uses Microsoft Sentinel and Microsoft Defender XDR. You need to ensure that a new SOC analyst can triage incidents without being able to delete or modify analytics rules. Which role should you assign?

A.Security Reader
B.Microsoft Sentinel Reader
C.Global Reader
D.Security Operator
AnswerB

The Microsoft Sentinel Reader role is an Azure RBAC scoped to the Sentinel workspace, providing full read-only visibility into incidents, analytics rules, workbooks, and threat intelligence. It allows you to view all Sentinel data and configuration settings without permitting any edits, making it the appropriate role for a user who only needs to monitor security events. Because it is purpose-built for Sentinel, it grants direct access to analytics rules and incident details that other read-only Azure roles lack.

Why this answer

Microsoft Sentinel Reader provides read-only access to Sentinel data, including incidents, workbooks, and analytics rules, but explicitly prevents any modifications or deletions. This role is ideal for SOC analysts who need to triage incidents without altering detection configurations. Security Reader and Global Reader lack Sentinel-specific incident triage permissions, while Security Operator allows modification of incidents, which exceeds the required scope.

Exam trap

The trap here is that candidates often confuse Security Reader (which provides broad read-only access across security services) with Sentinel Reader (which is Sentinel-specific), or they assume Security Operator is sufficient because it allows incident management, but it does not grant the Sentinel-specific read permissions needed to view analytics rules without modification capabilities.

How to eliminate wrong answers

Option A is wrong because Security Reader provides read-only access to security configurations and alerts in Microsoft Defender XDR but does not include the Sentinel-specific permissions needed to triage incidents in the Sentinel portal. Option C is wrong because Global Reader grants read-only access across all Azure services, including Sentinel, but it is overly broad and not scoped to Sentinel incident triage; it also does not provide the precise Sentinel Reader permissions required. Option D is wrong because Security Operator allows management of incidents (e.g., changing status, assigning ownership) in Microsoft Defender XDR, which would permit modifications beyond triage, and it does not grant the Sentinel-specific read-only access needed for analytics rules.

384
MCQhard

A security administrator wants to ensure that all Azure virtual machines have Microsoft Defender for Cloud's vulnerability assessment (VA) solution enabled automatically. They need to deploy the VA solution to new and existing VMs without manual intervention. Which method should they use?

A.Configure 'Vulnerability assessment for machines' in Defender for Cloud settings
B.Assign an Azure Policy with DeployIfNotExists effect for the VA solution
C.Enable the Defender for Servers plan on the subscription
D.Run a PowerShell script to install the VA solution on all VMs
AnswerB

Assigning an Azure Policy definition that uses the DeployIfNotExists effect (such as the built-in 'A vulnerability assessment solution should be enabled on your virtual machines' initiative) guarantees enforcement at scale: after assignment, the policy identifies VMs without the VA solution and automatically deploys it using a managed identity for the deployment operations. Because policy evaluation runs on resource creation and during periodic compliance scans, both existing and newly created VMs are brought into compliance without manual intervention, providing continuous coverage.

Why this answer

Azure Policy with a DeployIfNotExists effect can automatically deploy the Microsoft Defender for Cloud integrated vulnerability assessment (VA) solution (Qualys or Microsoft) to both new and existing Azure VMs without manual intervention. This policy evaluates VMs that do not have the VA extension installed and triggers a remediation task to deploy it, ensuring continuous compliance across the subscription.

Exam trap

The trap here is that candidates often confuse enabling the Defender for Servers plan (which only activates the feature) with the automatic deployment mechanism provided by Azure Policy, leading them to select option C instead of the correct policy-based approach.

How to eliminate wrong answers

Option A is wrong because configuring 'Vulnerability assessment for machines' in Defender for Cloud settings only enables the VA solution at the plan level but does not automatically deploy the agent to existing or new VMs; it requires manual installation or a separate deployment mechanism. Option C is wrong because enabling the Defender for Servers plan on the subscription activates threat detection and security alerts but does not automatically deploy the VA solution; it only makes the VA feature available for manual enablement. Option D is wrong because running a PowerShell script to install the VA solution on all VMs is a one-time manual action that does not provide ongoing automatic deployment for new VMs and lacks the compliance enforcement and remediation capabilities of Azure Policy.

385
Multi-Selecteasy

You are investigating a phishing incident in Microsoft Defender for Office 365. Which THREE pieces of information are available in the Threat Explorer?

Select 3 answers
A.Email body content
B.User's mailbox audit log
C.Sender IP address
D.Delivery action (e.g., blocked, delivered to Junk)
E.Email subject and sender address
AnswersC, D, E

In Threat Explorer, each message record exposes the SenderIP property, populated from transport-level message tracking data (e.g., MessageTrace). This property is directly filterable in the UI, enabling investigators to pivot on the exact IPv4 or IPv6 address that originated the message. Because the question asks which finding could be used to attribute the message to a source host, Sender IP is a legitimate and expected column in Threat Explorer.

Why this answer

Sender IP address is available in Threat Explorer because it is a core property of email message trace data in Microsoft Defender for Office 365. Threat Explorer captures the originating IP address from the SMTP session header, which is essential for identifying the source of a phishing attack and correlating with threat intelligence feeds.

Exam trap

The SC-200 exam often tests the misconception that Threat Explorer provides full email body content or mailbox audit logs, when in reality it only exposes metadata and delivery actions, not the actual message body or user-level audit events.

386
MCQmedium

Your organization uses Microsoft Defender for Office 365. You need to ensure that when a user reports a phishing email via the built-in Outlook add-in, an automated investigation is triggered in Microsoft 365 Defender. What should you configure?

A.Define a safe links policy.
B.Enable user-reported message settings in the Microsoft 365 Defender portal.
C.Configure an anti-phishing policy.
D.Set up a safe attachments policy.
AnswerB

User-reported message settings in the Microsoft 365 Defender portal control how messages reported by end users via the Report Message or Report Phishing add-ins are processed. By enabling these settings and selecting the appropriate option, you can route reported messages to Microsoft or to a custom mailbox, and—critically—you can choose to automatically trigger an investigation and response (AIR) in Defender for Office 365 on those reports. This is the only setting among the options that directly ties user reporting to automated investigation.

Why this answer

Enabling user-reported message settings in the Microsoft 365 Defender portal allows messages reported via the built-in Outlook add-in to automatically trigger an automated investigation (AIR) in Microsoft 365 Defender. This configuration ties the user reporting action directly to the incident response workflow, enabling the system to analyze the reported email and initiate remediation steps without manual intervention.

Exam trap

The trap here is that candidates often confuse the configuration for automated investigation triggers with anti-phishing or safe links policies, not realizing that the user-reported message settings are the specific control that bridges user reporting to automated incident response.

How to eliminate wrong answers

Option A is wrong because a safe links policy protects users from malicious URLs in emails and Office documents, but it does not control how user-reported messages trigger automated investigations. Option C is wrong because an anti-phishing policy defines protection against phishing attempts (e.g., impersonation, spoofing) but does not configure the automated investigation trigger for user-reported emails. Option D is wrong because a safe attachments policy scans email attachments for malicious content using detonation in a sandbox, but it does not enable the automated investigation flow from user-reported messages.

387
MCQmedium

Your organization is using Microsoft Defender for Identity (MDI) and Microsoft Sentinel. The security team wants to correlate alerts from MDI with other data sources in Sentinel. What is the recommended approach?

A.Export MDI logs manually to Sentinel
B.Configure MDI to send syslog to Sentinel
C.Create a playbook to pull MDI alerts
D.Enable the Microsoft Defender for Identity data connector in Sentinel
AnswerD

Enabling the Microsoft Defender for Identity data connector is the correct method because it establishes an automated, native ingestion pipeline between MDI and Microsoft Sentinel. Once connected, MDI alerts and related entities are streamed into the Sentinel `SecurityAlert` and `IdentityLogonEvents` tables, enabling detection rules, hunting, and incident correlation. The connector uses the Microsoft Graph security API and requires appropriate permissions on the MDI instance, but after configuration it runs continuously without manual intervention.

Why this answer

The Microsoft Defender for Identity data connector in Microsoft Sentinel is the recommended approach because it provides native, out-of-the-box integration that automatically ingests MDI alerts and events into Sentinel without requiring additional infrastructure or manual configuration. This connector leverages the Microsoft Graph Security API to pull alerts, enabling seamless correlation with other data sources for unified threat detection and investigation.

Exam trap

The trap here is that candidates may overcomplicate the solution by thinking a custom integration (like a playbook or syslog) is needed, when Microsoft provides a native connector that handles ingestion automatically and is the simplest, most reliable method.

How to eliminate wrong answers

Option A is wrong because manually exporting MDI logs to Sentinel is inefficient, error-prone, and not scalable; Sentinel is designed for automated ingestion via connectors, not manual uploads. Option B is wrong because MDI does not natively support syslog export; it uses its own sensor and cloud service, and syslog would require a custom forwarder or third-party tool, adding complexity and potential data loss. Option C is wrong because creating a playbook to pull MDI alerts is an unnecessary workaround; the built-in data connector already handles ingestion automatically, and playbooks are for automated response, not data collection.

388
MCQeasy

Refer to the exhibit. A SOC analyst runs this KQL query in Microsoft Sentinel. What is the purpose of this query?

A.Detect brute force attempts by finding users with many failed sign-ins from a single IP
B.List all successful sign-ins in the last hour
C.Identify users who successfully signed in from multiple IPs
D.Find users with more than 5 failed sign-ins from an IP address in the last hour
AnswerD

This is the correct interpretation. The query groups the sign-in log by UserPrincipalName and IPAddress, counts the rows within the last hour, and then uses a filter to keep only groups with a count greater than 5. Because the source data is filtered to failed sign-ins, the result is exactly a list of users who have more than 5 failed sign-ins from the same IP address within that time window, which is a common brute-force detection pattern.

Why this answer

The KQL query filters for events where the result type is 'Failure' (failed sign-ins), then groups by account and IP address, counting occurrences. The `where count_ > 5` clause ensures only accounts with more than 5 failed sign-ins from a single IP are returned, which is a classic indicator of a brute force attack. This directly matches option D.

Exam trap

The trap here is that candidates may confuse 'failed sign-ins from a single IP' (option D) with 'many failed sign-ins' (option A), missing the explicit threshold of >5 in the query.

How to eliminate wrong answers

Option A is wrong because the query specifically counts failed sign-ins per IP and user, not just any user with many failed sign-ins from a single IP—it requires more than 5 failures, not just 'many'. Option B is wrong because the query filters for 'Failure' events, not successful sign-ins, and it groups by IP and user rather than listing all successful sign-ins. Option C is wrong because the query focuses on failed sign-ins, not successful ones, and it groups by single IP per user, not multiple IPs.

389
Multi-Selectmedium

Which THREE features in Microsoft Sentinel allow an analyst to automate incident response actions?

Select 3 answers
A.Playbooks (Logic Apps)
B.Watchlists
C.Workbooks
D.Automation rules
E.Analytics rules with incident automation
AnswersA, D, E

Playbooks in Microsoft Sentinel are built on Azure Logic Apps and allow analysts to define complex, multi-step automated response workflows. They can connect to hundreds of external services, execute custom logic, and perform remediation actions such as blocking an IP, disabling a user, or opening a service desk ticket. Playbooks are the most flexible automation tool in Sentinel, often triggered by automation rules or directly from an incident, and are a correct answer for features that enable automated workflows.

Why this answer

Playbooks (Logic Apps) are correct because they provide a library of pre-built or custom workflows that can be triggered by automation rules or analytics rules to execute complex, multi-step incident response actions, such as blocking IPs, isolating hosts, or enriching alerts with threat intelligence. They integrate with Azure services and third-party APIs via connectors, enabling automated remediation without manual intervention.

Exam trap

The trap here is that candidates confuse Watchlists and Workbooks as active automation tools, when they are passive data stores and visualization tools, respectively, and fail to recognize that only Playbooks, Automation rules, and Analytics rules with incident automation can directly execute response actions.

390
MCQmedium

A threat hunter runs the KQL query above in Microsoft Sentinel. What is the main limitation of this query?

A.The query relies on an external data source that may be slow or unavailable
B.The IdentityLogonEvents table does not have an IPAddress column
C.The let statement is incorrectly defined because it uses externaldata without a schema
D.The with(format="csv") is invalid
AnswerA

The query calls an external data source, so its reliability and latency depend on that service rather than Microsoft Sentinel's own log store. If the source is unavailable or slow, the hunt returns incomplete or delayed results, unlike queries against native workspace tables.

Why this answer

The query uses the externaldata() operator to fetch a list of IP addresses from an external URL. This introduces a dependency on that external source, which may be slow, fail, or be out of date. Option A correctly identifies this limitation.

Option B is incorrect because the IdentityLogonEvents table does have an IPAddress column. Option C is incorrect because the let statement is correctly defined with a schema. Option D is incorrect because the with(format='csv') is valid for CSV files.

391
Multi-Selectmedium

Which TWO data sources are most useful for detecting unauthorized lateral movement in a hybrid environment using Microsoft Sentinel?

Select 2 answers
A.Azure Activity Log
B.Network Security Group Flow Logs
C.Microsoft Defender for Endpoint DeviceLogonEvents
D.Windows Security Events (Event ID 4624)
E.Office 365 Audit Logs
AnswersC, D

Defender for Endpoint's DeviceLogonEvents table captures endpoint-level authenticated logon telemetry, including both successful and failed attempts, along with key contextual fields such as logon type, source IP, and the executing process. This makes it invaluable for detecting lateral movement, because it exposes patterns like a single account authenticating to many devices in a short time or unusual logon types (e.g., network logons) that indicate credential reuse. As a native hunting table in Microsoft 365 Defender, it enables queries that directly correlate logon activity with endpoint alerts and device risk indicators.

Why this answer

Option C, Microsoft Defender for Endpoint DeviceLogonEvents, is correct because it records interactive, network, and remote logon attempts (including type 3 and type 10) on endpoints, which are the primary telemetry for spotting credential-based lateral movement across hosts in a hybrid estate. Option D, Windows Security Events (Event ID 4624), is correct because successful logon events on domain-joined servers and workstations reveal authentication across the environment, and analyzing 4624 logon types (e.g., 3 network, 10 RDP) alongside source workstation and account fields exposes lateral movement paths. Option A, Azure Activity Log, is not the best fit because it captures control-plane operations on Azure resources (resource writes, role assignments) rather than host-to-host authentication activity.

Option B, Network Security Group Flow Logs, only shows allowed/denied IP flows at the NSG level and lacks user or process context needed to confirm unauthorized lateral movement. Option E, Office 365 Audit Logs, covers cloud service activities such as mailbox and SharePoint access, not internal endpoint or domain logon traffic.

Exam trap

SC-200 often tests the confusion between network-layer telemetry (NSG Flow Logs) and identity-layer telemetry, tempting candidates to pick flow logs when the question asks about credential-based lateral movement.

392
MCQeasy

A security analyst in Microsoft 365 Defender is investigating an incident that contains multiple alerts from different sources (e.g., Microsoft Defender for Endpoint, Microsoft 365 Defender for Office). The analyst wants to see a consolidated list of all alerts associated with the incident, including their severity, status, and detection source. Which tab within the incident details page should the analyst use?

A.Alerts tab
B.Devices tab
C.Users tab
D.Mailboxes tab
AnswerA

The Alerts tab consolidates every alert linked to the incident, showing severity, status and detection source across Defender for Endpoint and Office. This gives the analyst the unified alert list the investigation requires without switching portals.

Why this answer

The Alerts tab on the incident details page in Microsoft 365 Defender provides a consolidated, filterable list of all alerts linked to the incident, regardless of their source (e.g., Microsoft Defender for Endpoint, Microsoft Defender for Office 365). This tab displays each alert's severity, status, and detection source, allowing the analyst to triage and correlate alerts from different workloads in a single view. The other tabs focus on specific entities (devices, users, mailboxes) rather than the unified alert list.

Exam trap

The trap here is that candidates may confuse the entity-specific tabs (Devices, Users, Mailboxes) with the alert-centric view, mistakenly thinking those tabs also show alert metadata, but they only show associated entities and their properties, not the consolidated alert list with severity and detection source.

How to eliminate wrong answers

Option B is wrong because the Devices tab shows only the devices involved in the incident, not a consolidated list of alerts with their severity, status, and detection source. Option C is wrong because the Users tab lists user accounts related to the incident, not the alerts themselves. Option D is wrong because the Mailboxes tab displays only mailboxes associated with the incident, not the cross-source alert summary.

393
MCQmedium

Your company uses Microsoft Sentinel as its SIEM. You are investigating an incident where a user reported receiving a phishing email that appeared to come from the CEO requesting a wire transfer. The user did not respond. However, the incident also contains alerts from Microsoft Defender for Office 365 indicating that other users clicked on a malicious link in a similar email. The email was sent to 100 users. The company has Microsoft Defender for Endpoint deployed on all devices. The incident requires immediate containment to prevent further compromise. What should you do first?

A.Run a threat hunting query to find all users who clicked the link.
B.Block the malicious URL using Microsoft Defender for Cloud Apps.
C.Isolate the device of the user who reported the email.
D.Delete the email from all users' mailboxes using Microsoft 365 Defender.
AnswerB

Blocking the URL in Microsoft Defender for Cloud Apps immediately prevents any user or device from reaching the phishing destination through the protected web traffic. Microsoft Defender for Cloud Apps uses app proxy and conditional access to enforce URL blocking at the cloud level, covering unmanaged devices and off-network users as well. This is the fastest way to stop the spread of compromise and aligns with the 'contain first' principle in incident response.

Why this answer

Blocking the malicious URL using Microsoft Defender for Cloud Apps (now part of Microsoft 365 Defender) immediately prevents all users from accessing the phishing link, stopping further compromise at the network level. This is the fastest containment action as it applies a URL block across the tenant without requiring individual mailbox or device actions. The incident involves multiple users clicking the link, so a URL block is the most efficient first step to halt the attack chain.

Exam trap

The trap here is that candidates confuse containment with investigation or remediation, often choosing to delete the email (D) or isolate a device (C) instead of recognizing that blocking the URL is the fastest way to stop all users from accessing the malicious link, which is the immediate containment priority.

How to eliminate wrong answers

Option A is wrong because running a threat hunting query is an investigative step that identifies affected users but does not contain the threat; containment requires an immediate blocking action, not analysis. Option C is wrong because isolating the device of the user who reported the email is unnecessary since that user did not respond to the phishing email, and the compromise is from other users who clicked the link; isolating a non-compromised device wastes time and resources. Option D is wrong because deleting the email from all mailboxes removes the phishing message but does not prevent users who already clicked the link from being compromised or block the malicious URL from being accessed again if the email is recovered or forwarded.

394
MCQhard

You are investigating a potential insider threat incident in Microsoft Sentinel. A user account has been flagged for downloading a large number of files from SharePoint Online. You need to determine if the user's activity is anomalous compared to their normal behavior. Which Microsoft Sentinel feature should you use to analyze this?

A.Workbooks with custom visualizations
B.User and Entity Behavior Analytics (UEBA)
C.Fusion incident detection
D.Microsoft Sentinel analytics rules with threshold-based detection
AnswerB

UEBA in Microsoft Sentinel uses machine learning to establish baselines of normal behavior for users and entities, then identifies anomalies. For a user downloading an unusually large number of files from SharePoint, UEBA can flag this as anomalous based on historical activity, helping you determine if it's an insider threat. This is the correct feature for behavioral analysis.

Why this answer

UEBA in Microsoft Sentinel is specifically designed to analyze user and entity behavior, establishing baselines and detecting anomalies. For a user downloading an unusually large number of SharePoint files, UEBA can identify this deviation from normal activity, aiding in insider threat investigations. Other features like Fusion, threshold rules, or workbooks do not provide behavioral baselining and anomaly detection.

Exam trap

The trap here is assuming that any detection feature can perform behavioral analysis, when in fact UEBA is the dedicated capability for baselining and anomaly detection.

395
MCQhard

Your organization uses Microsoft Defender XDR and you are configuring attack surface reduction (ASR) rules. You need to implement a rule that blocks executable files from running unless they meet a prevalence, age, or trusted list criterion. Which ASR rule should you enable?

A.Block untrusted and unsigned processes that run from USB
B.Block Office applications from creating executable content
C.Block credential stealing from the Windows local security authority subsystem (lsass.exe)
D.Block executable files from running unless they meet a prevalence, age, or trusted list criterion
AnswerD

This is the correct ASR rule: it uses Microsoft's cloud-based threat intelligence to compute a risk score for each executable file. An executable is allowed to run only if it is widely prevalent, has been observed for a sufficiently long time, or is explicitly listed in a trusted list; otherwise, execution is blocked. This directly matches the requirement to block executable files from running unless they meet a prevalence, age, or trusted list criterion, making it the appropriate choice.

Why this answer

The ASR rule 'Block executable files from running unless they meet a prevalence, age, or trusted list criterion' (GUID: 01443614-cd74-433a-b99e-2ecdc07bfc25) is specifically designed to prevent executable files (e.g., .exe, .dll, .scr) from running unless they have been seen in the organization (prevalence), are old enough (age), or are on a trusted list. This rule uses cloud-delivered protection and Microsoft's reputation-based intelligence to evaluate files before execution, directly matching the requirement described in the question.

Exam trap

The trap here is that candidates often confuse this ASR rule with the 'Block untrusted and unsigned processes that run from USB' rule, mistakenly thinking that 'untrusted' means the same as 'not meeting prevalence/age/trusted list criteria,' but the USB rule only applies to removable drives, not all executable files from any location.

How to eliminate wrong answers

Option A is wrong because 'Block untrusted and unsigned processes that run from USB' (GUID: b2b3f03d-6a4c-4b7e-8f6f-0c7f8f8e8f8f) only blocks processes launched from USB removable drives, not all executable files regardless of source. Option B is wrong because 'Block Office applications from creating executable content' (GUID: 3b576869-a4ec-4529-8536-b80a7769e899) specifically targets Office apps (Word, Excel, etc.) creating executable content, not all executable files from any source. Option C is wrong because 'Block credential stealing from the Windows local security authority subsystem (lsass.exe)' (GUID: 9e6c4e1f-7d60-472f-b1a0-3f2d6d7e8f9a) is an ASR rule that protects LSASS from credential dumping attacks, not a rule that evaluates executable files based on prevalence, age, or trusted list criteria.

396
MCQhard

Your organization uses Microsoft Sentinel and Microsoft Defender for Cloud. During an incident, you need to automatically disable a compromised Azure VM from the network. Which playbook action should you use?

A.Apply an Azure Policy to deny network changes.
B.Create an Azure Firewall rule to block the VM's IP.
C.Add a rule to the VM's network security group to deny all traffic.
D.Remove the VM's role assignment from Azure RBAC.
AnswerC

Adding a deny-all rule to the VM's network security group (NSG) at the network interface level immediately blocks all inbound and outbound traffic to and from that interface, effectively isolating the VM from the rest of the network. NSG rules are evaluated in priority order, so a high-priority deny rule (e.g., priority 100) supersedes any permissive rules. This is the standard and most direct control for isolating a compromised Azure VM.

Why this answer

Adding a rule to the VM's network security group (NSG) to deny all traffic is the most direct and immediate way to isolate a compromised Azure VM at the network level. NSG rules are evaluated in order of priority, and a deny-all rule (e.g., denying any inbound and outbound traffic) effectively cuts off all network communication to and from the VM, which is a common containment step during incident response. This action can be automated via a Microsoft Sentinel playbook using the Azure Network Security Group connector.

Exam trap

The trap here is that candidates often confuse network-level isolation (NSG rules) with management-plane controls (RBAC) or perimeter-level filtering (Azure Firewall), leading them to choose options that do not actually block all traffic to the compromised VM.

How to eliminate wrong answers

Option A is wrong because applying an Azure Policy to deny network changes is a preventive governance control that blocks future modifications to network resources, but it does not actively block traffic to or from a compromised VM. Option B is wrong because creating an Azure Firewall rule to block the VM's IP would only filter traffic passing through the firewall; if the VM communicates within the same virtual network or uses other paths (e.g., VNet peering, VPN), the firewall rule may not apply, and the VM could still be reachable. Option D is wrong because removing the VM's role assignment from Azure RBAC revokes management-plane permissions (e.g., stopping or reconfiguring the VM) but does not affect network traffic; the VM would remain fully accessible over the network.

397
MCQmedium

During an incident response, a security analyst identifies that a user's account was used to access sensitive data from an anomalous location. The analyst needs to immediately prevent further access from that account while preserving forensic data. Which action should the analyst take?

A.Revoke the user's current sessions in Microsoft Entra ID.
B.Block the IP address of the anomalous location in the firewall.
C.Disable the user account in Microsoft Entra ID.
D.Enable multi-factor authentication (MFA) for the user.
AnswerC

Disabling the user account in Microsoft Entra ID is the correct containment action because it immediately prevents any new authentication attempts, including interactive and behind-the-scenes service account sign-ins. The user object, its assigned licenses, group memberships, and mailbox data are all preserved, so forensic analysis can continue without further compromise. This provides an unambiguous, identity-based kill switch that overrides every other access path relying on the user's credentials.

Why this answer

Disabling the user account in Microsoft Entra ID immediately prevents any further authentication or access to resources, including sensitive data, while preserving the account's forensic data (e.g., sign-in logs, audit events) for investigation. This action stops all current and future sessions without deleting the account or its associated data, which is critical for incident response.

Exam trap

The trap here is that candidates confuse 'revoke sessions' (which only ends current sessions but allows re-authentication) with 'disable account' (which permanently blocks all access), leading them to choose Option A as a quick fix without understanding that it does not prevent further access.

How to eliminate wrong answers

Option A is wrong because revoking the user's current sessions only terminates active sessions but does not prevent the user from re-authenticating and gaining access again, so it fails to stop further access. Option B is wrong because blocking the IP address in the firewall only addresses the specific anomalous location but does not prevent the user from accessing data from other locations, and it may block legitimate users sharing that IP. Option D is wrong because enabling MFA for the user does not immediately stop access; it only adds an additional authentication requirement for future logins, leaving the current sessions and potential re-authentication without MFA intact.

398
Multi-Selecthard

Which THREE data sources can be used in Microsoft Sentinel for threat hunting to detect unusual authentication patterns? (Choose three.)

Select 3 answers
A.SecurityEvent (Windows Event Logs)
B.AADNonInteractiveUserSignInLogs
C.CommonSecurityLog
D.OfficeActivity (Office 365)
E.SigninLogs (Microsoft Entra ID)
AnswersA, B, E

SecurityEvent carries Windows logon events, including 4624, 4625 and 4648, exposing failed logons, explicit credential use and unusual logon types. These fields let hunters detect anomalous authentication patterns across on-premises and domain-joined systems forwarded to Microsoft Sentinel.

Why this answer

Option A, SecurityEvent (Windows Event Logs), is correct because it ingests Windows security events such as 4624, 4625, and 4648, which reveal logon successes, failures, and explicit credential use that are essential for spotting unusual authentication patterns on hosts. Option B, AADNonInteractiveUserSignInLogs, is correct because it captures non-interactive Microsoft Entra ID sign-ins (token, service principal, and client-credential flows) that often indicate anomalous or automated authentication activity missed by interactive-only logs. Option E, SigninLogs (Microsoft Entra ID), is correct because it records interactive Entra ID sign-in events with details like IP address, location, device, conditional access result, and risk level, directly supporting detection of unusual authentication behavior.

Option C, CommonSecurityLog, is not among the marked answers because it primarily carries CEF-formatted data from third-party security appliances (firewalls, proxies, IDS/IPS) rather than identity authentication telemetry. Option D, OfficeActivity (Office 365), is not among the marked answers because it focuses on Office 365 workload operations such as file, mailbox, and admin activities, not core authentication sign-in patterns.

Exam trap

SC-200 often tests whether candidates can distinguish identity authentication tables (SigninLogs, AADNonInteractiveUserSignInLogs, SecurityEvent) from activity and network tables (OfficeActivity, CommonSecurityLog), so the trap is selecting OfficeActivity or CommonSecurityLog because they sound security-relevant when the question specifically asks about authentication patterns.

399
MCQhard

You are hunting for signs of ransomware using Microsoft Defender XDR's advanced hunting. Which query pattern would best identify a process that encrypts many files in a short time?

A.DeviceFileEvents | summarize Duration = max(Timestamp)-min(Timestamp) by DeviceName, InitiatingProcessFileName | where Duration < 1h
B.DeviceFileEvents | where ActionType == 'FileModified' | summarize Count = count() by DeviceName, InitiatingProcessFileName, bin(Timestamp, 5m) | where Count > 100
C.DeviceProcessEvents | where FileName in ('powershell.exe', 'wscript.exe') | summarize by DeviceName
D.DeviceFileEvents | summarize Count = count() by DeviceName | where Count > 1000
AnswerB

Aggregating DeviceFileEvents by device, initiating process and five-minute bins, then filtering counts above 100, directly surfaces mass file modification — the ransomware encryption signature. Grouping by InitiatingProcessFileName attributes the burst to a specific process, satisfying the stem's requirement to identify rapid, high-volume encryption activity.

Why this answer

It counts the number of file modifications per initiating process per 5-minute window using DeviceFileEvents, and then filters for those with more than 100 modifications. This directly detects a process that is rapidly encrypting many files, which is a strong indicator of ransomware. Option A is wrong because it measures the duration between the first and last file event by a process, not the count; a process could encrypt files over a longer period and still be suspicious, but this query would miss high-density encryption in a short burst.

Option C is wrong because it only looks at process creation events for specific script interpreters (powershell.exe, wscript.exe), not at file modifications, and it fails to identify encryption activity from other executables. Option D is wrong because it counts all file events per device without grouping by process, so it cannot pinpoint which process is responsible for the encryption.

400
Multi-Selecteasy

Your SOC team needs to ensure that all incidents in Microsoft Sentinel are assigned to an analyst within 30 minutes of creation. Which TWO configurations should you implement?

Select 2 answers
A.Create a playbook that uses the Update Incident action to set the owner field.
B.Set up a playbook that sends an email to the SOC manager when an incident is created.
C.Create an automation rule that triggers when an incident is created and sets the owner.
D.Configure a Microsoft Teams connector to post incidents to a channel.
E.Modify the analytics rule to include a custom details field for analyst name.
AnswersA, C

Microsoft Sentinel playbooks, built on Azure Logic Apps, include an 'Update Incident' action that can directly set the incident's Owner property to a specific user or group. When invoked from an automation rule on incident creation, this action assigns ownership as part of the incident lifecycle, making it a fully valid solution. The playbook can also incorporate conditions or lookups to choose the right owner dynamically.

Why this answer

A playbook (an Azure Logic Apps workflow) can use the 'Update Incident' action to programmatically set the owner field on an incident. This allows you to implement custom assignment logic, such as round-robin or based on analyst skill set, triggered by an automation rule or manually. Option C is correct because an automation rule can directly set the owner field when an incident is created, without needing a playbook, by using the 'Update incident' action within the rule itself.

Both configurations ensure incidents are assigned within the required 30-minute window.

Exam trap

The trap here is that candidates often confuse notification actions (email, Teams) with assignment actions, assuming that notifying a manager or posting to a channel fulfills the requirement to 'assign' the incident, but only setting the owner field in the incident object actually assigns it.

401
MCQmedium

Your organization uses Microsoft Defender for Endpoint. A user reports that their device is running slowly and exhibiting unusual network activity. You run a live response session and find a suspicious process running. Which action should you take first to contain the threat?

A.Collect a full memory dump for analysis.
B.Terminate the suspicious process.
C.Isolate the device from the network.
D.Add a firewall rule to block outbound traffic from the device.
AnswerC

Isolating the device cuts all network communication except the Defender for Endpoint service channel, immediately halting the suspicious process's command-and-control traffic and lateral movement. This satisfies the stem's containment requirement before further investigation, since live response alone leaves the threat active and the device still reachable.

Why this answer

The first containment action in a live response session should be to isolate the device from the network. Isolation stops lateral movement, command-and-control communication, and data exfiltration while preserving the device state for forensic investigation. Terminating the process or collecting a memory dump can wait until the device is contained, because the threat may respawn or the attacker may pivot.

Exam trap

SC-200 often tests the ordering of incident response steps — candidates pick 'terminate process' or 'collect memory' because they sound like immediate action, but containment (isolation) must precede eradication and forensic collection.

How to eliminate wrong answers

Option A is wrong because collecting a full memory dump is a forensic preservation step, not containment — it takes time and does not stop the threat from spreading. Option B is wrong because terminating the suspicious process may destroy evidence, and the process could be re-launched by a persistence mechanism; containment must come first. Option D is wrong because adding a firewall rule to block outbound traffic is a partial, manual mitigation that is slower and less complete than Defender for Endpoint's built-in device isolation, which blocks all network traffic except the Defender service.

402
MCQeasy

A company uses Microsoft Defender for Cloud. They need to continuously assess the compliance of their Azure resources against the CIS benchmark. Which feature should they enable?

A.Regulatory compliance dashboard
B.Secure Score
C.Azure Policy
D.Just-In-Time VM access
AnswerA

The Regulatory compliance dashboard in Microsoft Defender for Cloud is the dedicated feature that assesses resources against built-in regulatory initiatives such as CIS, Azure Security Benchmark, and other standards. It provides a continuous compliance score with per-control status, showing which resources pass or fail each benchmark requirement. Because you can add or remove standards and see detailed remediation steps, this dashboard is the direct answer for monitoring compliance against CIS benchmarks.

Why this answer

Microsoft Defender for Cloud's Regulatory compliance dashboard continuously assesses Azure (and AWS/GCP) resources against built-in standards including CIS, PCI DSS, ISO 27001, and NIST, showing pass/fail per control. Enabling the CIS benchmark in this dashboard gives the continuous compliance assessment the company needs. It is the purpose-built feature for mapping resource configurations to regulatory controls.

Exam trap

SC-200 often tests whether candidates confuse Secure Score (a posture score) with the Regulatory compliance dashboard (framework-mapped assessment), so the trap is picking Secure Score because it sounds like it measures compliance.

How to eliminate wrong answers

Option B is wrong because Secure Score is a prioritized posture score that aggregates recommendations but does not map them to specific regulatory frameworks like CIS — it measures overall security hygiene, not compliance against a benchmark. Option C is wrong because Azure Policy is the underlying enforcement/assessment engine that Defender for Cloud uses, but by itself it does not provide the compliance dashboard view mapped to CIS controls; you would have to build and map initiatives manually. Option D is wrong because Just-In-Time VM access is a feature that opens management ports on demand for a limited time — it is a workload protection control, not a compliance assessment feature.

403
MCQeasy

Your organization uses Microsoft Sentinel. The SOC manager wants to track the average time to triage incidents. You need to create a report that shows this metric. What should you use?

A.Create a workbook that uses KQL to query incident data and display the average time.
B.Create a playbook that sends a report via email.
C.Create an automation rule that logs the triage time to a custom table.
D.Create an analytics rule that calculates the time to triage.
AnswerA

Workbooks query the Sentinel data lake with KQL, so incident records can be aggregated to compute average triage duration and rendered as a report. Analytics rules generate incidents and automation rules respond to them; neither produces the requested metric visualisation.

Why this answer

Microsoft Sentinel workbooks can be built using Kusto Query Language (KQL) to query the SecurityIncident table and compute the average time to triage, allowing the SOC manager to track this metric. Option B is incorrect because playbooks are designed for automation and response, not for creating reports. Option C is incorrect because automation rules are for automated incident handling, not for reporting or logging custom metrics.

Option D is incorrect because analytics rules are used to generate alerts based on queries, not to produce reports.

404
MCQmedium

You are responding to a data exfiltration incident involving a user who copied sensitive files to a personal cloud storage service. The files were accessed from the user's managed device. Which Microsoft Defender for Cloud Apps activity policy should you create to detect similar future incidents?

A.An anomaly detection policy that flags impossible travel.
B.An activity policy that detects uploads to personal cloud storage services.
C.A file policy that detects files shared with external users.
D.An app discovery policy that identifies new cloud apps used in the organization.
AnswerB

An activity policy in Microsoft Defender for Cloud Apps is designed to monitor specific actions, such as file uploads, across cloud apps. You can configure policy filters based on app (e.g., personal cloud storage services) and the activity type (e.g., upload). This directly matches the incident by triggering an alert when a user uploads a file to a non-corporate cloud service, making it the correct response control.

Why this answer

The incident involves a user copying sensitive files to a personal cloud storage service from a managed device. An activity policy in Microsoft Defender for Cloud Apps can be configured to detect specific activities, such as uploads to personal cloud storage services (e.g., Dropbox, Google Drive), by monitoring the 'Upload' event for recognized cloud apps. This directly addresses the detection of similar future incidents by alerting on the exact action (upload) to the specific service category (personal storage).

Exam trap

The trap here is that candidates may confuse 'file policy' (which governs sharing and permissions) with 'activity policy' (which governs actions like uploads), leading them to incorrectly select Option C, which detects shared files rather than the act of uploading.

How to eliminate wrong answers

Option A is wrong because an anomaly detection policy for impossible travel detects geographically improbable logins, not file uploads to personal cloud storage. Option C is wrong because a file policy that detects files shared with external users focuses on sharing permissions (e.g., via a link), not the act of uploading files to a personal cloud storage service. Option D is wrong because an app discovery policy identifies new cloud apps being used in the organization via traffic logs, but it does not detect specific user activities like uploads to already-known personal storage services.

405
MCQeasy

You are investigating a ransomware incident in Microsoft Sentinel. The incident contains multiple alerts. You need to group related alerts under the same incident to reduce alert fatigue. What should you do?

A.Enable User and Entity Behavior Analytics (UEBA).
B.Create a new analytics rule to combine alerts.
C.Use an automation rule to merge incidents.
D.Configure incident creation rules in the analytics rule.
AnswerD

Configuring incident creation rules in the analytics rule is the correct way to combine related alerts into a single incident in Microsoft Sentinel. When editing an analytics rule, you can enable incident creation and set alert grouping to group up to 150 alerts into one incident based on matching entities (such as account or host) within a defined time window (up to 24 hours). This approach ensures that alerts from the same attack campaign are represented as a single incident, reducing alert fatigue and providing a unified scope for investigation.

Why this answer

In Microsoft Sentinel, incident creation is configured directly within the analytics rule. When you create or edit an analytics rule, the 'Incident creation' settings allow you to enable incident generation from alerts triggered by that rule. This ensures that all alerts from the same rule are grouped into a single incident, reducing alert fatigue by preventing multiple separate incidents for related alerts.

Exam trap

The trap here is that candidates often confuse automation rules (which handle incident actions) with incident creation settings within analytics rules, mistakenly thinking automation rules can merge incidents when they cannot.

How to eliminate wrong answers

Option A is wrong because UEBA (User and Entity Behavior Analytics) is used to detect anomalous behavior based on historical patterns, not to group related alerts under the same incident. Option B is wrong because creating a new analytics rule does not combine alerts; each analytics rule generates its own alerts, and you cannot merge alerts from different rules into one incident through rule creation alone. Option C is wrong because automation rules can trigger actions on incidents (e.g., assign, close, or run playbooks) but cannot merge separate incidents into one; merging incidents is not a supported action in automation rules.

406
Multi-Selectmedium

Which TWO of the following are valid response actions that can be taken on a device from Microsoft Defender for Endpoint? (Choose two.)

Select 2 answers
A.Quarantine email
B.Disable user account
C.Run antivirus scan
D.Reset user password
E.Isolate device from network
AnswersC, E

Running an antivirus scan is a native device response action in Microsoft Defender for Endpoint that initiates a Windows Defender scan directly on the endpoint. This action can be a quick or full scan, allowing security teams to detect and remediate malware without removing the device from the network. It is commonly used to assess a device's health after a potential compromise and is a valid response action for endpoint containment.

Why this answer

Microsoft Defender for Endpoint includes a 'Run antivirus scan' response action that initiates a Microsoft Defender Antivirus scan on the device. This action can be triggered from the Microsoft 365 Defender portal to detect and remediate malware or suspicious files without requiring user interaction.

Exam trap

The trap here is that candidates confuse response actions across different Microsoft security products (Defender for Endpoint vs. Defender for Office 365 vs. Azure AD) and mistakenly select identity-based or email-based actions as valid device-level responses.

407
MCQhard

Your organization has Microsoft Sentinel with UEBA enabled. An incident is generated for a user with high risk score. You need to identify if the user's recent behavior deviates from their baseline. Which Sentinel feature should you use?

A.A custom hunting query using the BehaviorAnalytics table.
B.The user's Azure AD sign-in logs.
C.The UEBA timeline in the entity page.
D.The incident investigation graph.
AnswerC

The UEBA timeline is a dedicated tab on the Sentinel entity page that presents a chronological view of a user's or device's activities, highlighting deviations from established behavioral baselines and flagging risky actions with anomaly scores. Because UEBA is natively integrated into entity pages, this is the built-in feature designed to show baseline deviations over time. It directly addresses the requirement to see anomalies relative to normal behavior.

Why this answer

The UEBA timeline in the entity page is the correct feature because it provides a chronological view of a user's activities, including deviations from their established behavioral baseline. When UEBA is enabled, Sentinel profiles normal behavior for each user and flags anomalies; the timeline directly visualizes these deviations, such as unusual login times, locations, or resource access, which aligns with the need to identify if recent behavior deviates from the baseline.

Exam trap

The trap here is that candidates often confuse the BehaviorAnalytics table (option A) as the primary tool for deviation analysis, overlooking that the UEBA timeline is the purpose-built, no-code interface for visualizing baseline deviations directly on the entity page.

How to eliminate wrong answers

Option A is wrong because a custom hunting query using the BehaviorAnalytics table, while capable of surfacing UEBA data, is not the dedicated feature for quickly viewing a user's behavioral timeline and deviations; it requires writing and executing a KQL query, which is less efficient than the built-in timeline. Option B is wrong because Azure AD sign-in logs only show authentication events and do not incorporate UEBA's behavioral baseline analysis or deviations; they lack the contextual anomaly scoring and timeline of behavioral changes. Option D is wrong because the incident investigation graph focuses on mapping relationships between entities and alerts within an incident, not on displaying a user's behavioral timeline or baseline deviations.

408
MCQmedium

Your organization has a Microsoft Sentinel workspace that ingests logs from multiple sources. You need to implement a process to review and approve changes to analytics rules before they are deployed to production. What should you use?

A.Create a playbook that emails the SOC manager when an analytics rule is modified.
B.Use a workbook to track changes to analytics rules.
C.Configure Microsoft Sentinel repository integration with Azure DevOps and use branch policies for approval.
D.Export analytics rules to a notebook for manual review.
AnswerC

Microsoft Sentinel repository integration connects your workspace to an Azure DevOps (or GitHub) repository that stores analytics rules as ARM templates or Terraform files. By configuring branch policies on the main branch, you mandate that any rule modification must be made in a separate branch and merged only after a reviewer approves the pull request. Successful merge then triggers a CI/CD pipeline to deploy the rules to Sentinel, providing version control, audit history, and a hard, enforceable approval gate that governs every change before it reaches the production workspace.

Why this answer

Microsoft Sentinel repository integration with Azure DevOps (or GitHub) enables source control for analytics rules, allowing changes to be managed through pull requests and branch policies. This enforces a review and approval workflow before rules are deployed to production, directly meeting the requirement for a structured change management process.

Exam trap

The trap here is that candidates may confuse notification or tracking mechanisms (like playbooks or workbooks) with actual approval workflows, overlooking that only source control integration with branch policies provides a formal review and approval gate before deployment.

How to eliminate wrong answers

Option A is wrong because a playbook that emails the SOC manager when a rule is modified only provides notification, not a formal review and approval process; it lacks enforcement of approval before deployment. Option B is wrong because a workbook is a visualization tool for querying and displaying data, not a mechanism for managing or approving changes to analytics rules. Option D is wrong because exporting rules to a notebook for manual review is an offline, non-automated process that does not integrate with version control or enforce approval workflows.

409
Multi-Selecteasy

Which TWO are immediate containment actions in Microsoft Sentinel for a compromised Azure VM? (Choose two.)

Select 1 answer
A.Install anti-malware extension
B.Apply an NSG to block all inbound and outbound traffic
C.Reset the VM administrator password
D.Initiate a VM backup
E.Stop the VM using an automation rule
AnswersB

Attaching a network security group denies all inbound and outbound traffic to the VM, cutting command-and-control and lateral movement immediately. This satisfies the containment requirement by isolating the compromised host while investigation continues, without deleting evidence.

Why this answer

The correct answer is B (Apply an NSG to block all inbound and outbound traffic), an immediate containment action that isolates the compromised Azure VM by blocking network traffic. Option A (install anti-malware extension) is a remediation step, not immediate containment. Option C (reset password) does not stop an active attack and may interfere with investigation.

Option D (initiate VM backup) is not containment and could preserve compromised data. Option E (stop the VM using an automation rule) is not a valid Sentinel containment action; automation rules trigger playbooks and do not directly stop VMs, and stopping the VM can destroy volatile evidence.

Exam trap

Do not confuse remediation (installing anti-malware, resetting passwords, backups) with immediate containment (network isolation). Microsoft Sentinel automation rules trigger playbooks; they do not directly stop VMs.

410
MCQhard

A SOC team uses Microsoft Sentinel with Microsoft Defender XDR integration. An incident is created from a Defender for Endpoint alert. The analyst wants to run a KQL query across all affected devices without creating a new analytics rule. How can the analyst achieve this?

A.Modify the analytics rule that created the incident.
B.Use the incident's Logs blade to run a KQL query.
C.Use the Microsoft Sentinel Hunting blade.
D.Create a new workbook.
AnswerB

The incident's Logs blade opens a query environment scoped to the underlying Log Analytics workspace, allowing you to run KQL to pivot on entities, timestamps, or raw tables without creating or altering any rule. This ad-hoc query capability is the appropriate tool for investigating an existing incident because it gives immediate, context-aware access to the telemetry relevant to that incident.

Why this answer

The incident's Logs blade in Microsoft Sentinel allows analysts to run KQL queries directly against the data ingested into the workspace, scoped to the incident's context. This enables ad-hoc investigation across all affected devices without modifying or creating any analytics rules, which would require rule authoring and deployment.

Exam trap

The trap here is that candidates confuse the Hunting blade (which is for proactive, scheduled queries) with the incident-specific Logs blade (which is for reactive, ad-hoc investigation), leading them to choose option C incorrectly.

How to eliminate wrong answers

Option A is wrong because modifying the analytics rule that created the incident would change the rule's logic for future detections, not allow a one-time ad-hoc query across affected devices. Option C is wrong because the Hunting blade is designed for proactive threat hunting across historical data, not for running a query scoped to a specific incident's affected devices. Option D is wrong because creating a new workbook is for building visualizations and reports, not for running an immediate, incident-scoped KQL query.

411
Multi-Selecteasy

Your organization uses Microsoft Defender XDR (formerly Microsoft 365 Defender). You need to configure role-based access control (RBAC) for the security team. Which TWO built-in roles can be assigned in Microsoft 365 Defender to manage incidents and alerts?

Select 2 answers
A.Global Administrator
B.Compliance Administrator
C.Security Operator
D.Security Administrator
E.Security Reader
AnswersC, D

Security Operator is purpose-built for tier-1 incident response within Microsoft 365 Defender. It can view active incidents, modify their status, assign them to analysts, and perform basic response actions like isolating devices or blocking senders—without granting broader administrative control over security policies or identity management. This role provides the exact permissions required for day-to-day alert handling while adhering to least privilege, making it the correct answer.

Why this answer

Security Operator and Security Administrator are the two built-in roles in Microsoft 365 Defender that include permissions to manage incidents and alerts. Security Operator can view and respond to incidents and alerts, while Security Administrator has full access to all security features, including the ability to edit policies and manage incidents. These roles are specifically designed for security operations tasks within Defender XDR.

Exam trap

The trap here is that candidates often confuse Security Reader (read-only) with Security Operator (read-write for incidents/alerts), or assume Global Administrator is required for incident management, when in fact Security Operator and Security Administrator are the correct roles with the necessary permissions.

412
MCQeasy

A company wants to continuously assess the compliance of their Azure resources against the CIS (Center for Internet Security) benchmark. Which Microsoft Defender for Cloud feature should they use?

A.Regulatory compliance dashboard
B.Secure score
C.Azure Policy
D.Workload protections
AnswerA

The Regulatory compliance dashboard in Defender for Cloud is the dedicated feature that continuously assesses your Azure resources against built-in standards such as the CIS Microsoft Azure Foundations Benchmark and NIST SP 800-53. When you add a standard, Defender for Cloud assigns the corresponding Azure Policy initiative to your subscriptions, and the dashboard then shows the compliance state for each control, including the number of passed and failed resources. This dashboard is the correct choice because it explicitly links continuous policy evaluation to regulatory frameworks, allowing you to track and prove compliance over time.

Why this answer

The Regulatory compliance dashboard in Microsoft Defender for Cloud provides pre-built assessments and continuous monitoring against specific compliance standards, including the CIS benchmark. It automatically evaluates Azure resources against CIS controls and displays compliance status, making it the correct feature for this requirement.

Exam trap

The trap here is that candidates often confuse Secure score (which measures overall security hygiene) with the Regulatory compliance dashboard (which measures adherence to specific standards like CIS), leading them to select Secure score when the question explicitly asks for compliance against a benchmark.

How to eliminate wrong answers

Option B is wrong because Secure score measures overall security posture based on implemented security controls, not specific compliance with a regulatory standard like CIS. Option C is wrong because Azure Policy is a service for creating, assigning, and managing policies that enforce rules on resources, but it does not natively include pre-built CIS benchmark assessments; the Regulatory compliance dashboard leverages Azure Policy initiatives but provides the compliance-specific dashboard. Option D is wrong because Workload protections refer to advanced threat detection capabilities for workloads (e.g., servers, databases), not compliance assessment against benchmarks like CIS.

413
MCQhard

An administrator creates a Microsoft Defender for Cloud Apps policy to block unsanctioned cloud storage apps. Despite the policy, users can still access these apps. What is the most likely cause?

A.The action type 'Block' is incorrect; it should be 'Alert'
B.The policy requires a 'Device' filter to apply to all users
C.The filter uses 'Unsanctioned' tag, but apps are tagged 'Sanctioned'
D.The policy mode is set to 'Monitor', which only alerts and does not block
AnswerD

The policy mode is indeed set to 'Monitor', which is why the 'Block' action does not work. In Defender for Cloud Apps, a policy in Monitor mode only records activity and creates alerts; it does not enforce any governance or blocking actions. To actually block app access, the policy mode must be set to an enforcement mode like 'Block' or 'Govern'. Therefore, this is the correct explanation because changing the mode from Monitor to an enforced setting is required for the Block action to take effect.

Why this answer

When a Microsoft Defender for Cloud Apps policy is set to 'Monitor' mode, it only generates alerts and does not enforce any blocking action. To actually block unsanctioned cloud storage apps, the policy must be configured with a 'Block' action type, typically in conjunction with a 'Governance' action that applies the block at the proxy or API level. The 'Monitor' mode is designed for detection and logging, not enforcement.

Exam trap

The trap here is that candidates often focus on the action type (e.g., 'Block' vs. 'Alert') or the app tagging, overlooking that the policy mode itself controls whether enforcement occurs, not just the action setting.

How to eliminate wrong answers

Option A is wrong because the 'Block' action type is correct for preventing access; changing it to 'Alert' would only notify administrators without blocking. Option B is wrong because a 'Device' filter is not required to apply a policy to all users; policies can target users, groups, or IP ranges without a device condition. Option C is wrong because if apps are tagged 'Sanctioned', they would be allowed, not blocked; the issue is that the policy is in 'Monitor' mode, which does not enforce the block regardless of the tag.

414
MCQmedium

Refer to the exhibit. You have a KQL query in a Microsoft Sentinel analytics rule. The rule is not generating incidents even though there are 'Suspicious sign-in' alerts from non-contoso.com users. What is the most likely issue?

A.The 'extend' line is incorrectly parsing the entity.
B.The query is querying the wrong table. 'Suspicious sign-in' alerts may be in a different table.
C.The 'where' clause using !endswith is incorrect.
D.The query does not filter by AlertName correctly.
AnswerB

This is the correct issue. 'Suspicious sign-in' alerts are typically surfaced through Microsoft Sentinel's SecurityAlert table or through identity protection logs such as SigninLogs, and these records are not guaranteed to exist in the table referenced by this query. Querying the wrong table means the where and extend clauses are applied to a schema that lacks the alert evidence or uses different field names, resulting in no matching rows. Confirming the table name against the alert product's data connector is the necessary first troubleshooting step.

Why this answer

The query is likely querying the 'Alert' table, but 'Suspicious sign-in' alerts from non-contoso.com users are generated by Microsoft Defender for Identity or Azure AD Identity Protection and stored in the 'SecurityAlert' table (or 'AlertEvidence' in the new schema). The rule's query must reference the correct table to retrieve these alerts; otherwise, no matching records are found, and no incidents are created.

Exam trap

The trap here is that candidates assume all security alerts are stored in a single 'Alert' table, but Microsoft Sentinel separates alerts into multiple tables (e.g., 'SecurityAlert', 'AlertEvidence', 'SigninLogs') based on the source service, and the exam tests your knowledge of which table corresponds to which alert type.

How to eliminate wrong answers

Option A is wrong because the 'extend' line is used to add or modify columns, not to parse entities; entity parsing is done via the 'EntityMapping' section of the analytics rule, not within the KQL query itself. Option C is wrong because the 'where' clause using '!endswith' is syntactically correct for filtering out domains that do not end with a specific suffix (e.g., 'contoso.com'); the logic is valid if the field contains the full user principal name. Option D is wrong because the query does not need to filter by AlertName if the rule is triggered by the presence of any alert from the 'Suspicious sign-in' category; the rule's trigger condition is based on the query returning results, not on a specific alert name filter.

415
MCQmedium

You are reviewing an alert rule in Microsoft Sentinel created via ARM template. What is the primary purpose of this rule?

A.To send an alert when a sign-in with high risk level is detected.
B.To isolate the user's device from the network.
C.To automatically block the user from signing in.
D.To create an incident in Microsoft Sentinel.
AnswerA

This is the intended function of the analytics rule: it periodically runs a KQL query over SigninLogs where the risk level is 'high', and when the number of matching sign-ins exceeds the threshold, it generates a Sentinel alert and sends a notification through the configured action group (email, SMS, or ITSM). The action group is the delivery channel, so the rule's purpose is precisely to alert on high-risk sign-in events—not to take any direct remediation or downstream orchestration steps.

Why this answer

The primary purpose of an alert rule in Microsoft Sentinel created via ARM template is to generate an alert when a specific condition is met, such as a sign-in with a high risk level detected by Azure AD Identity Protection. This alert can then be used to trigger automated responses or create incidents, but the rule itself is designed to detect and alert on the defined condition, not to perform remediation actions like isolation or blocking.

Exam trap

The trap here is that candidates often confuse the purpose of an alert rule with the actions that can be triggered by it, such as automated remediation or incident creation, leading them to select options that describe downstream responses rather than the rule's primary detection function.

How to eliminate wrong answers

Option B is wrong because isolating a user's device from the network is a remediation action that would be performed by an automated response (e.g., a playbook or a Microsoft Defender for Endpoint action), not by the alert rule itself. Option C is wrong because automatically blocking a user from signing in is a conditional access policy action in Azure AD, not a function of a Sentinel alert rule; the rule only generates an alert based on risk detection. Option D is wrong because while an alert rule can be configured to automatically create an incident in Microsoft Sentinel, that is a secondary configuration setting (e.g., 'Create incident from alert' enabled), not the primary purpose of the rule; the rule's core function is to generate an alert when the detection condition is met.

416
MCQmedium

Your Microsoft Sentinel workspace is ingesting logs from multiple sources. You notice that the data ingestion cost is higher than expected. You want to reduce costs without losing security value. Which action should you take?

A.Reduce the retention period for all data to 30 days.
B.Switch the pricing tier from Capacity Reservations to Pay-as-you-go.
C.Disable analytics rules that generate high volume of alerts.
D.Configure basic logs ingestion for verbose data sources such as firewall logs.
AnswerD

Configuring Basic Logs ingestion for verbose data sources such as firewall logs is a valid cost optimization because this data tier is significantly cheaper per GB than Analytics Logs, yet still queryable for incident response using KQL within the 8-day default retention window. This allows you to preserve high-volume raw telemetry for on-demand hunting and investigation without paying full analytics prices for every event, and you can selectively upgrade specific tables or add dedicated retention policies as needed. It directly reduces the main cost driver—ingestion—while maintaining access to the data for Deep Dive (also known as resource-oriented) when a security incident occurs.

Why this answer

Basic logs are designed for high-volume, verbose data sources (e.g., firewall logs, syslog) that have lower security value. They are stored at a reduced cost and support only summary queries, not full KQL analytics. By routing verbose logs to basic logs, you reduce ingestion costs while retaining the ability to perform threat hunting and incident response on high-value analytics logs.

Exam trap

The trap here is that candidates confuse reducing retention (Option A) with reducing ingestion volume, or they mistakenly think disabling analytics rules (Option C) lowers ingestion costs, when in fact ingestion cost is driven by data volume, not rule execution.

How to eliminate wrong answers

Option A is wrong because reducing retention to 30 days may delete historical data needed for compliance or long-term threat hunting, and it does not address the root cause of high ingestion volume. Option B is wrong because switching from Capacity Reservations to Pay-as-you-go typically increases per-GB costs, especially at high ingestion volumes, making the problem worse. Option C is wrong because disabling analytics rules reduces security monitoring coverage and may allow threats to go undetected; it does not reduce the cost of ingesting the underlying log data.

417
Multi-Selecthard

An analyst writes an advanced hunting query to investigate a suspicious executable that initiated outbound connections. Which two Microsoft 365 Defender tables are most relevant? (Choose 2.)

Select 2 answers
A.DeviceProcessEvents.
B.DeviceNetworkEvents.
C.EmailAttachmentInfo.
D.IdentityInfo.
AnswersA, B

DeviceProcessEvents is the correct table because it records process creation events, including the executable path, command-line arguments, and process ID (which appears as InitiatingProcessId for child processes). In an advanced hunting query, this table supplies the process execution side of the evidence chain, enabling you to join with network events on device ID and time window to determine exactly which process was launched before a suspicious connection was made.

Why this answer

DeviceProcessEvents is correct because it records process creation events, including the executable that initiated the outbound connection. By querying this table, you can identify the suspicious executable's name, command line, and parent process, which is essential for tracing the origin of the malicious activity.

Exam trap

The trap here is that candidates may mistakenly choose EmailAttachmentInfo thinking the executable arrived via email, but the question focuses on the executable's outbound connections, not its delivery method.

418
MCQhard

Your organization uses Microsoft Defender XDR. You need to configure a custom detection rule that runs every hour and alerts when a specific process is executed on multiple devices within 10 minutes. Which type of rule should you create?

A.Hunting query saved as a detection
B.Behavioral rule
C.Custom detection rule
D.Advanced hunting query
AnswerC

Custom detection rule is correct because this is the dedicated rule type in Microsoft Defender XDR that allows you to schedule an Advanced Hunting KQL query to run at defined intervals, apply time-based aggregations, and automatically generate alerts and incidents when thresholds are met. Custom detection rules provide full control over frequency, severity, and response actions, and they directly integrate with the incident management pipeline. This makes them the precisely designed mechanism for turning a recurring query into an active, automated detection.

Why this answer

Custom detection rules in Microsoft Defender XDR allow you to define a query that runs on a schedule (e.g., every hour) and triggers an alert based on aggregation over a specified time window (e.g., 10 minutes). This rule type supports the exact requirement: detecting a specific process executed on multiple devices within a short timeframe, using the `make_set` or `dcount` aggregation functions in KQL.

Exam trap

The trap here is that candidates confuse 'custom detection rule' with 'advanced hunting query' or 'saved hunting query,' assuming any KQL-based alert is the same, but only custom detection rules provide the scheduled, time-windowed aggregation and alerting required for this scenario.

How to eliminate wrong answers

Option A is wrong because a hunting query saved as a detection is a static query that runs on a schedule but does not natively support time-windowed aggregation across multiple devices; it would require manual KQL to simulate the 10-minute window, and it lacks the built-in alerting and tuning capabilities of a custom detection rule. Option B is wrong because behavioral rules are designed to detect anomalies based on learned baselines (e.g., user or device behavior), not to match a specific process name across multiple devices within a fixed time window. Option D is wrong because an advanced hunting query is an ad-hoc, interactive search tool that does not run on a schedule or generate alerts automatically; it requires manual execution and cannot be used as a persistent detection.

419
MCQmedium

A company uses Microsoft Defender for Cloud to manage security across multiple Azure subscriptions. They want to automatically remediate non-compliant resources when a policy violation is detected—for example, enabling encryption on a storage account that has it disabled. Which feature should they configure?

A.Regulatory compliance dashboard
B.Azure Policy's DeployIfNotExists effect
C.Adaptive network hardening
D.Just-In-Time VM access
AnswerB

Azure Policy's DeployIfNotExists effect is a true remediation mechanism because it automatically deploys a requested configuration whenever a non-compliant resource is created or updated. When assigned, it evaluates resources against the policy definition and, if the specified condition is not met, it runs an ARM template or deployment to bring the resource into compliance. For example, if a policy requires storage encryption to be enabled, DeployIfNotExists can automatically enable it by deploying the encryption configuration, thus achieving continuous and automated remediation without human interaction.

Why this answer

Azure Policy's DeployIfNotExists effect is the correct feature because it automatically deploys a resource configuration (such as enabling encryption on a storage account) when a policy evaluation detects non-compliance. This effect runs during policy evaluation and remediation tasks, ensuring that the resource is brought into compliance without manual intervention. It is specifically designed for automated remediation of non-compliant resources in Azure, aligning with the requirement to fix violations like missing encryption.

Exam trap

The trap here is that candidates may confuse the Regulatory compliance dashboard (a monitoring tool) with an automated remediation feature, overlooking that Azure Policy's DeployIfNotExists effect is the actual mechanism for enforcing and fixing compliance violations.

How to eliminate wrong answers

Option A is wrong because the Regulatory compliance dashboard is a reporting and monitoring tool that displays compliance status against standards (e.g., CIS, NIST), but it does not perform automated remediation of non-compliant resources. Option C is wrong because Adaptive network hardening provides recommendations to tighten network security group rules based on traffic patterns, not automated remediation of policy violations like encryption settings. Option D is wrong because Just-In-Time VM access reduces attack surface by controlling inbound traffic to VMs on demand, but it does not address policy compliance or resource configuration remediation.

420
MCQmedium

Your organization uses Microsoft Sentinel and Microsoft Defender for Cloud. You need to ensure that security alerts from Defender for Cloud are automatically ingested into Sentinel. What should you configure?

A.Enable diagnostic settings on the Defender for Cloud subscription.
B.Configure the 'Azure Activity' data connector.
C.Create an automation rule in Sentinel to fetch alerts from Defender for Cloud.
D.Add the 'Microsoft Defender for Cloud' data connector in Microsoft Sentinel.
AnswerD

The Microsoft Defender for Cloud data connector is the standard, supported method to ingest security alerts from Defender for Cloud into Microsoft Sentinel. It connects to your subscriptions and streams alerts into the SecurityAlert table, while optionally enabling incident creation and bi-directional synchronization of alert status. Once configured, your analytics rules and automation rules can then operate on those alerts directly.

Why this answer

The 'Microsoft Defender for Cloud' data connector in Microsoft Sentinel is specifically designed to ingest security alerts from Defender for Cloud into Sentinel. When you enable this connector, it automatically synchronizes alerts from all connected Defender for Cloud subscriptions, allowing you to investigate and respond to those alerts within Sentinel's unified security operations environment.

Exam trap

The trap here is that candidates often confuse diagnostic settings (which export logs) with data connectors (which import security alerts), leading them to choose Option A instead of the correct data connector in Option D.

How to eliminate wrong answers

Option A is wrong because enabling diagnostic settings on a Defender for Cloud subscription sends logs and metrics to a Log Analytics workspace, but it does not automatically ingest security alerts into Sentinel; diagnostic settings are used for resource logs, not for alert ingestion. Option B is wrong because the 'Azure Activity' data connector ingests subscription-level operational logs (e.g., create/delete resources), not security alerts from Defender for Cloud. Option C is wrong because automation rules in Sentinel trigger actions on already-ingested alerts or incidents; they cannot fetch or import alerts from external sources like Defender for Cloud.

421
Multi-Selecthard

Which THREE of the following are indicators of a potential pass-the-hash attack that a threat hunter should investigate in Microsoft Defender for Identity?

Select 3 answers
A.High volume of TGS requests from a single user
B.Multiple failed logon attempts followed by a successful logon from the same IP
C.Anomalous NTLM authentication from a domain controller
D.Event ID 4624 with LogonType 9 (NewCredentials) from a non-privileged account
E.Anomalous spike in CPU usage on domain controllers
AnswersB, C, D

A burst of failed logons immediately followed by a success from the same IP signals credential brute-forcing or hash reuse, matching the pass-the-hash pattern where stolen NTLM hashes authenticate without knowing the plaintext password. Defender for Identity surfaces this sequence as suspicious authentication behaviour worth hunting.

Why this answer

Option B is correct because a burst of failed logons immediately followed by a success from the same source IP is a classic credential-stuffing/brute-force precursor that often precedes or accompanies pass-the-hash, where stolen NTLM hashes are replayed to authenticate. Option C is correct because pass-the-hash relies on NTLM authentication, and anomalous NTLM traffic originating from a domain controller (which should normally use Kerberos for domain auth) is a strong Defender for Identity signal of hash replay or lateral movement. Option D is correct because LogonType 9 (NewCredentials) with Event ID 4624 indicates a process is using explicit alternate credentials via NTLM, which is exactly how tools like Mimikatz or PsExec execute pass-the-hash with a stolen hash rather than a password.

Option A is not correct because a high volume of TGS requests points to Kerberoasting or ticket-based attacks, not pass-the-hash, which uses NTLM rather than TGS tickets. Option E is not correct because CPU spikes on domain controllers are a generic performance/availability indicator and are not a specific behavioral signature of pass-the-hash in Defender for Identity.

422
Multi-Selectmedium

Which TWO tables in Microsoft Defender XDR advanced hunting provide information about user authentication events?

Select 2 answers
A.AlertInfo
B.AADSignInEventsBeta
C.EmailEvents
D.IdentityLogonEvents
E.DeviceNetworkEvents
AnswersB, D

AADSignInEventsBeta records Microsoft Entra ID sign-in events, capturing interactive and non-interactive authentication attempts with user, application, device and conditional access details. This directly satisfies the stem's requirement for user authentication data, complementing IdentityLogonEvents, which covers on-premises Active Directory authentication rather than cloud sign-ins.

Why this answer

Option B (AADSignInEventsBeta) is correct because this table in Microsoft Defender XDR advanced hunting contains Microsoft Entra ID (Azure AD) sign-in events, including interactive and non-interactive user authentication activity such as successful and failed sign-ins. Option D (IdentityLogonEvents) is correct because it records authentication events across on-premises identity services, including Active Directory and other identity providers surfaced through Defender for Identity, capturing logon and authentication activity for user accounts. Option A (AlertInfo) is not correct because it stores metadata about generated alerts rather than raw authentication events.

Option C (EmailEvents) is not correct because it holds email message and delivery information, not user sign-in data. Option E (DeviceNetworkEvents) is not correct because it contains network connection events from devices, not user authentication records.

423
MCQmedium

A SOC team uses Microsoft Sentinel and wants to ingest custom log events from an on-premises Linux application that writes to a local file. The team sets up the Log Analytics agent on the Linux server and configures a data connector. Which of the following is the necessary configuration step to collect the custom log file?

A.Create a Syslog data connector and specify the facility and severity to filter the application logs from /var/log.
B.Configure the Log Analytics agent to collect performance counters for the application process.
C.Use the Custom Logs feature in the Log Analytics workspace to specify the path to the application log file and define the log type name.
D.Deploy a Log Analytics gateway and configure the application to write directly to the gateway using the HTTP Data Collector API.
AnswerC

Using the Custom Logs feature in the Log Analytics workspace is the correct method for ingesting text-based application logs from a local file. In the workspace, you create a custom log by specifying the file path, assigning a log type name (e.g., AppLogs_CL), and providing a sample log file so the agent can determine the format. The Log Analytics agent then continuously tails the specified file and forwards each new line as a record into that custom table. This approach requires no modification to the application because the agent handles file monitoring directly.

Why this answer

The Custom Logs feature in the Log Analytics workspace is specifically designed to ingest text-based log files from on-premises Linux servers via the Log Analytics agent. You must specify the exact file path (e.g., /var/log/myapp.log) and define a custom log type name (e.g., MyApp_CL) to parse the file and send the data to a custom table in the Log Analytics workspace. This is the only method that directly collects custom application log files without requiring syslog or API-based ingestion.

Exam trap

The trap here is that candidates confuse syslog data connectors with custom log file collection, assuming any Linux log file can be ingested via syslog, when in fact syslog only handles logs sent to the syslog daemon, not arbitrary application files.

How to eliminate wrong answers

Option A is wrong because Syslog data connectors collect system logs using the syslog protocol (RFC 5424) from /var/log/syslog or /var/log/messages, not arbitrary application log files; they filter by facility and severity, not by file path. Option B is wrong because performance counters collect metrics like CPU or memory usage, not log file content; they are used for performance monitoring, not log ingestion. Option D is wrong because a Log Analytics gateway is a proxy for forwarding data to Azure, not a collection endpoint; the HTTP Data Collector API requires custom code in the application to send JSON payloads, not file-based collection.

424
MCQmedium

A security analyst is using Microsoft 365 Defender and discovers that a legitimate business application has been incorrectly blocked as malicious by an automated investigation. The analyst needs to unblock this application immediately so it can run on all endpoints in the organization. What action should the analyst take from the file's entity page in Microsoft 365 Defender?

A.Add an indicator to allow the file
B.Submit the file to Microsoft for analysis
C.Remove the existing indicator for the file
D.Restore the file from quarantine
AnswerA

Creating an allow indicator in Microsoft 365 Defender for the file's SHA-256 hash or certificate forces the security stack to treat that file as trusted across all onboarded devices. As a custom indicator, it overrides automated block verdicts from threat intelligence, so the file will no longer be blocked by antivirus, Cloud App Security, or other Microsoft Defender components. This is the only option that immediately and persistently changes the file's disposition within your tenant.

Why this answer

Adding an indicator to allow the file creates a custom indicator of compromise (IoC) in Microsoft 365 Defender that explicitly overrides the automated investigation's verdict. This action immediately permits the file to run on all endpoints in the organization by adding an 'allow' entry to the threat intelligence feed, which takes precedence over the automated detection logic.

Exam trap

The trap here is that candidates confuse the immediate unblocking action (adding an allow indicator) with the longer-term feedback process (submitting to Microsoft) or with post-remediation steps (restoring from quarantine), failing to recognize that custom indicators provide real-time override capability for automated investigations.

How to eliminate wrong answers

Option B is wrong because submitting the file to Microsoft for analysis is a feedback mechanism for improving detection algorithms, not an immediate remediation action to unblock a file that is already blocked. Option C is wrong because removing an existing indicator would only eliminate a previous custom rule; it does not address the current block caused by the automated investigation's verdict. Option D is wrong because restoring the file from quarantine applies only to files already quarantined on individual endpoints, not to preventing future blocks across all endpoints from the automated investigation.

425
MCQmedium

Your organization uses Microsoft Defender for Cloud Apps. You need to receive alerts when a user accesses a cloud app from a location that is not whitelisted. What should you configure?

A.Create a conditional access policy in Microsoft Entra ID.
B.Set up a session policy in Microsoft Defender for Cloud Apps.
C.Configure an access policy in Microsoft Defender for Cloud Apps.
D.Create an activity policy in Microsoft Defender for Cloud Apps.
AnswerD

Creating an activity policy in Microsoft Defender for Cloud Apps is correct because activity policies are purpose-built to monitor user activities and trigger alerts when specific conditions, such as an unusual location, are met. You can define rules based on attributes like IP address, geographic location, device, and activity type to generate alerts for investigation. This directly fulfills the requirement of alerting on location-based anomalies.

Why this answer

An activity policy in Microsoft Defender for Cloud Apps monitors user activities and can trigger alerts based on specific conditions, such as access from non-whitelisted locations. This policy type evaluates activities against defined criteria (e.g., IP address ranges) and generates alerts without blocking access, which matches the requirement to receive alerts.

Exam trap

The trap here is confusing activity policies (which alert) with access or session policies (which enforce controls), leading candidates to choose an option that blocks access instead of generating an alert.

How to eliminate wrong answers

Option A is wrong because a conditional access policy in Microsoft Entra ID controls access (e.g., block or require MFA) but does not generate alerts in Defender for Cloud Apps; it enforces access decisions at the authentication level. Option B is wrong because a session policy in Defender for Cloud Apps monitors and controls real-time app sessions (e.g., blocking downloads) but is designed for session-level control, not for alerting on location-based access. Option C is wrong because an access policy in Defender for Cloud Apps blocks or allows access based on conditions (e.g., location) but does not generate alerts; it enforces access control rather than notification.

426
Drag & Dropmedium

Order the steps to perform a threat hunting exercise using Microsoft 365 Defender advanced hunting.

Drag or tap steps into the slots.

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

Why this order

Threat hunting starts with a hypothesis, then querying, analyzing, and documenting results.

427
Multi-Selectmedium

Which TWO of the following are valid ways to automate incident response in Microsoft Sentinel?

Select 2 answers
A.Create a playbook using Azure Logic Apps.
B.Use Azure Functions to run a script.
C.Use PowerShell to modify incidents via API.
D.Use Microsoft Power Automate to create a flow.
E.Create an automation rule that triggers a playbook.
AnswersA, E

Creating a playbook using Azure Logic Apps is a native Microsoft Sentinel automation capability because Sentinel playbooks are implemented as Logic Apps workflows, purpose-built to run automated response actions on incidents and alerts. These workflows can be invoked directly from an incident's context or via an automation rule without any custom code or external infrastructure, making it a valid automation method.

Why this answer

Azure Logic Apps is the native workflow engine for Microsoft Sentinel playbooks, allowing security analysts to automate incident response actions such as blocking IPs, resetting passwords, or enriching alerts. Playbooks are triggered by automation rules or directly from incidents, and they leverage hundreds of connectors to integrate with external systems. This is the primary and recommended method for building automated response workflows in Sentinel.

Exam trap

The trap here is that candidates often confuse 'automation rule' with 'playbook' — an automation rule is the trigger condition, while a playbook is the action workflow; both are required for full automation, and the exam expects you to recognize that creating a playbook (A) and creating an automation rule that triggers a playbook (E) are the two valid steps in the process.

428
MCQhard

A threat hunter is using Microsoft Sentinel and Microsoft Defender XDR to hunt for a potential cross-domain attack where an attacker compromised an on-premises server and then used a privileged account to sign into Microsoft 365 from a new IP. The hunter wants to identify the server using a query that combines Windows Event Logs from the server with Microsoft 365 sign-in logs. Which approach should the hunter take to correlate the data?

A.Create a Sentinel watchlist of known attacker IPs and compare with server logs
B.Enable Sysmon on the server and use its Event ID 3 (network connection) to find the IP
C.Ingest Windows Security Event logs (Event ID 4624) from the server into a Log Analytics workspace, and join with SigninLogs on account name and timestamp
D.Use the DeviceLogonEvents table in Microsoft Defender XDR advanced hunting
AnswerC

Ingesting Windows Security Event ID 4624 into a Log Analytics workspace lets the hunter join those sign-in events with SigninLogs on account name and timestamp, correlating the on-premises server compromise with the Microsoft 365 sign-in from the new IP.

Why this answer

To correlate on-premises Windows logons with Microsoft 365 sign-ins, the hunter must ingest Windows Security Event ID 4624 (successful logon) from the server into a Log Analytics workspace, then join with the SigninLogs table on account name and timestamp. This is the standard Sentinel correlation pattern for cross-domain attacks. Event ID 4624 captures the account and logon type, enabling linkage to cloud sign-ins.

Exam trap

SC-200 often tests whether candidates know which table holds which data — the trap is choosing DeviceLogonEvents (Defender XDR) when the requirement is on-premises Windows Event Logs joined with SigninLogs in Sentinel.

How to eliminate wrong answers

Option A is wrong because a watchlist of attacker IPs does not correlate server logs with sign-in logs — it only enriches, and it assumes the IP is already known. Option B is wrong because Sysmon Event ID 3 records network connections, not logon events, and does not provide the account-to-signin correlation needed. Option D is wrong because DeviceLogonEvents in Defender XDR covers device logons from Defender for Endpoint, not on-premises Windows Security Event logs, and does not directly join with Microsoft 365 SigninLogs.

429
MCQeasy

A SOC analyst needs to investigate a potential data exfiltration incident involving a user uploading files to an external cloud storage service. Which Microsoft Sentinel data source would provide the MOST relevant information?

A.SigninLogs
B.CommonSecurityLog
C.AzureActivity
D.OfficeActivity
AnswerD

OfficeActivity is the correct log because it captures detailed audit records from Microsoft 365, including SharePoint, OneDrive, Exchange, and Teams. It records data-plane events such as FileUploaded, FileDownloaded, and FileAccess, which are directly relevant to identifying data exfiltration. For instance, an analyst can search for a user downloading many documents from a sensitive SharePoint site or uploading content to an external location, making this the authoritative source for investigating file-based exfiltration.

Why this answer

OfficeActivity (D) is the correct data source because it captures audit logs from Microsoft 365 services, including SharePoint Online, OneDrive for Business, and Exchange Online. These logs record file uploads, downloads, and sharing events, making them the most relevant for investigating data exfiltration to external cloud storage services like OneDrive or SharePoint.

Exam trap

The trap here is that candidates often confuse AzureActivity (resource management logs) with user activity logs, or assume SigninLogs contain file-level actions, when in fact only OfficeActivity provides the granular file upload events needed for data exfiltration investigations.

How to eliminate wrong answers

Option A is wrong because SigninLogs only record authentication events (successful/failed logins) and do not contain file-level activity details. Option B is wrong because CommonSecurityLog is used for ingesting syslog or CEF-format logs from on-premises security appliances (e.g., firewalls, proxies) and does not natively capture Microsoft 365 cloud storage events. Option C is wrong because AzureActivity logs track resource management operations in Azure (e.g., creating VMs, modifying subscriptions) and do not include user file uploads to cloud storage services.

430
MCQeasy

A security analyst is investigating a suspicious process on an endpoint and needs to see all network connections initiated by that process. The analyst knows the ProcessId and DeviceName. Which advanced hunting table in Microsoft 365 Defender should the analyst query to retrieve network connection details associated with this process?

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

DeviceNetworkEvents records each connection initiated on a device, capturing the initiating ProcessId, DeviceName, remote IP, port and protocol. Filtering on the known ProcessId and DeviceName returns exactly the process's outbound and inbound network activity, which no other hunting table provides at that granularity.

Why this answer

The DeviceNetworkEvents table in Microsoft 365 Defender is specifically designed to capture network connection events, including source and destination IP addresses, ports, protocols, and the initiating process ID (ProcessId). By querying this table with the known ProcessId and DeviceName, the analyst can retrieve all network connections initiated by that process, making it the correct choice for this investigation.

Exam trap

The trap here is that candidates often confuse DeviceProcessEvents (which shows process creation) with DeviceNetworkEvents (which shows network activity), assuming process events include network details, but Microsoft Defender XDR separates these concerns into distinct tables for granular hunting.

How to eliminate wrong answers

Option A is wrong because DeviceProcessEvents logs process creation and termination events, not network connections; it would show the process start but not its network activity. Option C is wrong because DeviceEvents is a generic table that includes various security events (e.g., Windows Defender alerts, file modifications) but does not specifically contain network connection details with process-to-connection mapping. Option D is wrong because IdentityLogonEvents tracks user authentication and logon events (e.g., successful/failed logins, Kerberos tickets) and has no relation to process-level network connections.

431
Multi-Selecteasy

Which TWO of the following are required to enable Microsoft Sentinel UEBA (User and Entity Behavior Analytics)?

Select 2 answers
A.Enable UEBA in the Microsoft Sentinel workspace settings.
B.Integrate Microsoft Defender for Cloud Apps.
C.Purchase a separate UEBA license.
D.Configure Azure Key Vault to store UEBA data.
E.Ingest Microsoft Entra ID sign-in logs and audit logs.
AnswersA, E

UEBA is disabled by default in Microsoft Sentinel; you must explicitly turn it on via the workspace settings under Entity behavior. This setting activates the machine learning-based analytics that profile entities and surface anomalous activity. Without toggling this on, UEBA features remain dormant even if other data sources are connected.

Why this answer

UEBA must be explicitly enabled in the Microsoft Sentinel workspace settings under the 'Entity behavior analytics' blade. This activation allows Sentinel to start profiling user and entity behaviors using built-in machine learning models. Without this toggle, UEBA remains disabled regardless of other configurations.

Exam trap

The trap here is that candidates often assume UEBA requires a separate license or integration with a specific security product like Defender for Cloud Apps, when in fact it is a built-in feature of Sentinel that only needs to be enabled and fed with appropriate log sources.

432
MCQmedium

Refer to the exhibit. You are reviewing a Microsoft Sentinel scheduled analytics rule configured as above. An incident was created for multiple alerts triggering within a 5-hour window. The SOC team needs to investigate each alert separately because they involve different user accounts. What should the analyst do to ensure each alert generates a separate incident?

A.Change the matchingMethod to 'AnyAlert'.
B.Set 'enabled' to false under groupingConfiguration.
C.Set 'reopenClosedIncident' to true.
D.Change the lookbackDuration to PT0H.
AnswerB

Setting enabled to false under groupingConfiguration completely disables the alert grouping engine for that analytics rule. With grouping disabled, Sentinel no longer applies entity-matching or lookback logic, and each individual alert will generate its own independent incident. This is the only direct way to guarantee a one-to-one mapping from alert to incident, which is exactly the desired behavior.

Why this answer

Setting 'enabled' to false under groupingConfiguration disables alert grouping entirely. When grouping is disabled, each individual alert that triggers the scheduled rule will generate its own separate incident, allowing the SOC team to investigate alerts involving different user accounts independently.

Exam trap

The trap here is that candidates often confuse disabling grouping with changing the matchingMethod or lookbackDuration, thinking those options separate alerts, when in fact only setting 'enabled' to false under groupingConfiguration achieves true per-alert incident creation.

How to eliminate wrong answers

Option A is wrong because changing the matchingMethod to 'AnyAlert' still groups alerts into a single incident if they fall within the same time window; it only changes how alerts are matched within the group, not whether grouping occurs. Option C is wrong because setting 'reopenClosedIncident' to true reopens a closed incident when a new alert matches it, but does not prevent grouping of multiple alerts into one incident. Option D is wrong because changing the lookbackDuration to PT0H (zero hours) would still group alerts that trigger at the exact same time, and does not disable the grouping mechanism; it only reduces the time window for grouping.

433
MCQhard

Your organization uses Microsoft Sentinel with UEBA (User and Entity Behavior Analytics) enabled. The SOC team notices that UEBA is not generating any anomalies for a specific user group. What is the most likely cause?

A.The user group is excluded from Identity Protection.
B.The data history for that user group is less than the required baseline period.
C.The user group is not being monitored by any data connector.
D.The analytics rules for UEBA are not enabled.
AnswerB

UEBA builds behavioural baselines from historical activity before it can flag deviations. A user group with insufficient data history has no established normal pattern, so the analytics engine cannot compute anomalies for it regardless of connector health or licensing state.

Why this answer

UEBA in Microsoft Sentinel requires a baseline period of historical data (typically 14 days minimum, often up to 30 days) before it can establish normal behavior patterns and generate meaningful anomalies. If a user group was recently added or their identity data has only been ingested for a short time, Sentinel lacks the behavioral baseline needed to flag deviations, so no anomalies appear. This is expected behavior, not a misconfiguration.

Exam trap

SC-200 often tests the UEBA baseline requirement, tricking candidates into blaming missing data connectors or disabled analytics rules when the real issue is simply insufficient historical data for behavioral learning.

How to eliminate wrong answers

Option A is wrong because Identity Protection exclusions affect risk detections in Entra ID, not Sentinel UEBA anomaly generation — these are separate systems. Option C is wrong because if no data connector were feeding identity logs, UEBA would show no data at all rather than selectively failing for one group; also UEBA depends on Azure AD/Entra sign-in and audit logs, which are typically tenant-wide. Option D is wrong because UEBA analytics are built-in and enabled by the UEBA toggle in Sentinel settings; there is no separate 'analytics rules for UEBA' that must be enabled per group.

434
MCQmedium

Your organization has a Microsoft Sentinel workspace that ingests logs from Azure resources, Microsoft 365, and third-party firewalls. You need to ensure that data retention for Azure Activity logs complies with a regulatory requirement of 3 years, while keeping costs low for other data types. What should you do?

A.Use the Archive tier for Azure Activity logs and set the total retention period to 3 years.
B.Set the workspace retention to 3 years.
C.Configure a data retention policy on the AzureActivity table to 3 years.
D.Enable Basic Logs plan on the AzureActivity table.
AnswerC

This is correct because table-level retention policies let you extend or shorten the retention for a specific table, here the AzureActivity table, to meet 3-year compliance for Azure Activity logs without affecting other tables' data lifecycle. Since the policy targets only that table's logs, it balances compliance requirements with cost optimization while keeping the data natively queryable in the Log Analytics workspace.

Why this answer

Azure Sentinel allows you to configure a custom retention policy on a specific table (e.g., AzureActivity) to retain data for up to 2 years (or longer with Archive tier) independently of the workspace's default retention. This meets the 3-year regulatory requirement for Azure Activity logs without increasing retention costs for other data types, as the workspace default can remain shorter.

Exam trap

The trap here is that candidates often confuse workspace-level retention with table-level retention, assuming that setting the workspace retention to 3 years is the only way to meet the requirement, when in fact table-level policies allow granular control without affecting other data types.

How to eliminate wrong answers

Option A is wrong because the Archive tier is used for long-term, low-cost storage after an initial retention period (typically 30 days for Activity logs), but it does not by itself set the total retention to 3 years; you must also configure a table-level retention policy to define the total retention period, and the Archive tier alone does not guarantee compliance without that policy. Option B is wrong because setting the workspace retention to 3 years would apply that retention to all data types in the workspace, increasing costs unnecessarily for non-Activity logs that do not require 3-year retention. Option D is wrong because enabling Basic Logs plan on the AzureActivity table reduces ingestion costs but does not change the retention period; it still requires a separate retention policy to meet the 3-year requirement.

435
Multi-Selecthard

Which TWO are required to enable Microsoft Sentinel to use AI-generated incident summaries?

Select 2 answers
A.The Security Reader role assigned to the user
B.Microsoft Copilot for Security enabled
C.An Azure OpenAI service instance deployed
D.A Log Analytics workspace with a premium pricing tier
E.A Power BI Pro license
AnswersA, B

The Security Reader role is a least-privilege RBAC role that grants read-only access to Microsoft Sentinel resources, including incidents, alerts, and the AI-generated summaries. Without this role, Microsoft Copilot for Security may be enabled, but the user will see an authorization error rather than the Copilot-derived narrative in the incident pane. This role is required at minimum to retrieve incident details that Copilot's summarization pipeline consumes and displays.

Why this answer

Microsoft Sentinel's AI-generated incident summaries require Microsoft Copilot for Security to be enabled, as this feature leverages Copilot's natural language processing capabilities to summarize incidents. Additionally, the user must have the Security Reader role assigned to access and view these summaries within Sentinel, ensuring proper permissions for security data.

Exam trap

The trap here is that candidates often assume a separate Azure OpenAI service or premium Log Analytics tier is needed, but Microsoft Copilot for Security is a standalone licensed service that handles AI processing without requiring those additional resources.

436
MCQmedium

You are managing a Microsoft Sentinel environment that ingests data from multiple sources: Microsoft 365, Azure Activity, and custom logs via AMA. The SOC manager has requested that all security events from Windows servers be collected and stored for 90 days for compliance purposes. You have configured the Windows Security Events via AMA data connector to collect all events (Event ID 4624, 4625, etc.) and set the workspace retention to 90 days. After a week, you notice that the daily ingested volume is higher than expected, exceeding the budget. You analyze the data and find that many low-severity informational events are being ingested, such as Event ID 5156 (Windows Filtering Platform allowed connection). The manager confirms that only security-relevant events are needed. What should you do to reduce ingestion volume while still meeting compliance requirements?

A.Reduce the workspace retention period to 30 days to lower storage costs.
B.Configure the Azure Activity data connector to filter out low-severity events.
C.Modify the data collection rule (DCR) for the Windows Security Events connector to use a custom XPath query that excludes informational events (e.g., exclude Event ID 5156).
D.Disable the AMA-based connector and use the legacy MMA-based connector instead.
AnswerC

Filtering at the data collection rule with a custom XPath query stops Event ID 5156 and similar informational events before ingestion, directly cutting volume and cost. Because the DCR sits between the AMA agent and the workspace, excluded events never reach Microsoft Sentinel, while security-relevant events still land and satisfy the 90-day retention requirement.

Why this answer

The AMA connector uses data collection rules (DCRs) that allow you to filter events based on custom XPath queries. By creating a custom XPath query that excludes informational events like Event ID 5156, you can reduce ingestion volume while still collecting security-relevant events (e.g., 4624, 4625) for the required 90-day retention. Option A is incorrect because reducing the workspace retention to 30 days would violate the compliance requirement for 90 days.

Option B is incorrect because the Azure Activity data connector collects Azure resource logs, not Windows security events. Option D is incorrect because the legacy MMA connector is deprecated and does not provide the same filtering capabilities; AMA is the recommended solution.

437
MCQhard

You are a SOC analyst using Microsoft Sentinel. You have a scheduled analytics rule that generates incidents from KQL queries. Recently, incidents are being created but automatically closed within minutes without any actions taken. You suspect a configuration issue. What should you check first?

A.Verify the 'Alert grouping' settings in the analytics rule; they might be grouping alerts incorrectly.
B.Check if the analytics rule has a 'Suppression' setting enabled that causes the incident to close.
C.Review the incident automation rules that might have a 'Close incident' action triggered by a condition.
D.Examine the entity mapping configuration; it might be causing the incident to close automatically.
AnswerC

Incident automation rules in Microsoft Sentinel run automatically upon incident creation or update, and they can include a 'Close incident' action when defined conditions are met. For example, a rule with a condition like 'Alert severity equals Low' will close any newly created matching incident without human intervention. Reviewing these rules is the correct approach because they are the primary native mechanism that automatically closes incidents based on incident properties.

Why this answer

Incident automation rules in Microsoft Sentinel can be configured to automatically close incidents when specific conditions are met, such as a related alert being resolved or a playbook completing. Since the incidents are being closed within minutes without manual intervention, an automation rule with a 'Close incident' action is the most likely cause, as it directly triggers closure based on conditions. Checking this first aligns with the SOC analyst's need to identify automated actions that could prematurely close incidents.

Exam trap

The trap here is that candidates confuse 'suppression' (which stops alert creation) with 'automation rules' (which can close incidents), leading them to choose Option B instead of recognizing that suppression does not affect existing incidents.

How to eliminate wrong answers

Option A is wrong because 'Alert grouping' settings control how alerts are combined into incidents, not how incidents are closed; incorrect grouping might create duplicate or merged incidents but does not automatically close them. Option B is wrong because 'Suppression' settings in an analytics rule prevent the rule from running or generating alerts for a specified period after an incident is created, but they do not close existing incidents; suppression stops new alerts, not closes incidents. Option D is wrong because entity mapping configuration maps entities (like users or IPs) to alerts for correlation and investigation, but it has no mechanism to automatically close incidents; it affects data enrichment, not incident lifecycle.

438
MCQmedium

You are managing a Microsoft Defender XDR environment. The security team wants to receive email notifications when a new incident is created with severity 'High' or 'Medium'. They also want to ensure that notifications are sent only for incidents that are not automatically resolved by AIR. What should you configure?

A.Create a playbook in Microsoft Sentinel that sends an email when an incident is created.
B.Configure an automation rule in Microsoft Sentinel to send email notifications.
C.Create an email notification rule in Microsoft Defender XDR with conditions for severity and status set to 'Active'.
D.Configure alert service settings in the Microsoft 365 Defender portal to send emails for high and medium severity alerts.
AnswerC

Email notification rules in Microsoft Defender XDR are the native mechanism for sending email alerts when incidents meet specific criteria, such as severity (high, medium) and status (New, Active, Resolved). To receive notifications for open investigations, you would set the status condition to 'Active' and select the desired severity levels, then specify the recipient address and notification frequency. This rule is managed directly in Microsoft 365 Defender portal under Settings > Microsoft 365 Defender > Email notifications > Incidents, making it the intended feature for this scenario. It operates independently of Microsoft Sentinel and covers the full scope of Defender XDR incidents.

Why this answer

Microsoft Defender XDR allows you to create email notification rules specifically for incidents, with conditions to filter by severity (e.g., High, Medium) and status (e.g., Active). This ensures notifications are sent only for new incidents that are not automatically resolved by AIR, as AIR-resolved incidents would have a status of 'Resolved' or 'Redirected', not 'Active'.

Exam trap

The trap here is confusing Microsoft Sentinel's incident management (which uses automation rules and playbooks) with Microsoft Defender XDR's native incident notification system, leading candidates to select options that apply to Sentinel rather than Defender XDR.

How to eliminate wrong answers

Option A is wrong because Microsoft Sentinel playbooks are designed for automated response actions, not for configuring native email notifications within Defender XDR; they would require additional licensing and integration, and do not directly address the requirement to exclude AIR-resolved incidents. Option B is wrong because automation rules in Microsoft Sentinel operate on Sentinel incidents, not on Defender XDR incidents; the requirement is specifically for Defender XDR incident notifications. Option D is wrong because alert service settings in the Microsoft 365 Defender portal send notifications for alerts, not incidents, and they lack the granularity to filter by incident status (Active vs.

Resolved) or to exclude AIR-resolved incidents.

439
MCQhard

You are a threat hunter at Fabrikam. You suspect that an attacker is using the Win32_Process class to create a process on a remote workstation via WMI. You need to write an advanced hunting query in Microsoft Defender XDR to detect this activity. Which table should you query to find WMI process creation events?

A.DeviceProcessEvents
B.DeviceEvents
C.DeviceNetworkEvents
D.DeviceRegistryEvents
AnswerB

DeviceEvents includes various event types, such as WmiProcessCreate, which specifically logs process creation via WMI. This table captures the WMI provider host process, the command line, and the remote caller, allowing you to detect remote WMI process creation. Querying DeviceEvents for ActionType == 'WmiProcessCreate' is the correct approach for this scenario.

Why this answer

To detect WMI process creation, you need to query a table that specifically logs WMI activity. In Microsoft Defender XDR advanced hunting, the DeviceEvents table includes an ActionType called WmiProcessCreate that captures process creation via WMI, including the remote caller and command line. Filtering DeviceEvents for this ActionType will surface the relevant events.

Exam trap

The trap here is assuming that all process creation events are in DeviceProcessEvents, but WMI-specific process creation is logged in DeviceEvents with a distinct ActionType.

440
Multi-Selecthard

Which THREE data sources in Microsoft Sentinel can be used to detect lateral movement in a network? (Choose three.)

Select 3 answers
A.DNS logs
B.Microsoft Defender for Endpoint (device events)
C.Windows Event Logs (Event ID 5140)
D.Windows Security Events (Event ID 4624)
E.Microsoft Entra ID sign-in logs
AnswersB, C, D

Microsoft Defender for Endpoint's device events provide deep host telemetry, including process creation, command lines, network connections, and local account logon events. This enables detection of lateral movement techniques such as PsExec, SMB/WMI remote execution, and RDP sessions at the endpoint level. Because it correlates specific processes with network activity and the originating host, it is a powerful source for hunting lateral movement in Sentinel.

Why this answer

Microsoft Defender for Endpoint (MDE) provides detailed device-level events, including process creation, network connections, and logon sessions. These telemetry points are critical for detecting lateral movement because they reveal anomalous remote logins, service creation, or file execution on multiple endpoints, which are hallmarks of an attacker moving laterally.

Exam trap

The trap here is that candidates often select DNS logs (Option A) thinking they can detect lateral movement via unusual internal DNS queries, but DNS logs lack the authentication and process execution context required to confirm lateral movement, making them a supporting data source at best.

441
MCQhard

A security analyst is investigating a complex incident in Microsoft 365 Defender that involves multiple stages: a phishing email, credential theft, and lateral movement. The analyst wants to view a visual representation of the attack chain, showing how alerts and entities are related. Which feature should the analyst use?

A.Incident graph
B.Advanced hunting
C.Automated investigation
D.Alert timeline
AnswerA

The incident graph is a dedicated visualization feature in Microsoft 365 Defender that maps the entire attack chain as nodes and edges, showing how alerts, entities, and observed events relate to each other. It provides an interactive, graphical representation that lets analysts quickly trace the progression of an attack from initial access to impact, making it the correct choice for understanding complex incident relationships.

Why this answer

The incident graph in Microsoft 365 Defender provides a visual, interactive map of the entire attack chain, linking alerts, entities (such as users, devices, and IPs), and suspicious activities. This allows the analyst to see the progression from the phishing email to credential theft and lateral movement in a single view, making it the correct tool for understanding complex, multi-stage incidents.

Exam trap

The trap here is that candidates often confuse the alert timeline (a simple chronological list) with the incident graph (a relational visualization), or they assume Advanced hunting is the only way to correlate events, missing the purpose-built visual tool for attack chain analysis.

How to eliminate wrong answers

Option B (Advanced hunting) is wrong because it is a query-based tool for searching raw data across tables (e.g., EmailEvents, IdentityLogonEvents) and does not provide a pre-built visual representation of the attack chain; it requires the analyst to manually construct queries to correlate events. Option C (Automated investigation) is wrong because it focuses on automatically running playbooks and remediation actions on alerts, not on visualizing the relationships between alerts and entities in an attack chain. Option D (Alert timeline) is wrong because it shows a chronological list of alerts for an incident but lacks the graphical entity-relationship mapping that the incident graph provides, making it insufficient for understanding complex lateral movement paths.

442
MCQhard

Refer to the exhibit. You are reviewing a custom hunting query in Microsoft Defender XDR. The query aims to identify devices with more than 100 outbound connections in the last 30 days to IPs that appear in active threat intelligence indicators. However, the query returns no results. What is the most likely cause?

A.The RemoteIPType filter for 'Public' excludes all internal IPs, but devices connect to internal IPs mostly.
B.The join on RemoteIP and NetworkIP is mismatched because one is IPv4 and the other IPv6.
C.The ThreatIntelligenceIndicator table does not contain any indicators with an Active status that match the remote IPs.
D.The ConnectionCount threshold of 100 is too high; most devices do not exceed this.
AnswerC

This is the most plausible reason: in a KQL inner join, only rows with matching keys are returned. If the ThreatIntelligenceIndicator table contains no indicators with an Active status that equal any of the observed RemoteIP values, the joined result set will be empty by design. Indicators that are expired or have another status are filtered out, and the TI lookup data may simply not include the IPs the devices are connecting to. This aligns with the classic behavior where an inner join produces zero rows when the right side lacks matches.

Why this answer

The most likely cause is that the ThreatIntelligenceIndicator table does not contain any active indicators that match the remote IPs from the DeviceNetworkEvents. The query uses an inner join between DeviceNetworkEvents and ThreatIntelligenceIndicator on RemoteIP and NetworkIP. If there are no matching indicators, the join produces zero results.

Option A is incorrect because filtering for public IPs is correct for outbound connections to the internet. Option B is incorrect because IP version mismatch would cause a join failure, but the query would still return results if the version matched. Option D is incorrect because the threshold of 100 connections may be high, but if there were matching indicators, some devices would return results.

443
Multi-Selecthard

Which THREE components are required to implement a threat intelligence feed in Microsoft Sentinel using the Threat Intelligence - TAXII data connector?

Select 3 answers
A.Root collection ID
B.A Log Analytics workspace with Microsoft Sentinel enabled
C.TAXII server URL
D.API key for the TAXII server
E.A watchlist named 'ThreatIntelligenceIndicators'
AnswersA, C, D

The Root collection ID is a mandatory parameter for the Microsoft Defender Threat Intelligence (MDTI) TAXII connector. It uniquely identifies the specific collection of threat intelligence indicators to be ingested, as a single TAXII 2.0 server can host multiple collections. Without this ID, the connector cannot determine which feed to pull from, even if the server URL and API key are correctly configured. This value is typically provided in the form of a UUID and is required to establish a successful data pull.

Why this answer

The root collection ID is a required component for the Threat Intelligence - TAXII data connector because it identifies the specific collection of threat indicators on the TAXII server. Without this ID, Microsoft Sentinel cannot determine which set of indicators to ingest, as a single TAXII server may host multiple collections. The connector uses the root collection ID to query the correct STIX/TAXII endpoint and retrieve the relevant threat intelligence feed.

Exam trap

The trap here is that candidates often confuse the prerequisite (a Log Analytics workspace with Sentinel enabled) with a required component for the connector, or mistakenly think a watchlist is needed to store ingested threat indicators, when in fact the indicators are stored directly in the ThreatIntelligenceIndicator table.

444
MCQhard

Your organization uses Microsoft Defender XDR and has a custom detection rule that queries DeviceProcessEvents for suspicious PowerShell commands. You notice that the rule is generating a high number of false positives. You need to reduce false positives while still detecting real threats. What should you do?

A.Add a condition to exclude processes signed by trusted certificates or from known IT admin accounts.
B.Disable the rule and create a new rule with a different MITRE technique.
C.Increase the lookback period from 7 to 30 days.
D.Modify the rule to set the severity to 'Informational'.
AnswerA

Adding an exclusion condition that filters out processes signed by trusted certificate publishers or running from known IT admin accounts directly targets the root cause of false positives, because many legitimate administration tools (e.g., PsExec, remote management scripts) share behavioral indicators with malicious activity. This allowlist-based approach preserves detection coverage for unsigned or anomalous processes while suppressing benign alerts that security analysts would otherwise need to triage. It is a standard tuning practice for custom detection rules in Microsoft Defender XDR.

Why this answer

Adding a condition to exclude processes signed by trusted certificates or from known IT admin accounts directly reduces false positives by filtering out legitimate administrative activity. Custom detection rules in Microsoft Defender XDR allow you to refine queries with additional conditions, such as excluding specific signers or accounts, which preserves detection of malicious PowerShell commands while ignoring benign ones.

Exam trap

The trap here is that candidates may think lowering severity or changing the detection technique reduces false positives, but only refining the query logic (e.g., excluding trusted signers or accounts) directly addresses the root cause of false alerts.

How to eliminate wrong answers

Option B is wrong because disabling the rule and creating a new rule with a different MITRE technique does not address the false positive issue; it changes the detection focus rather than refining the existing query. Option C is wrong because increasing the lookback period from 7 to 30 days would only expand the data window, potentially increasing false positives and not filtering out legitimate activity. Option D is wrong because setting the severity to 'Informational' merely lowers the alert priority but does not reduce the number of false positives; the rule would still generate the same volume of alerts.

445
Multi-Selecthard

During a ransomware incident, Microsoft Defender for Cloud Apps alerts indicate that a user is uploading large volumes of data to an external cloud storage provider not approved by your organization. Which two actions should you take first? (Choose two.)

Select 2 answers
A.Block the unapproved cloud storage app
B.Suspend the user's account
C.Notify the user about the policy violation
D.Initiate a legal hold on the user's data
AnswersA, B

Blocking the unapproved cloud storage app in Microsoft Defender for Cloud Apps immediately enforces a block policy that prevents any session or upload to that app, cutting off the attacker's exfiltration channel. This is a direct containment action that stops ransomware from spreading via file uploads to shadow IT services. By applying a session policy or app governance control, you terminate the active data movement without waiting for user awareness.

Why this answer

Blocking the unapproved cloud storage app in Microsoft Defender for Cloud Apps immediately stops the ongoing data exfiltration by preventing further uploads to that external provider. This is a direct, real-time containment action that leverages Defender for Cloud Apps's app governance and conditional access controls to enforce organizational policies without disrupting the user's access to other resources.

Exam trap

The trap here is that candidates often choose only one containment action (e.g., blocking the app) and overlook the need to also suspend the user account, failing to recognize that the user may continue exfiltration via other unapproved apps or methods if only the app is blocked.

446
MCQhard

A security analyst is preparing to use a Jupyter notebook for threat hunting in Microsoft Sentinel. Which of the following sequences of actions is correct to start executing the notebook?

A.Provision compute → Clone Sentinel notebooks → Connect to workspace → Execute cells
B.Clone Sentinel notebooks → Provision compute → Connect to workspace → Execute cells
C.Connect to workspace → Provision compute → Clone Sentinel notebooks → Execute cells
D.Provision compute → Connect to workspace → Clone Sentinel notebooks → Execute cells
AnswerA

This sequence follows Microsoft's recommended readiness path for Sentinel notebooks: the Azure ML compute instance must be created first because Jupyter kernels, the Python environment, and MSTICpy dependencies are all bound to that compute target. Once the compute is live, cloning the official Sentinel notebooks populates the workspace with query templates while ensuring the files are accessible to that same compute. Only then is the notebook able to establish an authenticated connection to the Log Analytics/Sentinel workspace, normally via MSTICpy's `nbinit` or a Microsoft Entra sign-in, before any cells are executed.

Why this answer

The correct sequence to start executing a Jupyter notebook for threat hunting in Microsoft Sentinel is to first provision compute (i.e., create a compute instance in Azure Machine Learning), then clone the Sentinel notebooks from the official GitHub repository, connect to the Sentinel workspace using the msticpy library, and finally execute the cells. This order ensures the compute environment is ready before loading the notebooks and establishing the workspace connection.

Exam trap

The trap here is that candidates often assume the workspace connection should be established first (as in typical cloud workflows), but in Sentinel notebooks, the compute environment must be ready before any authentication or file operations can occur.

How to eliminate wrong answers

Option B is wrong because cloning Sentinel notebooks before provisioning compute would fail, as there is no compute environment to store or run the notebooks. Option C is wrong because connecting to the workspace before provisioning compute is impossible without a compute instance to authenticate and establish the connection. Option D is wrong because connecting to the workspace before cloning the notebooks would result in missing notebook files to execute, and the connection step requires the notebooks to be present for context.

447
MCQmedium

Your SOC team needs to ensure that all high-severity Microsoft Sentinel incidents are automatically assigned to the senior analyst on call. The team uses Microsoft Teams for communication. Which configuration should you implement?

A.Configure an analytics rule to set the incident owner to the senior analyst and enable Teams integration in Sentinel settings.
B.Create a playbook that reassigns incidents and posts to Teams, and attach it to an automation rule triggered by high-severity incidents.
C.Create a workbook that filters high-severity incidents and configure a Teams webhook in the workbook settings.
D.Create an automation rule that runs when an incident is created with severity High, sets the owner to the senior analyst, and then runs a playbook to post a message to Teams.
AnswerD

An automation rule can be configured to trigger 'When incident is created' and apply a condition for Severity equals High, then perform actions such as setting the owner to the senior analyst and running a playbook. The playbook, typically an Azure Logic App with a Microsoft Teams connector, can post an adaptive card message to a Teams channel. This combined approach correctly satisfies both requirements: automated ownership assignment and proactive notification, making it the right solution.

Why this answer

Automation rules in Microsoft Sentinel can directly set the incident owner when an incident is created, and then trigger a playbook to post a message to Microsoft Teams. This two-step configuration ensures high-severity incidents are automatically assigned to the senior analyst on call and the SOC team is notified via Teams without manual intervention.

Exam trap

The trap here is that candidates often assume a playbook alone can handle both assignment and notification, but Microsoft Sentinel automation rules are the correct mechanism for setting incident properties like owner, while playbooks are best suited for external actions like posting to Teams.

How to eliminate wrong answers

Option A is wrong because analytics rules do not have the capability to set the incident owner; that is a function of automation rules or playbooks, and enabling Teams integration in Sentinel settings only provides basic connectivity, not automated assignment. Option B is wrong because while a playbook can reassign incidents and post to Teams, attaching it to an automation rule triggered by high-severity incidents would require the playbook to also set the owner, but the automation rule itself can set the owner more efficiently and reliably without relying on the playbook for assignment. Option C is wrong because workbooks are visualization tools that do not modify incident properties or trigger actions; configuring a Teams webhook in a workbook would only allow manual export or refresh, not automated incident assignment or notification.

448
Matchingmedium

Match each Microsoft 365 Defender workload to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Protects endpoints from cyber threats

Safeguards email and collaboration tools

Detects identity-based attacks using Active Directory signals

Provides visibility and control over cloud apps

Secures multicloud and hybrid environments

Why these pairings

Microsoft 365 Defender includes four main workloads: Defender for Endpoint (endpoint security), Defender for Office 365 (email & collaboration), Defender for Identity (on-premises AD security), and Defender for Cloud Apps (cloud app security). Common confusions involve mixing up definitions between these workloads.

449
MCQmedium

An incident in Microsoft Defender XDR involves a device that is suspected to be infected with ransomware. The device is online and actively encrypting files. Which action should you take to contain the threat?

A.Isolate the device from the network
B.Disable the user's account
C.Run a full antivirus scan on the device
D.Collect a memory dump from the device
AnswerA

Device isolation in Microsoft Defender for Endpoint severs all external network connections while maintaining a secure channel to the MDE cloud so the security team can continue monitoring and issuing commands. This containment action immediately stops the attacker from using the compromised host to propagate over SMB, PsExec, or other protocols, and prevents ransomware from encrypting remote file shares. Isolation is reversible once forensic collection is complete, making it the correct first step in the incident response workflow.

Why this answer

Isolating the device from the network (Option A) is the correct immediate action because it stops the ransomware from communicating with its command-and-control (C2) server and prevents further lateral movement or encryption of network shares. In Microsoft Defender for Endpoint, device isolation blocks all inbound and outbound traffic at the OS kernel level, while still allowing the device to remain online for forensic analysis and remediation. This containment strategy is critical when the device is actively encrypting files, as it halts the attack's spread without losing the ability to investigate or remediate.

Exam trap

The trap here is that candidates often choose 'Run a full antivirus scan' (Option C) because they think detection must precede containment, but the SC-200 exam emphasizes that immediate containment (isolation) is the priority when active encryption is observed, not scanning.

How to eliminate wrong answers

Option B is wrong because disabling the user's account does not stop the ransomware process already running on the device; the malware will continue encrypting files under the system context or cached credentials. Option C is wrong because running a full antivirus scan takes significant time and may not stop the active encryption in progress, allowing the ransomware to complete its damage before detection. Option D is wrong because collecting a memory dump is a forensic step that does not contain the threat; it captures evidence but leaves the device online and actively encrypting, which worsens the incident.

450
MCQmedium

Based on the ARM template snippet, what is the purpose of this analytics rule?

A.To detect multiple failed logon attempts within a time window
B.To detect brute force attacks on user accounts
C.To detect successful logins by account
D.To detect account lockouts
AnswerB

Multiple failed logons indicate brute force.

Why this answer

The query counts failed logon events (EventID 4625) and triggers when the count exceeds a threshold (e.g., 5) within a time window, indicating multiple failed attempts. Option B is correct because a high count of failed logon attempts from the same account or IP is a classic sign of a brute force attack. Option C is incorrect because EventID 4625 is a failed logon, not a successful login.

Option D is incorrect because the query does not include EventID 4740 (account lockout) and does not check for lockouts.

Page 5

Page 6 of 18

Page 7