Courseiva

Microsoft Security Operations Analyst SC-200 (SC-200) — Questions 676–750

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

Page 9

Page 10 of 18

Page 11
676
MCQeasy

A company wants to protect Azure virtual machines from brute force attacks by allowing remote desktop protocol (RDP) access only when explicitly requested and approved. Which Microsoft Defender for Cloud feature should they enable?

A.Adaptive network hardening
B.Just-in-time VM access
C.File integrity monitoring
D.Security recommendations
AnswerB

Just-in-time VM access in Microsoft Defender for Cloud eliminates standing inbound exposure by locking down management ports with deny rules, and only transiently adds an allow rule when an authenticated, authorized request is made for a defined source IP, protocol, and time window. This reduced attack surface directly mitigates brute-force attempts because SSH/RDP ports remain closed to the public internet until a legitimate user specifically requests access.

Why this answer

Just-in-time (JIT) VM access in Microsoft Defender for Cloud locks down inbound traffic to Azure VMs by default, opening RDP (port 3389) only when a user requests access and is approved via Azure AD and Azure Policy. This directly addresses the requirement to allow RDP only on explicit request and approval, mitigating brute force attacks by reducing the attack surface.

Exam trap

The trap here is that candidates confuse Adaptive network hardening (which also involves NSG rules) with JIT VM access, but Adaptive network hardening only recommends permanent rule changes based on traffic patterns, not temporary, approval-based port openings.

How to eliminate wrong answers

Option A is wrong because Adaptive network hardening uses machine learning to recommend NSG rules based on historical traffic patterns, but it does not provide on-demand, approved access control for specific ports like RDP. Option C is wrong because File integrity monitoring (FIM) tracks changes to critical files and registry keys, not network access control or RDP port management. Option D is wrong because Security recommendations are advisory outputs from Defender for Cloud (e.g., 'Enable JIT access'), not a feature that itself enforces time-bound RDP access.

677
MCQmedium

You are a Microsoft Sentinel analyst investigating an incident that contains several related alerts about a compromised user account. Your incident response runbook requires you to temporarily prevent the attacker from using the account while preserving the ability to restore access after remediation. You need to disable the account in Microsoft Entra ID directly from the incident investigation experience. What should you do?

A.Open the user entity page in the incident, select the Disable user account action, and confirm the operation.
B.Delete the user object in Microsoft Entra ID and restore it from the deleted users list after remediation.
C.Add the user entity to a watchlist, then configure an automation rule that disables accounts on the watchlist.
D.Assign the user a Conditional Access policy that blocks all cloud apps, then close the incident.
AnswerA

From an incident, expanding the user entity in Microsoft Sentinel exposes entity actions, and Disable user account performs the Microsoft Entra ID account disablement in place. This satisfies the runbook requirement to stop the attacker from authenticating while keeping the object recoverable, because disabling blocks sign-in but does not delete or alter the account's data, so access can be restored after remediation completes.

Why this answer

Microsoft Sentinel surfaces user entities inside incidents and provides entity actions that reach into Microsoft Entra ID. Disabling the account immediately blocks authentication for the compromised identity while leaving the object intact, so it can be re-enabled once containment and remediation are verified. Watchlists, Conditional Access, and deletion either do not change account state directly or introduce unnecessary disruption and recovery complexity.

Exam trap

The trap here is assuming any containment control, such as a blocking Conditional Access policy, is equivalent to disabling the account itself.

678
MCQmedium

A SOC analyst creates a watchlist in Microsoft Sentinel from a CSV file containing IP ranges (10.0.0.0/16) and a tag. The analyst wants to use this watchlist in a KQL query to check if a sign-in IP is within the ranges. Which KQL function should be used?

A._GetWatchlist('name') and use the has operator
B._GetWatchlist('name') and use the in operator
C._GetWatchlist('name') and use the ipv4_is_in_range function with the watchlist as a parameter
D._GetWatchlist('name') and use the contains operator
AnswerC

The `ipv4_is_in_range` function is the correct KQL scalar function for this scenario because it parses its first argument as an IPv4 address and the second as a CIDR range, returning a boolean representing membership. Using `_GetWatchlist('name')` provides the table of range strings, and you join or filter so each watchlist range is passed as the second parameter against the sign-in IP column. For IPv6 subnets, `ipv6_is_in_range` offers the same capability, making this a network-aware approach rather than a text-based match.

Why this answer

The `ipv4_is_in_range` function is designed to check whether an IPv4 address falls within a specified CIDR range. When combined with `_GetWatchlist('name')`, you can iterate over the watchlist entries and use `ipv4_is_in_range` to compare the sign-in IP against each range. This is the only approach that correctly handles CIDR notation (e.g., 10.0.0.0/16) rather than performing string matching or exact value comparison.

Exam trap

The trap here is that candidates often confuse string-matching operators (has, contains, in) with IP-specific functions, failing to recognize that CIDR range evaluation requires a dedicated function like `ipv4_is_in_range`.

How to eliminate wrong answers

Option A is wrong because the `has` operator performs substring matching on strings, not IP range evaluation; it would incorrectly match partial IPs or fail to interpret CIDR notation. Option B is wrong because the `in` operator checks for exact equality of values, so it cannot match an IP against a CIDR range unless the IP exactly equals the range string. Option D is wrong because the `contains` operator also performs substring matching and would not evaluate whether an IP falls within a CIDR range.

679
Multi-Selecteasy

Which TWO of the following are required to enable Microsoft Sentinel to receive alerts from Microsoft Defender for Cloud? (Choose two.)

Select 2 answers
A.Deploy the Log Analytics agent on all VMs.
B.Connect a non-Azure machine using Azure Arc.
C.Install the 'Microsoft Defender for Cloud' data connector in Microsoft Sentinel.
D.Enable Microsoft Defender for Cloud on the Azure subscription.
E.Assign an Azure Policy to enable Defender for Cloud.
AnswersC, D

Install the 'Microsoft Defender for Cloud' data connector in Microsoft Sentinel. — To route Defender for Cloud alerts into Sentinel, you must install and configure the Microsoft Defender for Cloud data connector in the Sentinel workspace. This connector establishes the API integration and subscription selection that streams alerts into the SecurityAlert table. Without this connector, Sentinel has no pipeline to receive those alerts, even if Defender for Cloud is enabled.

Why this answer

The 'Microsoft Defender for Cloud' data connector in Microsoft Sentinel is the specific integration point that ingests security alerts from Defender for Cloud into Sentinel. Without installing and configuring this connector, Sentinel cannot receive the alerts, even if Defender for Cloud is enabled on the subscription.

Exam trap

The trap here is that candidates often confuse enabling Defender for Cloud at the subscription level (which is required) with deploying agents or policies, thinking those are prerequisites for alert ingestion, when in fact the connector handles the ingestion independently of agent deployment.

680
MCQmedium

Your company uses Microsoft Sentinel. A security analyst receives an incident that includes a large number of alerts from a single data source. The analyst needs to identify which alerts are duplicates or related so they can focus on unique threats. Which feature should the analyst use?

A.Alert grouping
B.Investigation graph
C.Entity mapping
D.Automation rules
AnswerA

Alert grouping is a built-in setting in Sentinel analytics rules that determines when a new incident should be created versus when an alert should be added to an existing incident. You can group by entity, by alert attributes, or within a specified time window, and you can also set the incident title. This directly reduces alert fatigue by consolidating related alerts, making it the correct answer.

Why this answer

Alert grouping in Microsoft Sentinel automatically combines related alerts into a single incident, reducing noise so analysts can focus on unique threats. It uses machine learning to correlate alerts that share entities, timing, or patterns, directly addressing the need to identify duplicates or related alerts.

Exam trap

SC-200 often tests the confusion between alert grouping (deduplication/correlation at incident creation) and entity mapping (field mapping for correlation), causing candidates to pick entity mapping when the question asks about reducing duplicate alerts.

How to eliminate wrong answers

Option B is wrong because the investigation graph is a visual tool for exploring entity relationships during an investigation, not for deduplicating or grouping alerts at ingestion. Option C is wrong because entity mapping defines how alert fields map to entities (accounts, hosts, IPs) in analytics rules — it enables correlation but does not itself group alerts. Option D is wrong because automation rules trigger playbooks or actions based on incident creation, not alert deduplication.

681
Multi-Selecteasy

Which TWO of the following are recommended practices when performing threat hunting in Microsoft Sentinel? (Choose 2)

Select 2 answers
A.Create custom hunting queries based on hypothesis
B.Rely solely on automated detection rules
C.Disable all built-in analytics rules to avoid noise
D.Delete log data older than 30 days to improve query performance
E.Use watchlists to maintain high-value indicators for matching
AnswersA, E

Threat hunting is hypothesis-driven: analysts form a theory about adversary behaviour, then encode it as a custom query to surface matching activity. This satisfies the recommended practise of proactive, hypothesis-led hunting rather than relying solely on existing scheduled detections.

Why this answer

Option A is correct because threat hunting in Microsoft Sentinel is hypothesis-driven: analysts write custom hunting queries in KQL (via the Hunting blade or Logs) to proactively search for evidence of the hypothesized adversary behavior rather than waiting for alerts. Option E is correct because watchlists let you upload and manage lists of high-value indicators (IPs, accounts, hashes, domains) that hunting queries can join against using the _GetWatchlist() function, keeping threat intel current without editing each query. Option B is wrong because relying solely on automated analytics rules is reactive detection, not proactive hunting, and misses threats the rules do not cover.

Option C is wrong because disabling all built-in analytics rules removes valuable detections and creates blind spots instead of tuning noise. Option D is wrong because deleting log data destroys the historical evidence hunting depends on and undermines retention/compliance; query performance is addressed with table plans, summaries, and scoping, not data deletion.

Exam trap

The trap is picking 'rely on automated detections' or 'disable noisy rules' — both sound operationally convenient but contradict the proactive, hypothesis-driven nature of threat hunting.

682
MCQeasy

A security analyst is investigating a compromised user account using Microsoft 365 Defender. The analyst wants to see all the sign-in attempts made by this user in the last 24 hours, including the IP addresses and locations. Which advanced hunting table should the analyst query?

A.IdentityLogonEvents
B.AlertInfo
C.EmailAttachmentInfo
D.DeviceLogonEvents
AnswerA

IdentityLogonEvents is an advanced hunting table in Microsoft 365 Defender that stores raw authentication events for user sign-ins to Microsoft Entra ID (formerly Azure AD). Each record captures the account UPN, IP address, geographic location, application, client type, and success or failure status, enabling analysts to trace a compromised account's activity across cloud resources. To investigate a compromised user, this table is the authoritative source for sign-in attempts, including impossible travel anomalies and repeated failures.

Why this answer

The IdentityLogonEvents table in Microsoft 365 Defender advanced hunting captures authentication events from Azure Active Directory, including sign-in attempts, IP addresses, and geographic locations. This makes it the correct table for an analyst investigating a compromised user account to review all sign-in activity over the last 24 hours.

Exam trap

The trap here is that candidates often confuse DeviceLogonEvents (which covers local Windows logons) with IdentityLogonEvents (which covers cloud-based Azure AD sign-ins), leading them to select the wrong table for investigating cloud account compromises.

How to eliminate wrong answers

Option B (AlertInfo) is wrong because it contains metadata about alerts generated by detection mechanisms, not raw sign-in logs or IP addresses. Option C (EmailAttachmentInfo) is wrong because it focuses on email attachment metadata from Microsoft Defender for Office 365, unrelated to user authentication events. Option D (DeviceLogonEvents) is wrong because it records logon events on endpoints (Windows devices), not cloud-based Azure AD sign-ins, and does not include location data.

683
MCQmedium

Your incident response team uses Microsoft Sentinel. You need to automatically assign incidents to the appropriate analyst based on the incident category. What should you configure?

A.Create an automation rule that runs a playbook to assign the incident.
B.Create an analytics rule that sets the owner field.
C.Create a custom incident label for each category.
D.Create a workbook that filters incidents by category.
AnswerA

An automation rule can be configured to respond to incident creation or update events and launch a playbook built with Azure Logic Apps. The playbook uses the Microsoft Sentinel connector's update-incident action to set the owner (assigned-to) field, making it the correct native mechanism for programmatic ownership assignment.

Why this answer

Automation rules in Microsoft Sentinel can trigger a playbook when an incident is created or updated. By configuring an automation rule with a condition based on the incident category, you can invoke a playbook that uses the Microsoft Sentinel API or Logic Apps to set the incident's owner field, thereby assigning it to the appropriate analyst. This is the correct approach because automation rules are designed to run automated responses, including playbooks, on incidents.

Exam trap

The trap here is that candidates often confuse analytics rules (which create incidents) with automation rules (which act on existing incidents), leading them to incorrectly select option B thinking the rule itself can assign ownership during incident creation.

How to eliminate wrong answers

Option B is wrong because analytics rules generate alerts and incidents from log data; they do not have the capability to set the owner field on an incident—owner assignment is a post-creation action. Option C is wrong because custom incident labels are used for tagging and filtering, not for automated assignment or ownership changes. Option D is wrong because workbooks are visualization tools that display data; they cannot modify or assign incidents.

684
MCQhard

Refer to the exhibit. An analyst is reviewing a custom detection rule in Microsoft Sentinel. The rule is triggering many false positives from legitimate remote desktop connections. What should the analyst do to reduce false positives while keeping detection of pass-the-hash attacks?

A.Change the data source from SecurityEvent to Event.
B.Remove the AuthenticationPackage filter to include all packages.
C.Change LogonType to 10 to target remote interactive logons.
D.Add an exclusion for known administrative jump boxes.
AnswerD

Excluding known administrative jump boxes suppresses alerts from trusted sources performing legitimate RDP, while the rule's pass-the-hash logic still fires on anomalous authentication patterns elsewhere. This targets the false-positive source named in the stem without weakening detection coverage.

Why this answer

The rule detects pass-the-hash attacks by looking for suspicious logon patterns (e.g., LogonType 3 with NTLM authentication). Legitimate remote desktop connections from known administrative jump boxes are a common source of false positives. Adding an exclusion for these trusted IPs or hostnames allows the rule to continue detecting pass-the-hash attempts from other sources while suppressing noise from authorized administrative activity.

This is a standard tuning technique in Microsoft Sentinel to improve signal-to-noise ratio without weakening detection coverage.

Exam trap

SC-200 often tests the misconception that changing logon types or data sources can reduce false positives, when in fact targeted exclusions of known legitimate activity are the correct tuning approach.

How to eliminate wrong answers

Option A is wrong because changing the data source from SecurityEvent to Event would not reduce false positives; it would likely break the rule entirely since Event is a generic table that may not contain the necessary security event details (e.g., LogonType, AuthenticationPackage) required for pass-the-hash detection. Option B is wrong because removing the AuthenticationPackage filter would broaden the rule to include all authentication packages, increasing false positives rather than reducing them, as it would capture more legitimate logons. Option C is wrong because changing LogonType to 10 (RemoteInteractive) would target remote desktop logons specifically, but pass-the-hash attacks often use network logons (LogonType 3), so this would miss the actual attacks and not address the false positives from legitimate RDP connections.

685
MCQhard

Your organization uses Microsoft Sentinel with Azure Policy. You need to ensure that new Log Analytics workspaces are automatically connected to Sentinel and configured with a standard set of data connectors. What should you use?

A.Deploy an ARM template to each new workspace manually.
B.Use Sentinel automation rules to configure new workspaces.
C.Develop a Logic App that runs on a schedule to check for new workspaces.
D.Create Azure Policy definitions that deploy Sentinel and data connectors.
AnswerD

Azure Policy definitions with the DeployIfNotExists effect automatically enable Sentinel on Log Analytics workspaces by deploying the Sentinel solution, and can embed ARM templates to install data connectors, using a system-assigned managed identity for role assignment. This is the recommended at-scale governance approach because it continuously evaluates new and existing workspaces, auto-remediates non-compliant resources, and reports compliance status in Azure Policy.

Why this answer

Azure Policy can be used to automatically deploy and configure Microsoft Sentinel and its data connectors on new Log Analytics workspaces. By creating policy definitions with 'DeployIfNotExists' or 'Modify' effects, you ensure that any new workspace is automatically onboarded to Sentinel and has the required data connectors installed, meeting the requirement for automated, consistent configuration at scale.

Exam trap

The trap here is confusing automation rules (which handle incident response within Sentinel) with Azure Policy (which handles resource provisioning and compliance), leading candidates to incorrectly choose option B.

How to eliminate wrong answers

Option A is wrong because manually deploying an ARM template to each new workspace does not provide automated enforcement or scalability; it requires human intervention for every new workspace. Option B is wrong because Sentinel automation rules operate on incidents and alerts within an already-configured Sentinel workspace, not on the provisioning or configuration of the workspace itself. Option C is wrong because a scheduled Logic App would introduce latency and complexity, and it is not a native, policy-driven approach; Azure Policy provides real-time, event-driven enforcement without custom polling logic.

686
Multi-Selecthard

Which TWO actions should you take to reduce the cost of Microsoft Sentinel while maintaining security coverage?

Select 2 answers
A.Remove data connectors for non-critical sources.
B.Reduce the retention period of tables that do not require long-term storage.
C.Ingest verbose logs (e.g., DNS events) into Basic Logs tier.
D.Disable analytics rules that generate low-severity incidents.
E.Switch the workspace pricing tier from Capacity Reservations to Pay-as-you-Go.
AnswersB, C

Each Log Analytics table in the Sentinel workspace has its own retention setting, and data beyond that interactive retention period can be moved to long-term archive at lower cost or purged if not needed. For high-volume, low-value tables such as network session logs or performance counters, trimming retention from two years to, say, 90 days directly reduces Azure storage billing and archived-log management overhead. This preserves the recent data needed for active detection and investigation, pairs well with short-lived alerting workflows, and is a proven cost optimization that does not degrade detection coverage.

Why this answer

Reducing the retention period for tables that do not require long-term storage directly lowers the data storage costs in Microsoft Sentinel. Sentinel charges per GB of data stored, and by shortening retention (e.g., from 90 days to 30 days) for non-critical tables, you reduce the volume of data retained without affecting security monitoring or incident investigation for the shortened period.

Exam trap

The trap here is that candidates often confuse reducing data ingestion (Option A) with reducing storage costs, but the question explicitly requires maintaining security coverage, so removing data connectors would break that requirement.

687
MCQeasy

A SOC team uses Microsoft Sentinel and needs to ingest custom logs from an on-premises Linux server that writes events to a local text file. The team installs the Azure Monitor Agent (AMA) on the Linux server. Which configuration step is required in Sentinel to collect the custom log file?

A.Create a custom table in the Log Analytics workspace and configure a Data Collection Rule (DCR) to ingest the file
B.Use the Syslog connector and map the file to a facility
C.Install the Log Analytics agent (MMA) and configure Custom Logs in the agent settings
D.Create a scheduled analytics rule that reads the file via an API
AnswerA

Custom text logs require a destination table in the Log Analytics workspace plus a Data Collection Rule that defines the file path, stream declaration and workspace target, which the Azure Monitor Agent then applies. Creating the custom table and DCR satisfies the stem's configuration requirement for ingesting the Linux server's local text file into Microsoft Sentinel.

Why this answer

Azure Monitor Agent (AMA) requires a Data Collection Rule (DCR) to define the data source (custom log file path) and the destination table in the Log Analytics workspace. Since the log is a custom text file (not syslog or a standard Windows event), you must first create a custom table (using the workspace's schema or via the 'Create custom log' wizard) and then configure the DCR to ingest the file into that table. This is the only supported method for AMA-based custom log ingestion.

Exam trap

The trap here is that candidates confuse the legacy MMA custom log configuration (which used the agent's own settings) with the modern AMA approach, which requires a DCR and a custom table — or they incorrectly assume Syslog can ingest any text file by simply mapping it to a facility.

How to eliminate wrong answers

Option B is wrong because the Syslog connector is designed for standard syslog messages (RFC 3164/5424) sent over UDP/TCP, not for reading arbitrary text files; mapping a file to a facility is not possible and would not parse the custom log format. Option C is wrong because the Log Analytics agent (MMA) is legacy and not recommended for new deployments; the question explicitly states the team installed AMA, so using MMA would be a step backward and incompatible with the stated agent choice. Option D is wrong because scheduled analytics rules query data already in Log Analytics; they cannot directly read files from a server via an API — that would require a custom data connector or a separate ingestion pipeline, not a rule.

688
Multi-Selecthard

Which THREE of the following are capabilities of Microsoft Copilot for Security?

Select 3 answers
A.Manage Azure Policy assignments.
B.Summarize incidents from Microsoft Defender XDR.
C.Automatically configure conditional access policies.
D.Generate KQL queries for Microsoft Sentinel.
E.Analyze scripts for malicious intent.
AnswersB, D, E

Security Copilot ingests alert and incident data from Microsoft Defender XDR—including device, identity, and email evidence—and generates a natural-language executive summary with estimated scope, impacted assets, and high-level attack chain. This allows the analyst to triage from the incident queue without manually pivoting across alerts, and the same summary can be exported for reporting. Because it is grounded in the live incident graph, the summary reflects current detections rather than static intel.

Why this answer

Microsoft Copilot for Security can summarize incidents from Microsoft Defender XDR, providing a concise overview of alerts, affected assets, and attack chains. This capability leverages natural language processing to parse incident data and generate human-readable summaries, aiding analysts in rapid triage.

Exam trap

The trap here is that candidates may confuse Copilot for Security's analytical and summarization capabilities with broader management or automation features of other Azure services, such as Azure Policy or Conditional Access, which are not part of Copilot's scope.

689
Multi-Selectmedium

Which TWO actions can reduce the cost of Microsoft Sentinel while maintaining security coverage?

Select 2 answers
A.Remove unused data connectors.
B.Switch to a pay-as-you-go workspace.
C.Configure some tables to use Basic Logs tier.
D.Move older logs to Azure Storage archive tier.
E.Reduce workspace retention to 30 days for all tables.
AnswersC, D

Configuring some tables to use Basic Logs tier reduces cost because Basic Logs are offered at a significantly lower ingestion price than Analytics Logs (up to 75% cheaper). This tier is ideal for high-volume, verbose tables used for debugging or troubleshooting, not for security analytics requiring advanced queries and alerts. However, Basic Logs have a shorter retention period and limited query capabilities, so they should only be used for tables that do not drive detection rules.

Why this answer

Configuring tables to use the Basic Logs tier reduces ingestion costs for high-volume, verbose logs (e.g., from firewalls or DNS servers) while still retaining the data for security analysis. Basic Logs are stored at a lower cost per GB but have reduced query capabilities (e.g., no interactive full-text search, limited to KQL summarization). This allows you to keep security coverage by retaining the logs for detection and investigation, albeit with a different query pattern.

Exam trap

The trap here is that candidates often confuse reducing retention (Option E) with cost savings, but Microsoft explicitly warns that deleting logs can break detection rules and incident investigations, whereas tiering (Basic Logs or archive) preserves data for compliance and hunting at a lower cost.

690
MCQhard

Refer to the exhibit. You have a Logic Apps playbook that triggers on Microsoft Sentinel alerts. The playbook is not posting messages to Teams. What is the most likely cause?

A.The playbook is using the wrong trigger type.
B.The Teams connector is not authenticated.
C.The trigger body is not referencing the correct alert ID.
D.The JSON syntax is invalid.
AnswerA

The playbook is using the wrong trigger type. A Logic Apps playbook designed for Microsoft Sentinel automation must use the 'When a Microsoft Sentinel alert is created' trigger (or the incident trigger in newer implementations), not a generic HTTP, schedule, or manual trigger. With the wrong trigger, the runtime does not supply the Sentinel alert schema, so all subsequent references to alert properties—such as the alert ID or title—resolve to empty values and the playbook fails before any Teams action executes. The fix is to replace the trigger with the Sentinel-specific trigger so the correct alert payload is bound to the workflow.

Why this answer

The playbook is triggered on Microsoft Sentinel alerts, but Logic Apps requires a specific trigger type to process these alerts correctly. The most likely cause is that the playbook uses a generic HTTP trigger instead of the 'Microsoft Sentinel Incident' or 'Microsoft Sentinel Alert' trigger, which is designed to parse the alert payload and provide the necessary context for downstream actions like posting to Teams. Without the correct trigger, the playbook may not receive the alert data or may fail to execute the Teams connector properly.

Exam trap

The trap here is that candidates often assume authentication issues (Option B) are the default cause for Teams failures, but the question's context of 'not posting messages' without errors points to a trigger mismatch rather than a connectivity problem.

How to eliminate wrong answers

Option B is wrong because if the Teams connector were not authenticated, the playbook would typically fail with an authentication error, not silently fail to post messages; the question implies no error is reported, so authentication is likely valid. Option C is wrong because the trigger body not referencing the correct alert ID would cause a data mapping issue, but the playbook would still attempt to run and likely produce an error or incorrect output, not a complete failure to post. Option D is wrong because invalid JSON syntax would cause the playbook to fail at design time or trigger a validation error, preventing it from running at all, whereas the playbook is running but not posting messages.

691
MCQhard

You are a security operations analyst for a company that uses Microsoft Sentinel. You need to ensure that all incidents created in the workspace are automatically enriched with threat intelligence indicators from Microsoft Defender Threat Intelligence. What should you configure?

A.The Microsoft Defender Threat Intelligence data connector in Microsoft Sentinel.
B.A playbook that queries the Microsoft Defender Threat Intelligence API and adds indicators as comments to the incident.
C.A workbook that visualizes threat intelligence matches for incidents.
D.A scheduled analytics rule that runs every hour to match incidents with threat intelligence.
AnswerA

Microsoft Sentinel includes a data connector for Microsoft Defender Threat Intelligence (MDTI) that ingests threat intelligence indicators into the workspace. Once connected, these indicators are automatically used to enrich incidents, matching entities in incidents against the indicators. This provides native enrichment without custom automation. Configuring this connector is the correct method to ensure all incidents are enriched with MDTI indicators.

Why this answer

The Microsoft Defender Threat Intelligence data connector in Microsoft Sentinel ingests threat intelligence indicators into the workspace. Once enabled, Microsoft Sentinel automatically matches these indicators against incident entities, enriching incidents with relevant threat intelligence. This is the native and intended method for automatic enrichment.

Exam trap

The trap here is thinking that a playbook or analytics rule is needed for enrichment, when the built-in MDTI connector provides automatic enrichment without custom automation.

692
Multi-Selecthard

Which TWO are valid methods to ingest logs into Microsoft Sentinel from a non-Azure virtual machine? (Select TWO.)

Select 2 answers
A.Azure Monitor Agent (AMA) with Azure Arc
B.Log Analytics agent (MMA) – legacy
C.Microsoft Sentinel agent (standalone)
D.Azure Monitor Agent (AMA) without Azure Arc
E.Log Analytics agent (OMS) – deprecated
AnswersA, B

Azure Monitor Agent (AMA) with Azure Arc is the current, recommended ingestion path for non-Azure virtual machines. AMA itself is a unified agent that collects telemetry from VMs, but for machines outside Azure, the agent must be deployed and configured through Azure Arc's management plane. Arc enables you to install AMA, assign Data Collection Rules (DCRs), and route the data into a Log Analytics workspace, which Microsoft Sentinel then ingests. Without Arc, AMA cannot be centrally managed on hybrid machines, so this pairing is a fully valid method for bringing logs into Sentinel.

Why this answer

Azure Arc bridges non-Azure VMs into Azure's management plane, allowing the Azure Monitor Agent (AMA) to be installed and managed as if the VM were native Azure. This enables log ingestion into Microsoft Sentinel without requiring direct Azure connectivity or a VPN, using the same AMA data collection rules (DCRs) as Azure VMs.

Exam trap

The trap here is that candidates confuse the deprecated OMS agent with the still-supported MMA legacy agent, or assume AMA can be installed on non-Azure VMs without Azure Arc, when Arc is mandatory for management plane integration.

693
Multi-Selectmedium

Which THREE techniques are commonly used in Microsoft Sentinel threat hunting to identify command and control (C2) communication? (Select THREE.)

Select 3 answers
A.Analyzing email headers for phishing
B.Detecting DNS tunneling
C.Analyzing network beaconing patterns
D.Examining SSL/TLS certificate anomalies
E.Identifying brute force attempts
AnswersB, C, D

Detecting DNS tunnelling is crucial for identifying C2 communication because attackers frequently encapsulate malicious traffic within legitimate DNS queries and responses. Microsoft Sentinel can analyse DNS logs, looking for anomalous patterns such as excessively long domain names, unusual query frequencies, or specific data encoding within DNS records. This technique effectively uncovers covert C2 channels, satisfying the requirement to identify command and control communication.

Why this answer

Detecting DNS tunneling (B) is correct because attackers frequently encode C2 data inside DNS queries and responses, and Sentinel hunting queries can flag anomalies such as high-entropy subdomains, excessive TXT/NULL record requests, or unusually long query names in DNS events. Analyzing network beaconing patterns (C) is correct because C2 implants typically check in at regular intervals, so hunting for periodic, low-volume outbound connections (for example, consistent time deltas or repeated small byte counts to the same destination) helps reveal compromised hosts. Examining SSL/TLS certificate anomalies (D) is correct because malicious C2 infrastructure often uses self-signed, expired, mismatched, or otherwise suspicious certificates, and Sentinel can correlate certificate metadata from network logs to identify such traffic.

Analyzing email headers for phishing (A) is not a C2 communication technique; it targets initial access via email, and identifying brute force attempts (E) addresses credential attacks rather than command-and-control traffic.

Exam trap

SC-200 often tests whether candidates can distinguish C2 detection techniques (DNS tunneling, beaconing, TLS anomalies) from adjacent attack-stage techniques like phishing analysis or brute force detection.

694
MCQhard

You are hunting for signs of Kerberoasting in Microsoft Sentinel. Which hunting query using KQL would you use to identify service principal names (SPNs) being queried via Kerberos TGS requests?

A.SecurityEvent | where EventID == 4769 and TicketEncryptionType == 0x17
B.DeviceEvents | where ActionType == 'KerberosTicketRequest'
C.DeviceLogonEvents | where LogonType == 'Kerberos' and AccountDomain == 'Service'
D.SecurityEvent | where EventID == 4768 and TicketEncryptionType == 0x17
AnswerA

Event ID 4769 logs Kerberos service ticket (TGS) requests, and encryption type 0x17 (RC4-HMAC) reveals weak cipher use typical of Kerberoasting, where attackers request SPN tickets then crack them offline. Filtering both fields surfaces exactly the SPN queries the stem requires.

Why this answer

Kerberoasting involves requesting TGS tickets for Service Principal Names (SPNs). In Microsoft Sentinel, the SecurityEvent table with EventID 4769 logs TGS requests. TicketEncryptionType 0x17 indicates RC4 encryption, which is commonly used in Kerberoasting attacks.

Option A correctly identifies this query. Option D is incorrect because EventID 4768 is for TGT requests, not TGS. Option B (DeviceEvents) may not capture this specific event, and Option C (DeviceLogonEvents) does not focus on SPN details.

695
MCQeasy

Your security team needs to assign a custom role in Microsoft Sentinel that allows read and write access to incidents but not to analytics rules. Which built-in role should you use as a base for the custom role?

A.Microsoft Sentinel Responder
B.Microsoft Sentinel Reader
C.Microsoft Sentinel Contributor
D.Global Administrator
AnswerA

Microsoft Sentinel Responder is the correct built-in role when the job requires actively working incidents: it lets the analyst view, triage, assign, update, and comment on incidents, as well as perform investigation actions like running queries. Critically, it omits write rights to analytics rules, automation rules, and data connectors, so an analyst can respond to threats without accidentally weakening detection logic. This aligns with least privilege for a pure incident-response duty.

Why this answer

The Microsoft Sentinel Responder role is the correct base because it grants read and write access to incidents while explicitly excluding write permissions to analytics rules. This aligns with the requirement for incident management without allowing modifications to detection logic.

Exam trap

The trap here is that candidates often confuse 'Contributor' as the default for any write access, overlooking that it grants broader permissions than needed, while 'Responder' is specifically scoped to incident operations without analytics rule modification.

How to eliminate wrong answers

Option B is wrong because Microsoft Sentinel Reader provides read-only access to all Sentinel data, including incidents and analytics rules, but does not allow write access to incidents. Option C is wrong because Microsoft Sentinel Contributor includes full write access to analytics rules, which violates the requirement to restrict such permissions. Option D is wrong because Global Administrator is a broad Azure AD role that grants full access to all Azure resources, including Sentinel, and is not a Sentinel-specific built-in role; it would allow unrestricted modifications to analytics rules.

696
MCQeasy

Your organization uses Microsoft Defender for Identity. You receive an alert about a suspicious Kerberos activity that may indicate a golden ticket attack. Which of the following actions should you take to investigate this alert?

A.Immediately reset the krbtgt account password twice
B.Export the Active Directory event logs to Microsoft Sentinel for analysis
C.Review the alert details in the Microsoft Defender for Identity portal and analyze related events
D.Disable the user account that triggered the alert
AnswerC

Reviewing the alert details in the Microsoft Defender for Identity portal is the correct first step because the portal aggregates the pertinent events, users, devices, and related alerts into an investigation experience. From the alert page, you can access the full timeline, examine the underlying activities, and pivot to entity profiles, which lets you validate whether the alert is a true positive and understand the attack chain. This analysis provides the context needed to decide on any subsequent containment or remediation.

Why this answer

The first step in investigating a golden ticket attack alert from Microsoft Defender for Identity is to review the alert details and analyze the related events within the Defender for Identity portal. This allows you to understand the scope of the suspicious Kerberos activity, identify the affected accounts, and correlate the alert with other security signals before taking any remediation actions.

Exam trap

The trap here is that candidates often jump to remediation actions like resetting the krbtgt password or disabling accounts without first investigating the alert details, which can lead to unnecessary disruption or missed context about the attack's scope.

How to eliminate wrong answers

Option A is wrong because immediately resetting the krbtgt account password twice is a remediation step that should only be performed after thorough investigation and confirmation of a golden ticket attack; premature reset can cause Kerberos authentication failures across the domain. Option B is wrong because exporting Active Directory event logs to Microsoft Sentinel for analysis is a secondary step that may be useful for long-term hunting or correlation, but the immediate investigation should start within the Defender for Identity portal where the alert originated. Option D is wrong because disabling the user account that triggered the alert is premature and could be a false positive; the alert may be triggered by legitimate activity or a compromised account that needs further analysis before taking disruptive action.

697
MCQhard

During an incident investigation, you find that a compromised account was used to log into a virtual machine via RDP from an IP address in a sanctioned country. The VM has Microsoft Defender for Endpoint installed. Which data source in Microsoft Sentinel would you query to see the RDP connection events?

A.DeviceLogonEvents (Microsoft Defender XDR)
B.CommonSecurityLog
C.SigninLogs (Microsoft Entra ID)
D.SecurityEvent
AnswerD

SecurityEvent is the correct table because it contains Windows Security event logs, including Event ID 4624 (successful logon) and 4625 (failed logon), which are essential for RDP investigations. When an RDP session is established on a Windows VM, the local Security channel generates a 4624 with LogonType 10 (RemoteInteractive), and this data is sent to Sentinel via the Windows Security Events data connector (using either the legacy Log Analytics agent or the Azure Monitor Agent). From this table you can query the source IP, source port, and account that performed the RDP logon to identify indicators of compromise. Thus, SecurityEvent is the authoritative and most direct source for RDP logon activity in Microsoft Sentinel.

Why this answer

The SecurityEvent table in Microsoft Sentinel collects Windows security events from machines with the Log Analytics agent or Azure Monitor Agent, including Event ID 4625 (failed logon) and Event ID 4624 (successful logon). Since the compromised account used RDP to log into a VM with Defender for Endpoint installed, the RDP connection events are captured as Windows security log events and stored in the SecurityEvent table. This is the correct data source for querying local authentication events on the VM itself.

Exam trap

The trap here is that candidates confuse cloud sign-in logs (SigninLogs) with local OS logon events, or assume Defender for Endpoint's DeviceLogonEvents is the primary Sentinel table, when in fact SecurityEvent is the correct source for Windows security events collected via the Log Analytics agent.

How to eliminate wrong answers

Option A is wrong because DeviceLogonEvents (Microsoft Defender XDR) captures device-level logon events from Microsoft Defender for Endpoint sensors, but it is designed for advanced hunting in the Microsoft 365 Defender portal, not directly in Microsoft Sentinel's workspace tables; while it can be accessed via cross-resource queries, the question asks for a data source in Microsoft Sentinel, and SecurityEvent is the native table for Windows security events. Option B is wrong because CommonSecurityLog is used for syslog-style logs from third-party security appliances (e.g., firewalls, proxies), not for Windows RDP logon events from a VM. Option C is wrong because SigninLogs (Microsoft Entra ID) records cloud-based authentication to Microsoft Entra ID (formerly Azure AD), such as user sign-ins to Azure portal or Office 365, not local RDP logons to a virtual machine.

698
MCQhard

You are responsible for Microsoft Defender for Cloud Apps. The security team reports that they are not receiving alerts for suspicious activities from a specific connected app (Salesforce). You verify that the app is connected and the log collection is working. What should you check next?

A.Review the IP address ranges configured for the Salesforce app.
B.Ensure that the anomaly detection policy for Salesforce is enabled in Defender for Cloud Apps.
C.Check if the Salesforce app connector is properly configured in Microsoft Entra ID.
D.Verify that the Salesforce tenant is licensed for Microsoft Entra ID P2.
AnswerB

You must explicitly enable an anomaly detection policy that targets Salesforce in Microsoft Defender for Cloud Apps because these policies are not automatically applied to every connected app. The 'Anomalous activity' policy, for example, can be customized per app family, and if Salesforce is not included or the policy is disabled, no alerts will be raised for unusual sign-ins, downloads, or admin actions in that tenant. Enabling the policy under Policies > Anomaly detection and confirming the Salesforce app is listed as a filter or data source is the direct prerequisite to receive the alert you are investigating.

Why this answer

Since the app is connected and log collection is verified, the issue is likely that the anomaly detection policy for Salesforce is disabled. Defender for Cloud Apps uses built-in anomaly detection policies to generate alerts for suspicious activities; if the policy is turned off, no alerts will be raised even though data flows correctly. Enabling the policy ensures that behavioral baselines and threat detection are applied to the Salesforce logs.

Exam trap

The trap here is that candidates assume connectivity and log collection guarantee alert generation, but they overlook that the anomaly detection policy is a separate toggle that must be explicitly enabled for each connected app.

How to eliminate wrong answers

Option A is wrong because reviewing IP address ranges for Salesforce would affect access control or location-based policies, not the generation of suspicious activity alerts; the core issue is policy enablement, not network configuration. Option C is wrong because the Salesforce app connector in Microsoft Entra ID is for SSO and identity federation, not for the log collection and alerting pipeline in Defender for Cloud Apps; the connector is already verified as connected. Option D is wrong because Microsoft Entra ID P2 licensing is required for Identity Protection and Privileged Identity Management features, not for Defender for Cloud Apps anomaly detection; Defender for Cloud Apps licensing is separate and does not depend on Entra ID P2 for alert generation.

699
MCQhard

You are deploying Microsoft Sentinel using the above ARM template parameters. After deployment, you notice that Microsoft Defender for Cloud alerts are not being ingested. What is the MOST likely reason?

A.UEBA is enabled, which conflicts with Defender for Cloud data ingestion.
B.The workspace location (eastus) does not support Defender for Cloud connector.
C.The 'MicrosoftThreatProtection' connector only ingests Microsoft Defender XDR signals, not Defender for Cloud alerts.
D.The workspace name 'sentinel-workspace' is reserved for internal use.
AnswerC

The 'MicrosoftThreatProtection' connector (also known as the Microsoft 365 Defender connector) exclusively ingests incident and alert data from Microsoft Defender XDR components such as Defender for Endpoint, Defender for Office 365, Defender for Identity, and Defender for Cloud Apps. Defender for Cloud alerts are delivered via the 'AzureSecurityCenter' (now 'Microsoft Defender for Cloud') connector, which is a separate data source with its own connector type. Because the ARM template only includes the MicrosoftThreatProtection connector, Defender for Cloud alerts would never appear in Sentinel, making this the correct explanation for the issue.

Why this answer

The 'MicrosoftThreatProtection' connector is specifically designed to ingest signals from Microsoft Defender XDR (formerly Microsoft 365 Defender), which includes Defender for Endpoint, Defender for Office 365, Defender for Identity, and Defender for Cloud Apps. It does not ingest Microsoft Defender for Cloud alerts. To ingest Defender for Cloud alerts, you must use the dedicated 'Defender for Cloud' data connector in Microsoft Sentinel.

Therefore, deploying only the 'MicrosoftThreatProtection' connector will result in Defender for Cloud alerts not being ingested.

Exam trap

The trap here is that candidates assume the 'MicrosoftThreatProtection' connector ingests all Microsoft security alerts, including Defender for Cloud, because of the broad 'Threat Protection' naming, but in reality it only covers Microsoft Defender XDR signals.

How to eliminate wrong answers

Option A is wrong because UEBA (User and Entity Behavior Analytics) is a feature within Microsoft Sentinel that analyzes patterns and anomalies; it does not conflict with or block data ingestion from Defender for Cloud. Option B is wrong because the 'eastus' region fully supports the Defender for Cloud connector; all Azure public regions support this connector. Option D is wrong because 'sentinel-workspace' is not a reserved name; workspace names must be globally unique within a resource group but are not reserved by Microsoft for internal use.

700
MCQmedium

A security team needs to enforce that all Azure virtual machines have a specific custom script execution baseline (e.g., block PowerShell from executing scripts from the internet). They want to use Microsoft Defender for Cloud to continuously monitor and alert when a VM deviates from this baseline. Which feature should they use?

A.Just-In-Time VM Access (JIT)
B.Adaptive application controls
C.Regulatory compliance dashboard
D.File Integrity Monitoring (FIM)
AnswerB

Adaptive application controls is the correct control because it is a runtime host-based allowlisting solution in Microsoft Defender for Cloud that builds a machine-generated baseline of trusted applications and scripts for each VM. Using machine learning, it whitelists known-safe executables and script behavior patterns, then both audits and, when configured to 'Deny' mode, blocks unapproved executables or scripts—such as a PowerShell payload retrieved from the internet—at the moment of execution. This provides the precise enforcement mechanism needed to keep unauthorized scripts from running on Azure VMs.

Why this answer

Adaptive application controls (AAC) in Microsoft Defender for Cloud allow you to define allowlists for applications and scripts that can run on your Azure VMs. By configuring AAC to block PowerShell scripts from the internet, the service uses machine learning to establish a baseline of allowed executables and scripts, then continuously monitors for deviations—such as an unauthorized PowerShell script execution—and generates security alerts. This directly meets the requirement for continuous monitoring and alerting on custom script execution baselines.

Exam trap

The trap here is that candidates confuse File Integrity Monitoring (FIM) with script execution control, but FIM only monitors file and registry changes, not the execution behavior of scripts or applications.

How to eliminate wrong answers

Option A is wrong because Just-In-Time VM Access (JIT) controls network access to management ports (e.g., RDP, SSH) and does not monitor or enforce script execution policies. Option C is wrong because the Regulatory compliance dashboard tracks compliance against standards like ISO 27001 or PCI DSS, not custom script execution baselines. Option D is wrong because File Integrity Monitoring (FIM) monitors changes to registry keys and critical files (e.g., system binaries), not script execution behavior or PowerShell policies.

701
MCQeasy

You are responding to a security incident involving a user who clicked on a malicious link in an email. The link led to a website that downloaded a file to the user's device. Microsoft Defender for Endpoint (MDE) detected the file as malware and blocked it. However, the user reports that the device is running slowly. You need to verify if there are any remnants of the malware. Which action should you take?

A.Re-onboard the device to MDE to ensure it's fully managed.
B.Run a full antivirus scan using Microsoft Defender Antivirus.
C.Initiate a live response session and run a PowerShell script to check for persistence mechanisms.
D.Perform a full OS reinstall to ensure the device is clean.
AnswerC

Initiating a live response session on the endpoint and executing a PowerShell script is the correct action because it provides a remote, audited shell that can directly interrogate the system's persistence mechanisms. The script can enumerate Services, Run keys, scheduled tasks, WMI event subscriptions, and other autostart locations to determine whether the attacker left behind a way to re-enter. This aligns with MDE's incident response workflow, allowing you to collect evidence and remediate instantly without taking the device offline.

Why this answer

A live response session in Microsoft Defender for Endpoint lets you run remote investigative commands — including PowerShell scripts — directly on the device to enumerate persistence mechanisms such as Run keys, scheduled tasks, services, and WMI subscriptions. Since MDE already blocked the malware, the goal is to verify no remnants or persistence artifacts remain, and live response is the purpose-built tool for that forensic check.

Exam trap

SC-200 often tests the instinct to 'nuke and pave' or run a generic AV scan — candidates overlook that live response is the targeted forensic tool for verifying remnants after a blocked infection.

How to eliminate wrong answers

Option A is wrong because re-onboarding the device only re-establishes the MDE agent connection and does not investigate or remove any malware remnants. Option B is wrong because a full Defender Antivirus scan may detect known signatures but will not reveal fileless persistence, registry artifacts, or scheduled tasks that a targeted live-response script can enumerate. Option D is wrong because a full OS reinstall is a destructive, disproportionate response when the malware was already blocked and only verification of remnants is required.

702
Multi-Selectmedium

An analyst is investigating a ransomware outbreak using Microsoft 365 Defender Advanced Hunting. They need to find all devices where a file with the extension '.locked' was created within one hour after a known malicious process (e.g., 'ransomware.exe') was executed on the same device. Which two tables should be joined in the query? (Choose 2.)

Select 2 answers
A.DeviceProcessEvents
B.DeviceNetworkEvents
C.DeviceFileEvents
D.DeviceRegistryEvents
AnswersA, C

DeviceProcessEvents is the correct table because advanced hunting in Microsoft 365 Defender stores process creation and launch activity here, including fields such as ProcessCommandLine, ParentProcessId, and Timestamp. When ransomware executes, its malicious executable appears as a new process event, and analysts can trace process lineage to identify the initial access vector and scope of execution. This table is the primary source for determining which process launched the ransomware and what actions it performed on the host.

Why this answer

DeviceProcessEvents is correct because it logs process creation events, including the execution of 'ransomware.exe'. This table is essential to identify the timestamp and device where the malicious process ran, which serves as the starting point for the time-bound investigation.

Exam trap

The trap here is that candidates may mistakenly choose DeviceNetworkEvents thinking network activity is key, but the question specifically requires file creation events, which only DeviceFileEvents provides.

703
MCQmedium

A SOC analyst is creating a scheduled analytics rule in Microsoft Sentinel to detect when a user is added to the Global Administrator role in Microsoft Entra ID. The analyst also needs to capture the user who performed the addition. Which Microsoft Entra ID table should the analyst query in the rule's KQL query?

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

AuditLogs is the correct table because it contains every write operation on Azure AD directory objects, including role management activities like 'Add member to role' or 'Update role'. Each log entry includes the actor (who performed the action), the target (the user or group who received the role), and the exact timestamp, which are essential for a scheduling rule that detects role changes. In Microsoft Sentinel, the AuditLogs table directly maps to the Azure AD Audit Log, making it the authoritative source for this detection.

Why this answer

The AuditLogs table in Microsoft Entra ID (formerly Azure AD) records all directory-level changes, including role assignments like adding a user to the Global Administrator role. Each audit log entry contains the 'InitiatedBy' property, which captures the user or service principal who performed the action, meeting the analyst's requirement to identify the actor. SigninLogs only tracks authentication events, not administrative changes, making AuditLogs the correct choice for this detection.

Exam trap

The trap here is that candidates confuse SigninLogs (which tracks who logged in) with AuditLogs (which tracks who made a change), assuming the actor's identity is always found in sign-in records rather than in directory audit trails.

How to eliminate wrong answers

Option A is wrong because SigninLogs captures user sign-in events (authentication) and does not include directory modification records such as role assignments. Option C is wrong because IdentityInfo provides user profile and attribute data (e.g., job title, department) but does not log administrative actions or role changes. Option D is wrong because BehaviorAnalytics contains user and entity behavior analytics (UEBA) insights derived from other logs, not raw audit records of role additions.

704
MCQhard

Your organization uses Microsoft Sentinel with Azure Monitor Agent (AMA) to collect Windows security events. You need to collect process creation events (Event ID 4688) and include command-line information. The current Data Collection Rule (DCR) collects only basic security events. What should you modify?

A.Upgrade the AMA to the latest version.
B.Enable the 'Include command line in process creation events' policy in Windows Group Policy.
C.Modify the DCR to include Event ID 4688 in the data source.
D.Switch to the Windows Security Events via Legacy Agent connector.
AnswerB

This is the correct fix because Windows does not record command-line arguments in Event ID 4688 unless the 'Include command line in process creation events' policy is enabled. The setting is located under Computer Configuration > Administrative Templates > System > Audit Process Creation and, when set to Enabled, adds the Process Command Line field to each generated 4688 event. Without this Group Policy (or local security policy) change, Microsoft Sentinel receives the event but the command-line field remains empty, which severely degrades process-investigation and hunting value.

Why this answer

Event ID 4688 (process creation) can include command-line arguments, but this data is not captured by default. The 'Include command line in process creation events' Group Policy setting must be enabled on the Windows machines to populate the CommandLine field in the security event log. Without this policy, the AMA and DCR will collect the event but the command-line information will be empty.

Exam trap

The trap here is that candidates assume modifying the DCR to include the event ID is sufficient, but they overlook the prerequisite Windows policy that must be enabled to populate the command-line data within the event itself.

How to eliminate wrong answers

Option A is wrong because upgrading the AMA version does not enable command-line capture; the AMA already supports collecting Event ID 4688 with command-line data if the underlying event contains it. Option C is wrong because modifying the DCR to include Event ID 4688 will collect the event, but the command-line field will remain blank unless the Group Policy setting is enabled first. Option D is wrong because switching to the legacy agent connector does not solve the command-line requirement; the legacy agent also relies on the same Group Policy setting to populate the command-line data.

705
MCQmedium

A SOC analyst creates a scheduled analytics rule in Microsoft Sentinel to detect anomalous Microsoft Entra ID sign-ins. The rule uses the SigninLogs table and runs every 15 minutes. The analyst wants to alert when a user signs in from a country that is not in the allowed list (['US', 'CA']). Which KQL query pattern should be used in the rule?

A.SigninLogs | where Location.countryOrRegion !in (dynamic(['US','CA']))
B.SigninLogs | where Country !in ('US','CA')
C.SigninLogs | where location != 'US' and location != 'CA'
D.SigninLogs | where geoLocation !in (dynamic(['US','CA']))
AnswerA

The `Location` column in the SigninLogs table is a dynamic (JSON-like) object, and `Location.countryOrRegion` correctly extracts the country/region string via dot notation. The `!in` operator with a `dynamic()` array of allowed country codes excludes sign-ins from the US and CA as intended. KQL string comparisons are case-insensitive, so this filter handles variations like 'us' or 'ca' correctly. This is the only option that matches both the actual schema and Kusto syntax.

Why this answer

The SigninLogs table stores the sign-in location in the `Location.countryOrRegion` field, which is a nested property of the `Location` dynamic object. The KQL operator `!in` with `dynamic(['US','CA'])` correctly performs a case-sensitive comparison against a list of string values, ensuring that only sign-ins from countries outside the allowed list trigger the alert.

Exam trap

The trap here is that candidates often confuse the flat field name `Country` or `location` with the correct nested property `Location.countryOrRegion`, leading them to choose options that reference non-existent or incorrectly named columns.

How to eliminate wrong answers

Option B is wrong because the `Country` field does not exist in the SigninLogs table; the correct field is `Location.countryOrRegion`. Option C is wrong because it uses the `location` field (which is a string like 'US' or 'CA' but not the correct property path) and the `!=` operator performs a case-sensitive comparison, but more critically it does not use the correct nested field name. Option D is wrong because `geoLocation` is not a valid field in SigninLogs; the correct field is `Location.countryOrRegion`, and the `!in` operator with `dynamic()` is syntactically correct but applied to the wrong column.

706
MCQeasy

Your organization uses Microsoft Sentinel. You receive an alert for a suspicious sign-in from an unusual location. You want to automatically create an incident and assign it to the security team for investigation. What should you configure?

A.Add the user to a watchlist and configure a fusion rule.
B.Create a playbook that triggers on the alert and creates an incident manually.
C.Modify the analytics rule to set the incident creation setting to 'Create incident from alert'.
D.Configure an automation rule that runs when the alert is generated, creates an incident, and sets the owner to the security team.
AnswerD

Automation rules are Sentinel's native orchestration mechanism that can trigger on alert creation and perform actions such as creating an incident, assigning an owner, changing severity, and running playbooks. By configuring a rule that runs when the alert is generated, you ensure the incident is created with the security team as the owner in one atomic step. This approach centralizes lifecycle management and is recommended over manual playbook or analytics-rule-only configurations for consistent ownership.

Why this answer

Automation rules in Microsoft Sentinel allow you to automatically create incidents from alerts and assign them to specific teams or owners. This is the native, efficient method to handle the scenario without manual intervention or custom playbooks.

Exam trap

The trap here is that candidates may think a playbook is required for incident creation, but automation rules provide a simpler, native mechanism that can both create incidents and assign ownership without custom code.

How to eliminate wrong answers

Option A is wrong because watchlists are used for correlation and enrichment, not for automatic incident creation; fusion rules combine multiple alerts but do not assign incidents. Option B is wrong because creating a playbook to manually create an incident is unnecessary overhead; automation rules can directly create incidents without a playbook. Option C is wrong because the 'Create incident from alert' setting is already enabled by default for analytics rules; the question requires assigning the incident to the security team, which is not achieved by this setting alone.

707
MCQeasy

A SOC analyst is creating a new analytics rule in Microsoft Sentinel to detect when a user account is disabled. The analyst needs to select a rule template that uses Microsoft Entra ID audit logs. Which rule type should the analyst choose?

A.Scheduled
B.NRT (Near-Real-Time)
C.Anomaly
D.Fusion
AnswerA

Scheduled query rules are the standard analytics rule type that execute a custom KQL query at a defined frequency over a set lookback window, and they can query any table in the Log Analytics workspace, including AuditLogs for Microsoft Entra ID. This makes them fully appropriate for detecting a specific event such as 'user account disabled' because the query can filter on event name and other properties. They also support configurable alert grouping, entity mapping, and incident auto-creation, giving the SOC analyst complete control over detection logic.

Why this answer

A scheduled query rule is the correct choice because it allows the analyst to define a KQL query that runs on a fixed interval against Microsoft Entra ID audit logs (AuditLogs table). This is the standard approach for built-in rule templates and provides full control over query logic and scheduling. While NRT rules also support AuditLogs, they are not used for standard rule templates and are more suited to custom high-frequency detections.

Exam trap

A common trap is confusing NRT rules with scheduled rules. NRT rules do support AuditLogs, but they are limited to specific tables and are not the standard for template-based detections; scheduled rules are the default choice for built-in templates that query AuditLogs.

How to eliminate wrong answers

Option B (NRT) is wrong because NRT rules are designed for near-real-time detection with a 1-minute latency and limited KQL functions, but they cannot query Microsoft Entra ID audit logs directly; they are optimized for high-frequency data like security events. Option C (Anomaly) is wrong because anomaly rules use machine learning to detect unusual patterns based on baseline behavior, not static events like account disablement, and they require specific anomaly detection configurations. Option D (Fusion) is wrong because Fusion is a correlation-based rule that automatically combines alerts from multiple sources to detect multi-stage attacks, and it does not allow custom KQL queries against audit logs.

708
MCQeasy

Your organization wants to use Microsoft Sentinel's built-in threat intelligence feeds to enrich alerts. Which data connector should you enable?

A.Office 365 connector.
B.Threat Intelligence - TAXII connector.
C.Microsoft 365 Defender connector.
D.Microsoft Defender for Cloud connector.
AnswerB

The Threat Intelligence - TAXII connector is the built-in Sentinel connector designed to pull structured threat indicators (STIX objects) from TAXII 2.0/2.1 feeds, such as those from trusted providers. It automatically ingests observables and indicators of compromise into the ThreatIntelligenceIndicator table, enabling analytics rules, threat hunting, and workbooks to reference up-to-date external threat intel. This directly meets the requirement for ingesting external threat intelligence feeds.

Why this answer

The Threat Intelligence - TAXII connector is the correct choice because it ingests threat intelligence feeds from STIX/TAXII servers, which are the standard protocol (Trusted Automated eXchange of Intelligence Indicator) used by built-in threat intelligence feeds. This connector allows Microsoft Sentinel to pull indicators of compromise (IOCs) from external threat intelligence sources, enriching alerts with context like malicious IPs, domains, or hashes.

Exam trap

The trap here is that candidates confuse 'threat intelligence feeds' with 'security alerts from Microsoft products,' leading them to choose the Microsoft 365 Defender or Defender for Cloud connectors, which ingest alerts but not the external threat intelligence indicators used for enrichment.

How to eliminate wrong answers

Option A is wrong because the Office 365 connector ingests audit logs and activity data from Exchange Online, SharePoint, and Teams, not threat intelligence feeds. Option C is wrong because the Microsoft 365 Defender connector ingests incidents and alerts from Defender products (e.g., Defender for Endpoint), not external threat intelligence feeds. Option D is wrong because the Microsoft Defender for Cloud connector ingests security alerts and recommendations from Azure and hybrid workloads, not threat intelligence feeds.

709
MCQmedium

A security analyst is investigating a potential business email compromise (BEC) campaign. The analyst wants to find all emails that were sent to external recipients from an internal user's mailbox that also had a login from an unusual location shortly after the email was sent. Which advanced hunting tables should the analyst query to get the email metadata and the sign-in details?

A.EmailEvents and AADSignInEventsBeta
B.EmailPostDeliveryEvents and DeviceLogonEvents
C.EmailAttachmentInfo and IdentityLogonEvents
D.EmailUrlInfo and CloudAppEvents
AnswerA

EmailEvents is the correct source for the send side of a business email compromise because it records the sender's SMTP address, recipient, subject, and send timestamp for every outbound message. AADSignInEventsBeta is equally essential for the sign-in side, capturing interactive and non-interactive authentication events against Microsoft Entra ID with fields like UserPrincipalName, IP address, and risk level. Joining on the sender's SMTP address to the sign-in UPN lets you correlate an anomalous sign-in with a suspicious email sent by that account, which directly ties the initial phish to attacker authentication.

Why this answer

EmailEvents stores email metadata (sender, recipient, subject, etc.) and AADSignInEventsBeta captures Azure AD sign-in logs, including location data. Joining these tables on the user's account object ID allows the analyst to correlate emails sent to external recipients with unusual sign-in locations shortly after the email was sent, directly addressing the BEC investigation scenario.

Exam trap

The trap here is that candidates confuse DeviceLogonEvents or IdentityLogonEvents with Azure AD sign-in logs, not realizing that AADSignInEventsBeta is the only table that captures cloud-based sign-in location data for Microsoft 365 services like Exchange Online.

How to eliminate wrong answers

Option B is wrong because EmailPostDeliveryEvents contains post-delivery actions (e.g., remediation, ZAP) and DeviceLogonEvents captures device-level logons (e.g., Windows sign-ins), not mailbox sign-ins or email metadata; this combination cannot correlate email sends with Azure AD sign-in locations. Option C is wrong because EmailAttachmentInfo only provides attachment metadata (file name, hash) and IdentityLogonEvents records identity-based logons (e.g., on-premises Active Directory), not Azure AD sign-ins with location details; it lacks the core email metadata needed. Option D is wrong because EmailUrlInfo stores URL click data from emails and CloudAppEvents tracks activities in cloud apps (e.g., Office 365 operations), but CloudAppEvents does not provide the precise sign-in location and timestamp needed for the unusual login correlation; it focuses on app-level actions rather than authentication events.

710
MCQmedium

A security analyst is investigating a phishing incident and needs to find the specific email message that was delivered to a user. The analyst knows the subject line and the sender domain. Which advanced hunting table should the analyst query?

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

EmailEvents is the central email record in the Microsoft 365 Defender advanced hunting schema. It stores one row per email delivery event and contains the message-level metadata needed for a phishing investigation: subject (Subject), sender and sender domain (SenderFromAddress/SenderMailFromDomain), recipient (RecipientEmailAddress), and the delivery status (DeliveryAction/DeliveryLocation). Therefore it is the correct starting point for correlating a suspected phish.

Why this answer

The EmailEvents table in Microsoft Defender XDR's advanced hunting schema contains the core properties of email messages, including subject line, sender domain, recipient details, and delivery status. Since the analyst needs to find a specific email by subject and sender domain, this table is the correct starting point for querying delivered messages.

Exam trap

The trap here is that candidates confuse EmailEvents with EmailPostDeliveryEvents, thinking post-delivery actions are needed to find the original message, but EmailEvents is the only table that stores the subject and sender domain for delivered emails.

How to eliminate wrong answers

Option B (EmailAttachmentInfo) is wrong because it focuses on attachment metadata (file name, hash, size) and does not include the subject line or sender domain fields needed to locate the email by those criteria. Option C (EmailUrlInfo) is wrong because it stores URLs extracted from email bodies or attachments, not the email's subject or sender domain. Option D (EmailPostDeliveryEvents) is wrong because it records actions taken after delivery (e.g., ZAP, user-reported phishing) and lacks the original subject line and sender domain required to identify the initial message.

711
Multi-Selecteasy

You are configuring Microsoft Sentinel analytics rules. Which THREE of the following are valid types of analytics rules in Microsoft Sentinel?

Select 3 answers
A.Fusion rule
B.Microsoft Security rule
C.Watchlist rule
D.Scheduled query rule
E.Playbook rule
AnswersA, B, D

Fusion rules are the correct answer here because they represent a built-in analytics rule type that uses advanced machine learning to correlate multiple low-severity signals across data sources, detecting multi-stage attacks in near real-time. Existing note: Fusion rules use advanced detection; this applies directly to the question's analytics rule configuration context.

Why this answer

In Microsoft Sentinel, the analytics rule types available when creating a rule include Scheduled query rules (D), which run KQL queries on a defined frequency and trigger alerts based on results; Fusion rules (A), which use Microsoft's machine-learning correlation engine to detect multi-stage attacks across signals; and Microsoft Security rules (B), which create incidents from alerts generated by Microsoft security products like Defender and Microsoft 365. These three are the standard rule types offered in the Sentinel analytics rule wizard. Watchlist rule (C) is not a rule type — watchlists are data sources used to enrich queries and can be referenced inside scheduled rules, not a standalone analytics rule.

Playbook rule (E) is also not a rule type — playbooks are Logic Apps used for automated response and are triggered by automation rules or analytics rules, not created as analytics rules themselves.

Exam trap

The trap here is that candidates confuse watchlists and playbooks with actual analytics rule types, as they are prominent features in Microsoft Sentinel but serve different purposes (data enrichment and automated response, respectively) rather than generating alerts or incidents.

712
MCQhard

Your security operations center uses Microsoft Sentinel and Microsoft Defender XDR. A new type of attack involves a user receiving a malicious email that triggers a macro, which then executes PowerShell to download a payload. You need to create a detection that correlates email, process creation, and network connection events from multiple Microsoft 365 Defender sources. What should you use?

A.Advanced hunting in Microsoft 365 Defender
B.Scheduled query rule in Microsoft Sentinel
C.Custom detection rule in Microsoft 365 Defender
D.Fusion rule in Microsoft Sentinel
AnswerA

Advanced hunting is the Kusto Query Language (KQL)-based hunting environment natively embedded in Microsoft 365 Defender, allowing you to query raw, already-collected data across email, process, network, and identity tables in a single portal. Unlike Sentinel scheduled queries, it does not require you to first configure data connectors or build a Log Analytics pipeline, and it provides the full raw schema optimized for investigative hunting. This is the correct starting point for cross-domain hunting.

Why this answer

Advanced hunting in Microsoft 365 Defender is the correct choice because it allows you to write Kusto Query Language (KQL) queries that can join data across multiple tables from different Microsoft 365 Defender sources, such as EmailEvents, DeviceProcessEvents, and DeviceNetworkEvents. This enables correlation of the email receipt, macro-triggered PowerShell process creation, and subsequent network connection to a malicious IP or domain in a single query, which is exactly what the scenario requires.

Exam trap

The trap here is that candidates often confuse the scope of custom detection rules in Microsoft 365 Defender, mistakenly believing they can cross-correlate multiple data sources, when in fact they are limited to a single table or entity type, whereas advanced hunting is designed for cross-table joins.

How to eliminate wrong answers

Option B is wrong because a scheduled query rule in Microsoft Sentinel operates on data ingested into the Log Analytics workspace, which may have latency and does not natively support real-time cross-product correlation across Microsoft 365 Defender tables without additional data connectors and schema mapping. Option C is wrong because a custom detection rule in Microsoft 365 Defender is limited to a single data source (e.g., only device events or only email events) and cannot join tables from different domains like EmailEvents and DeviceProcessEvents in one rule. Option D is wrong because a Fusion rule in Microsoft Sentinel is a prebuilt, machine-learning-based correlation that detects multistage attacks by combining alerts from multiple security products, but it cannot be customized to write a specific KQL query that joins raw event tables from Microsoft 365 Defender.

713
MCQhard

You are analyzing the query above in Microsoft 365 Defender advanced hunting. The goal is to identify potentially compromised accounts used only once. The query returns thousands of results including many normal single logons. How can you refine the query to reduce false positives?

A.Change the where clause to LogonCount > 1.
B.Remove the filter on AccountUpn endswith "@contoso.com".
C.Add a filter to only include accounts that have never logged on before.
D.Add a filter to exclude IP addresses from the corporate VPN range and common applications like Outlook Web Access.
AnswerD

Filtering out known-benign sources — corporate VPN egress addresses and common applications like Outlook Web Access — removes expected single logons, leaving anomalous ones. This directly targets the false-positive constraint by narrowing results to genuinely suspicious single-use accounts.

Why this answer

Adding a filter to exclude IP addresses from the corporate VPN range and common applications (like Outlook Web Access) helps reduce false positives by removing legitimate single logons that are expected. Option A (LogonCount > 1) would exclude the very accounts we are trying to find (single logons). Option B (removing the domain filter) would expand results but not necessarily reduce false positives.

Option C (accounts never logged on before) is too restrictive and may miss compromised accounts used only once.

714
Multi-Selectmedium

Your organization uses Microsoft Defender XDR and Microsoft Sentinel. You need to ensure that high-severity incidents are automatically escalated to the on-call security engineer via Microsoft Teams. Which three components should you configure?

Select 3 answers
A.A playbook that uses a condition to check severity and then sends a Teams message.
B.An automation rule in Microsoft Sentinel that triggers on incident creation with high severity.
C.A Microsoft Teams connector in the playbook to post a message to a channel.
D.An analytics rule that sends a Teams message when a high-severity alert fires.
E.A workbook that displays high-severity incidents for manual escalation.
AnswersA, B, C

A Microsoft Sentinel playbook is an Azure Logic Apps workflow that can inspect an incident's properties, such as severity, using a condition action. Once the condition evaluates that the severity meets the threshold, a subsequent action using the Teams connector posts the message to the specified channel. This is correct because playbooks are the automation components that run conditional logic and initiate external actions.

Why this answer

A playbook in Microsoft Sentinel can contain a condition action that evaluates the incident severity. If the severity is 'High', the playbook then uses a Microsoft Teams connector to send a message to the on-call security engineer, automating the escalation process.

Exam trap

The trap here is that candidates may confuse analytics rules with automation rules, thinking an analytics rule can directly send Teams messages, when in fact analytics rules only generate alerts and require a separate automation rule and playbook to perform actions like messaging.

715
MCQmedium

A company uses Microsoft Defender for Cloud with enhanced security features enabled. The security team wants to view a consolidated list of all security recommendations across multiple Azure subscriptions in a single view. Which blade should they navigate to in the Microsoft Defender for Cloud portal?

A.Regulatory compliance
B.Security posture
C.Workload protections
D.Inventory
AnswerB

The Security posture blade aggregates secure score, recommendations and regulatory compliance across every subscription and workload, giving the single consolidated view the team requires. It is the only blade that surfaces recommendations from all onboarded subscriptions together rather than per-resource.

Why this answer

The Security posture blade in Microsoft Defender for Cloud provides a consolidated view of all security recommendations across multiple Azure subscriptions, enabling the security team to assess and prioritize improvements. This blade aggregates recommendations from various security controls and displays them in a single, unified interface, directly addressing the requirement for a consolidated list.

Exam trap

The trap here is that candidates often confuse the Security posture blade with the Regulatory compliance blade, mistakenly thinking compliance views include all recommendations, whereas Regulatory compliance only shows recommendations mapped to specific compliance frameworks.

How to eliminate wrong answers

Option A is wrong because Regulatory compliance focuses on compliance standards (e.g., SOC 2, ISO 27001) and shows compliance posture against specific regulations, not a consolidated list of all security recommendations. Option C is wrong because Workload protections provides coverage and alerts for specific workload types (e.g., VMs, SQL servers) but does not aggregate all recommendations across subscriptions. Option D is wrong because Inventory lists all connected resources and their metadata, but it does not present security recommendations in a consolidated view.

716
Multi-Selecteasy

Which TWO of the following are common techniques used by attackers to bypass security controls that a threat hunter should look for?

Select 2 answers
A.Process injection into trusted processes
B.Enabling multi-factor authentication
C.Regular software updates
D.Enforcing strong password policies
E.DLL sideloading
AnswersA, E

Process injection writes malicious code into a trusted process's address space, so activity inherits that process's legitimacy and evades allow-listing and behavioural controls. Threat hunters detect it via anomalous memory allocation, thread creation or unexpected module loads.

Why this answer

Process injection into trusted processes (A) is a classic defense-evasion technique where an attacker writes malicious code into the memory space of a legitimate, trusted process (e.g., via CreateRemoteThread, APC injection, or process hollowing), allowing the payload to inherit the host process's privileges and blend into normal activity, which is exactly the kind of control bypass a threat hunter should detect. DLL sideloading (E) is another common evasion method in which a legitimate executable loads a malicious DLL from an attacker-controlled location due to insecure search-order or path resolution, hijacking trusted execution flow without triggering obvious alerts. By contrast, enabling multi-factor authentication (B), applying regular software updates (C), and enforcing strong password policies (D) are defensive hardening measures that strengthen security controls rather than techniques used to bypass them, so they are not attacker evasion methods.

717
MCQhard

Your Microsoft Sentinel workspace has multiple analytics rules generating incidents. You need to ensure that when an incident is created from a specific rule, a Teams message is sent to the security team. What should you configure?

A.Configure a workbook to send an email when an incident appears
B.Modify the incident creation rule in Microsoft 365 Defender
C.Add a custom analytics rule that triggers on incident creation
D.Create an automation rule that runs a playbook when the incident is created
AnswerD

An automation rule triggers a playbook on incident creation, satisfying the requirement to send a Teams message when a specific analytics rule generates an incident. The automation rule’s condition filters by the originating rule’s identifier, ensuring only incidents from that rule invoke the playbook, which uses a Teams connector to post the message.

Why this answer

Automation rules in Microsoft Sentinel can trigger on incident creation and execute a playbook, which can be configured to send a Teams message via a connector. This provides a native, low-code way to automate notifications without custom code or external tools.

Exam trap

The trap here is that candidates often confuse workbooks (visualization) or analytics rules (alert generation) with automation rules, which are the correct mechanism for triggering response actions like Teams messages on incident creation.

How to eliminate wrong answers

Option A is wrong because workbooks are visualization tools for dashboards and analytics, not for sending notifications or triggering actions like Teams messages. Option B is wrong because incident creation rules in Microsoft 365 Defender govern alert-to-incident correlation in the Defender portal, not in Sentinel, and cannot be modified to send Teams messages. Option C is wrong because custom analytics rules generate alerts from log data, not from incident creation events; they cannot directly trigger on incident creation or run playbooks.

718
MCQhard

Your organization uses Microsoft 365 Defender. An incident is created for a user who received a phishing email that contained a link to a malicious website. The user clicked the link but did not enter any credentials. The incident includes the alert 'Phishing delivered' from Microsoft Defender for Office 365. You need to remediate the incident and prevent future occurrences. The user is in the Finance department and frequently receives emails from external vendors. What is the best course of action?

A.Use Threat Explorer to delete the email from the user's mailbox and create a Safe Links policy to block the malicious URL.
B.Report the email to Microsoft for analysis and block the sender domain.
C.Provide security awareness training to the user and mark the incident as resolved.
D.Add the sender's domain to the Tenant Allow/Block List as allowed to avoid future false positives.
AnswerA

Threat Explorer permits soft-deleting the delivered phishing message from the mailbox, removing the threat, while a Safe Links policy rewrites and blocks the malicious URL at click time for all users, addressing the recurring external-vendor vector. Together they remediate the current incident and prevent recurrence.

Why this answer

The best remediation combines immediate containment with prevention: Threat Explorer (or the unified action center) lets you soft-delete or hard-delete the phishing email from the user's mailbox, and a Safe Links policy blocks the malicious URL so future clicks are neutralized. This addresses both the current incident and the recurring risk from external vendors, which is the correct incident-response sequence of contain, eradicate, and prevent.

Exam trap

SC-200 often tests the difference between reactive reporting and active remediation—candidates pick 'report to Microsoft' or 'train the user' because they sound responsible, but the exam rewards the option that removes the threat and blocks the vector.

How to eliminate wrong answers

Option B is wrong because reporting to Microsoft and blocking the sender domain is reactive and incomplete—it does not remove the already-delivered email from the mailbox, and blocking a domain can cause false positives for legitimate vendors. Option C is wrong because awareness training and closing the incident does nothing to remove the malicious email or block the URL, leaving the user and others exposed to the same link. Option D is wrong because adding the sender's domain to the allow list is the opposite of remediation—it would permit future phishing from that domain and defeat the Tenant Allow/Block List's protective purpose.

719
MCQhard

Your organization uses Microsoft Defender XDR and Microsoft Sentinel. You need to configure a solution that automatically blocks a user's account when a high-severity incident is generated. The solution must use built-in capabilities without custom code. What should you do?

A.Create an automation rule that triggers on incident creation with severity high, and runs a playbook that uses the 'Update user' action to disable the account.
B.Use a scheduled analytics rule that runs every hour and disables accounts found in the results.
C.Configure Microsoft Entra ID to automatically apply a conditional access policy blocking sign-ins when a high-severity alert is raised.
D.Create a playbook that uses the 'Run a query' action to find the device and then uses Microsoft Defender for Endpoint to isolate the device.
AnswerA

Automation rules in Microsoft Defender XDR can be configured to trigger immediately upon incident creation when the severity is high. The associated playbook (built on Azure Logic Apps) invokes the 'Update user' action, which calls the Microsoft Graph API to disable the specified Entra ID (Azure AD) account. This is the correct approach because it directly addresses the user account as the containment target and executes automatically without manual intervention.

Why this answer

Microsoft Sentinel automation rules can trigger on incident creation with a condition of severity equals high, and then run a playbook. The playbook can use the Microsoft Entra ID connector's 'Update user' action to disable the user account, which is a built-in capability requiring no custom code. This directly meets the requirement to automatically block a user's account when a high-severity incident is generated.

Exam trap

The trap here is that candidates may confuse device isolation (Microsoft Defender for Endpoint) with user account blocking (Microsoft Entra ID), or incorrectly assume that conditional access policies can be triggered by external alerts, when in fact they require specific risk signals from Microsoft Entra ID Protection.

How to eliminate wrong answers

Option B is wrong because scheduled analytics rules are designed to generate alerts based on log queries, not to perform remediation actions like disabling accounts; they lack the ability to directly execute actions on users. Option C is wrong because Microsoft Entra ID conditional access policies cannot be automatically triggered by a high-severity alert from Microsoft Sentinel or Defender XDR; they rely on risk signals from Microsoft Entra ID Protection or session controls, not external incident severity. Option D is wrong because it focuses on isolating a device using Microsoft Defender for Endpoint, which does not block a user's account; the question specifically requires blocking the user account, not the device.

720
MCQeasy

An analyst is investigating a phishing campaign that targeted multiple users. The analyst needs to identify if any users clicked a malicious link in the email. Which Microsoft Defender for Office 365 feature should be used?

A.Safe Attachments
B.Threat Explorer
C.Attack Simulator
D.Safe Links
AnswerB

Threat Explorer in Microsoft Defender for Office 365 provides real-time, detailed reporting on email threats, letting analysts filter by URL clicks and identify exactly which recipients interacted with the malicious link during the phishing campaign investigation.

Why this answer

Threat Explorer (also known as Explorer) in Microsoft Defender for Office 365 provides a real-time, interactive view of threat data, including email delivery status and user actions such as clicks on malicious links. It allows analysts to filter by 'Click action' to identify users who clicked a URL that was determined to be malicious, making it the correct tool for this investigation.

Exam trap

The trap here is that candidates often confuse the protection features (Safe Links and Safe Attachments) with the investigation tool (Threat Explorer), assuming that because Safe Links blocks malicious clicks, it also provides historical click reports, when in fact Threat Explorer is the dedicated hunting and investigation tool for analyzing user actions.

How to eliminate wrong answers

Option A is wrong because Safe Attachments is a protection feature that detonates email attachments in a sandbox environment to detect malware, but it does not track or report user clicks on links. Option C is wrong because Attack Simulator is a training and simulation tool used to launch simulated phishing attacks to test user awareness, not to investigate past real-world phishing campaigns. Option D is wrong because Safe Links is a protection feature that rewrites URLs and checks them at time of click to block malicious destinations, but it does not provide a historical log or report of which users clicked a specific malicious link in a past campaign.

721
MCQmedium

Your organization uses Microsoft Sentinel. You receive an incident for a potential data exfiltration involving a sensitive blob storage container. You need to determine if the data was accessed from an unusual IP address. What should you do?

A.Modify the analytics rule that triggered the incident.
B.Run a playbook to collect IP information.
C.Open the Sentinel workbook for storage monitoring.
D.Use the Incident details pane to review the entity timeline.
AnswerD

The Incident details pane includes an Entities tab where the entity timeline displays a chronological sequence of activities associated with entities such as IP addresses, hosts, and accounts. This view aggregates data from multiple sources—including alerts, events, and logs—allowing the analyst to see what an IP did before, during, and after the incident. It requires no additional configuration and directly supports the investigation by revealing behavioral patterns and attack paths.

Why this answer

The Incident details pane in Microsoft Sentinel includes an entity timeline that shows activities and events associated with entities (such as IP addresses, accounts, hosts) tied to the incident. Reviewing the entity timeline lets you see whether the blob storage was accessed from an unusual IP and correlate that IP with other activity. This is the direct investigative step for the question.

Exam trap

SC-200 often tests the distinction between investigation actions (reviewing entity timelines, running KQL) and response/automation actions (playbooks) or configuration actions (editing analytics rules) — the trap is picking a response or config action when the question asks how to investigate.

How to eliminate wrong answers

Option A is wrong because modifying the analytics rule changes detection logic going forward; it does not help investigate the current incident's IP access. Option B is wrong because running a playbook is a response automation action (e.g., block IP, notify), not an investigation step to determine whether an unusual IP accessed the data — and playbooks do not inherently 'collect IP information' for analysis. Option C is wrong because a workbook is a visualization/reporting tool; it may show aggregate storage metrics but does not provide the entity-level timeline needed to determine if a specific unusual IP accessed the container.

722
MCQmedium

Your organization uses Microsoft Defender for Cloud Apps. You detect a suspicious app that has high data access and unusual API calls. You want to automatically block the app and notify the user. What should you implement?

A.Create an access policy that blocks the app based on the risk level.
B.Create an app governance policy that automatically blocks the app and sends a notification to the user.
C.Create a session policy to monitor the app's API calls.
D.Create a DLP policy to prevent data exfiltration from the app.
AnswerB

App governance policies in Defender for Cloud Apps are specifically designed to govern OAuth apps and can perform automated actions such as disabling or blocking an app when suspicious behavior is detected. When a policy triggers, it can block the app from accessing resources and send notification emails to the configured recipients, including the user or admin. This directly matches the stated requirement, making it the correct choice.

Why this answer

App governance policies in Microsoft Defender for Cloud Apps are specifically designed to govern OAuth-enabled apps that have been granted permissions to access organizational data. When an app exhibits suspicious behavior like high data access and unusual API calls, an app governance policy can automatically block the app and send a notification to the user, directly addressing the requirement to both block and notify.

Exam trap

The trap here is that candidates confuse 'blocking an app' (which requires an app governance policy) with 'blocking user access to an app' (which is done via an access policy), leading them to choose the access policy option even though it does not block the app itself or notify the user.

How to eliminate wrong answers

Option A is wrong because an access policy controls user access to apps based on risk level (e.g., blocking access from risky IPs), but it does not block the app itself or send notifications to the user about the app's behavior. Option C is wrong because a session policy monitors and controls user sessions in real-time (e.g., preventing download of sensitive data), but it does not block the app or notify the user about the app's suspicious activity. Option D is wrong because a DLP policy prevents data exfiltration by scanning content in transit or at rest, but it does not block an app or notify the user about the app's API calls or data access patterns.

723
MCQhard

During an incident response, you need to collect forensic data from Microsoft Defender for Endpoint (MDE) on a remote device that is currently offline. What is the best approach?

A.Initiate a live response session when the device comes online
B.Wait until the device is online and then collect manually
C.Run a remotely scheduled antivirus scan
D.Collect the data from the device's cloud store
AnswerA

Live response in Microsoft Defender for Endpoint is the correct forensic data collection method because it provides an interactive, audited remote shell on the device. Once the device is online, you can run built-in commands such as 'collect' to capture evidence like running processes, registry data, event logs, and sensitive files in a structured package. Unlike manual methods, this session uses Microsoft's authorized API and records all commands for chain of custody, making it the preferred incident-response approach.

Why this answer

When a device is offline, Microsoft Defender for Endpoint cannot establish a live response session because the device must be connected to the MDE service to execute commands. Initiating a live response session when the device comes online is the best approach because it allows you to run forensic collection commands (e.g., 'getfile', 'run') directly on the device via the MDE API, without requiring manual intervention or additional infrastructure.

Exam trap

The trap here is that candidates assume MDE can collect forensic data from a cloud store or via scheduled scans, but MDE's live response is the only native method for on-demand forensic collection from a remote device, and it requires the device to be online.

How to eliminate wrong answers

Option B is wrong because waiting until the device is online and then collecting manually is inefficient and error-prone; it lacks the structured, auditable, and remote execution capabilities that live response provides, and manual collection may miss critical artifacts. Option C is wrong because running a remotely scheduled antivirus scan only checks for malware and does not collect forensic data such as memory dumps, registry hives, or event logs. Option D is wrong because MDE does not maintain a 'cloud store' of raw forensic data from offline devices; the cloud store contains telemetry and alerts, not full disk or memory images that can be collected on demand.

724
MCQeasy

Your organization uses Microsoft Sentinel and you need to ensure that incidents are automatically closed when a related playbook completes successfully. What should you configure?

A.Create an automation rule that triggers after the playbook runs and closes the incident
B.Add a 'Close incident' action in the playbook
C.Configure the analytics rule to close incidents automatically
D.Use a workbook to manually close incidents
AnswerA

An automation rule is a native Sentinel capability that can be configured with the 'When incident is updated' trigger and a condition that matches the playbook's execution context, such as a tag the playbook added. After that condition is met, the rule's 'Change status' action can set the incident to 'Closed', giving you a declarative, no-code closure path that runs immediately after the playbook finishes. This keeps the closure logic outside the Logic App, so you can modify or reuse it without redeploying the playbook.

Why this answer

Automation rules in Microsoft Sentinel can be configured to trigger after a playbook completes, and one of the available actions is to close an incident. This ensures that the incident is automatically closed only when the playbook has successfully finished, providing a reliable and automated closure mechanism without manual intervention.

Exam trap

The trap here is that candidates often think adding a 'Close incident' action inside the playbook is sufficient, but they overlook that this action closes the incident immediately when executed, not after the entire playbook completes, which can lead to premature closure if the playbook has subsequent steps that fail.

How to eliminate wrong answers

Option B is wrong because adding a 'Close incident' action directly inside the playbook would close the incident immediately when that action runs, not necessarily after the entire playbook completes successfully; if the playbook fails later, the incident would already be closed, which is incorrect. Option C is wrong because analytics rules in Microsoft Sentinel are used to generate alerts and incidents based on data queries, not to close incidents automatically after a playbook runs. Option D is wrong because workbooks are visualization tools for data analysis and reporting, not for automating incident closure; they require manual action to close incidents.

725
MCQmedium

An organization uses Microsoft 365 Defender. An automated investigation on a device identifies a malicious file and blocks it. The analyst now wants to allow a specific trusted application that was incorrectly blocked, while keeping other malicious files blocked. Which action should the analyst take from the device's entity page?

A.Initiate a live response session and delete the file manually.
B.Use the 'Add indicator' feature to create a custom IOC for the file hash with action 'Allow'.
C.Change the automated investigation settings to 'No action' and rerun investigation.
D.Collect the file for analysis; the allow decision must be made by Microsoft after analysis.
AnswerB

Creating a custom indicator for the file hash with the 'Allow' action instructs Microsoft Defender for Endpoint (and connected Microsoft 365 Defender services) to treat the file as trusted, overriding the automated investigation's block. This indicator is a tenant-level override that applies to all monitored devices and allows the file to run without triggering future alerts. After adding the indicator, the file is permitted and the automated investigation's block is effectively removed.

Why this answer

The 'Add indicator' feature in Microsoft Defender XDR allows analysts to create custom indicators of compromise (IOCs) based on file hashes, IPs, or domains. By setting the action to 'Allow' for the specific file hash, the analyst can override the automated block for that trusted application while keeping other malicious files blocked. This is the correct approach because it provides granular control without affecting the overall automated investigation settings.

Exam trap

The trap here is that candidates may confuse the 'Add indicator' feature with manual file deletion or changing global investigation settings, not realizing that a custom IOC with an Allow action is the precise mechanism to override a block for a specific trusted file.

How to eliminate wrong answers

Option A is wrong because initiating a live response session to delete the file manually does not create an allow rule; it only removes the file, and the block action from the automated investigation would still prevent the application from running. Option C is wrong because changing the automated investigation settings to 'No action' would disable all automated responses for future detections, not selectively allow a specific file. Option D is wrong because collecting the file for analysis does not immediately allow the file; Microsoft analysis is for threat intelligence, not for overriding a block on a trusted application.

726
MCQhard

You are hunting for lateral movement in your environment. In Microsoft Defender for Identity, which activity is a strong indicator of a potential pass-the-hash attack?

A.A user logging on with a smart card.
B.An NTLM authentication originating from a machine that is not the user's usual machine.
C.A remote desktop connection from a non-admin workstation to a domain controller.
D.A service account logging on to multiple servers simultaneously.
AnswerB

NTLM authentication originating from a machine the user does not normally use is a strong lateral movement indicator because NTLM uses a password hash in a challenge-response protocol, and attackers often employ pass-the-hash techniques to authenticate from a compromised host. In a Windows environment, this would appear as Event ID 4624 with LogonType 3 and NTLM as the authentication package, combined with a source hostname or IP that violates the user's typical logon pattern. This aligns with stolen credentials or hash theft, as a legitimate user would almost always authenticate from their known workstations or VPN exit points, so an unexpected source machine is statistically suspicious.

Why this answer

Pass-the-hash attacks involve using a captured NTLM hash to authenticate without knowing the plaintext password. In Defender for Identity, a strong indicator is NTLM authentication originating from a machine that is not the user's usual machine, because the attacker is moving laterally using the hash from a compromised host. This behavior is flagged as suspicious because it deviates from normal user logon patterns.

Exam trap

SC-200 often tests the specific indicators of pass-the-hash, and candidates may confuse it with other suspicious activities like service account logons or smart card usage. The trap is selecting a common but non-specific event instead of the NTLM authentication from an unusual machine.

How to eliminate wrong answers

Option A is wrong because smart card logons use certificate-based authentication (PKINIT) and are not associated with pass-the-hash attacks. Option C is wrong because a remote desktop connection from a non-admin workstation to a domain controller is a common administrative activity and not a specific indicator of pass-the-hash. Option D is wrong because service accounts logging on to multiple servers simultaneously is typical for service accounts and does not specifically indicate pass-the-hash.

727
Multi-Selectmedium

Which THREE are valid incident management features in Microsoft Sentinel?

Select 3 answers
A.Incident merging
B.Incident creation from analytics rules
C.Incident comments
D.Incident tasks
E.Incident templates
AnswersB, C, D

Analytics rules are the primary engine that creates Microsoft Sentinel incidents. When a rule's query detects a security signal and its trigger conditions are met, the rule generates an incident that appears in the Incidents blade. This incident creation is the standard path through which most detections become actionable, and it is the core incident-management feature the question asks about.

Why this answer

Incident creation from analytics rules is a core feature in Microsoft Sentinel. When an analytics rule detects a threat or suspicious activity, it automatically generates an incident, which serves as the primary object for investigation and response. This automation is fundamental to Sentinel's security orchestration, automation, and response (SOAR) capabilities.

Exam trap

The trap here is that candidates may confuse 'incident merging' with the ability to link related incidents or alerts, but Sentinel does not have a native 'merge' operation—it only supports grouping alerts under a single incident or manually linking incidents via the 'Add related incidents' action.

728
MCQhard

A company has multiple Azure subscriptions under a management group. They want to ensure that all VMs across all subscriptions have Microsoft Defender for Cloud's vulnerability assessment solution (using the Microsoft Defender Vulnerability Management engine) enabled. They also want to automatically remediate any non-compliant VMs by enabling the VA solution when a VM is missing it. Which combination of policy initiatives and automation should they use?

A.Assign the 'Azure Security Benchmark' initiative at the management group, enable automatic remediation for the 'Vulnerability assessment should be enabled on your virtual machines' policy.
B.Assign the 'Defender for Cloud' initiative with the 'Configure machines to receive a vulnerability assessment provider' policy, and configure a remediation task with a deployment script.
C.Assign the 'Azure Security Benchmark' initiative and create an Azure Automation runbook triggered by a compliance alert to enable VA.
D.Assign the 'Configure machines to receive a vulnerability assessment provider' policy with 'DeployIfNotExists' effect and set it to auto-remediate at the management group-level scope.
AnswerD

The built-in DeployIfNotExists policy 'Configure machines to receive a vulnerability assessment provider' automatically installs the vulnerability assessment agent/extension on any virtual machine that does not have it. Assigning this policy at the management group scope makes the effect apply to every subscription and VM under that group, and enabling the remediation task in the assignment ensures existing non-compliant VMs are also remediated, not just new ones. This approach couples detection with deployment, which is the key difference from audit-only options, and it uses the standard Azure Policy lifecycle without custom scripts or runbooks.

Why this answer

The 'Configure machines to receive a vulnerability assessment provider' policy with the 'DeployIfNotExists' effect directly deploys the Microsoft Defender Vulnerability Management (MDVM) extension to any VM that lacks it. By assigning this policy at the management group scope and enabling automatic remediation, the policy will automatically remediate non-compliant VMs without requiring additional runbooks or scripts, fulfilling both the detection and automatic remediation requirements.

Exam trap

The trap here is that candidates often confuse 'AuditIfNotExists' policies (which only report compliance) with 'DeployIfNotExists' policies (which can automatically remediate), leading them to choose options that rely on audit-only policies or external automation when a built-in deployment policy with auto-remediation is available.

How to eliminate wrong answers

Option A is wrong because the 'Azure Security Benchmark' initiative includes the 'Vulnerability assessment should be enabled on your virtual machines' policy with an 'AuditIfNotExists' effect, which only audits compliance and does not automatically enable the VA solution; automatic remediation for an audit policy is not supported. Option B is wrong because while the 'Defender for Cloud' initiative contains the correct policy, the suggestion to configure a remediation task with a deployment script is unnecessary and less reliable than using the built-in 'DeployIfNotExists' effect with auto-remediation, which directly deploys the required extension. Option C is wrong because creating an Azure Automation runbook triggered by a compliance alert introduces complexity and latency, and the 'Azure Security Benchmark' initiative's audit-only policy cannot trigger automatic remediation; the correct approach uses a 'DeployIfNotExists' policy with auto-remediation.

729
MCQeasy

You are deploying an ARM template to create a saved search in a Log Analytics workspace. The template fails with an error that the resource type is not valid for Microsoft Sentinel. What is the most likely reason?

A.The query is invalid KQL.
B.The apiVersion is incorrect.
C.The resource type should be Microsoft.SecurityInsights/alertRules, not OperationalInsights/workspaces/savedSearches.
D.The name format is incorrect.
AnswerC

To create a Microsoft Sentinel analytics rule, the template must use Microsoft.SecurityInsights/alertRules as the resource type, because scheduled analytics rules are owned by the SecurityInsights resource provider, not by Log Analytics. A saved search only stores a reusable KQL query and returns results manually; it does not generate alerts or run on a schedule. Deploying Microsoft.OperationalInsights/workspaces/savedSearches therefore creates the query artifact but never satisfies the requirement to provision a Sentinel alert rule, making this the correct diagnosis.

Why this answer

Microsoft Sentinel does not use the OperationalInsights/workspaces/savedSearches resource type for its analytics rules. Instead, Sentinel uses the Microsoft.SecurityInsights/alertRules resource type to define detection rules. The ARM template fails because the resource type specified is not recognized as valid for Sentinel deployments.

Exam trap

The trap here is that candidates confuse Log Analytics saved searches with Microsoft Sentinel analytics rules, assuming both use the same resource type, when in fact Sentinel requires the Microsoft.SecurityInsights/alertRules type.

How to eliminate wrong answers

Option A is wrong because an invalid KQL query would cause a validation or runtime error, not a 'resource type not valid' error. Option B is wrong because an incorrect apiVersion would produce an 'Unsupported api-version' error, not a resource type validation error. Option D is wrong because an incorrect name format would result in a naming validation error, not a resource type error.

730
MCQmedium

Your organization uses Microsoft Sentinel. A fusion incident was created involving multiple alerts from different sources. You need to investigate the incident to determine if it is a true positive. What is the first step you should take?

A.Run a KQL query on the raw logs to see if the alerts are connected.
B.Assign the incident to a senior analyst for further investigation.
C.Review the incident timeline and entity mapping in the incident details.
D.Close the incident as a false positive if the alerts seem unrelated.
AnswerC

Opening the incident details and examining the timeline and entity mapping is the correct first step because it shows the sequential events of the attack and the relationships between involved entities such as users, hosts, and IP addresses. Sentinel's fusion engine generates this correlation by combining multiple low-fidelity alerts across the attack chain, and the timeline helps you see if the alerts are sequentially connected. The entity mapping directly reveals shared indicators that might otherwise look disconnected when reading alert titles alone.

Why this answer

The first step in investigating a Fusion incident in Microsoft Sentinel is to review the incident timeline and entity mapping. This provides a consolidated view of all correlated alerts, their timestamps, and the entities involved (e.g., IP addresses, user accounts), enabling you to quickly assess whether the alerts are logically connected and indicative of a true positive attack chain. Starting with this high-level overview is efficient before diving into raw logs.

Exam trap

The trap here is that candidates often jump to running KQL queries (Option A) because they associate investigation with raw log analysis, but the correct first step is to use Sentinel's built-in incident visualization to understand the correlation before querying.

How to eliminate wrong answers

Option A is wrong because running a KQL query on raw logs is a later investigative step; you should first use the built-in incident details to understand the correlation before querying underlying data. Option B is wrong because assigning the incident to a senior analyst bypasses the initial triage responsibility of the current analyst, who should first review the incident details to determine if escalation is necessary. Option D is wrong because closing an incident as a false positive without reviewing the timeline and entity mapping violates proper incident response procedures and could miss a real threat.

731
MCQmedium

A company uses Microsoft Defender for Cloud's Just-In-Time (JIT) VM access to secure its Azure virtual machines. A security analyst needs to grant a developer temporary RDP access to a specific VM for debugging purposes. Instead of using the default request approval flow, the analyst wants to configure an exemption so that the developer's access request never triggers a recommendation for that VM. Which action must the analyst perform?

A.Approve the access request once from the JIT blade and set a long expiration.
B.Add an exemption for the VM on the 'Management ports should be closed on just-in-time based virtual machines' recommendation.
C.Configure a custom Azure Policy to allow open management ports for that VM.
D.Disable the JIT solution for the entire subscription from the Defender for Cloud environment settings.
AnswerB

Creating an exemption for the specific VM on the 'Management ports should be closed on just-in-time based virtual machines' recommendation is the correct approach. This exclusion is resource-scoped and suppresses the recommendation for that VM alone, allowing permanent open management ports without generating alerts or affecting compliance state. Exemptions are a standard Defender for Cloud mechanism for legitimate exceptions, and they require the appropriate permissions to create, such as Security Admin or Resource Policy Contributor.

Why this answer

To prevent a specific VM from triggering a recommendation for open management ports, you must add an exemption directly on the 'Management ports should be closed on just-in-time based virtual machines' recommendation in Defender for Cloud. This exemption tells the recommendation engine to exclude that VM from compliance evaluation, so no alert or recommendation is generated for it. Approving a request with a long expiration does not suppress the underlying recommendation; it only grants temporary access.

Exam trap

The trap here is that candidates confuse 'approving a request with a long expiration' with 'exempting the VM from the recommendation,' not realizing that an exemption is a separate Azure Policy concept that permanently suppresses the recommendation for that resource.

How to eliminate wrong answers

Option A is wrong because approving a request with a long expiration still leaves the recommendation active and will continue to appear in the security recommendations list; it does not create an exemption. Option C is wrong because configuring a custom Azure Policy to allow open management ports would override the JIT policy but does not create an exemption on the specific recommendation; it would instead change the compliance state for all VMs under that policy scope, which is not the targeted exemption requested. Option D is wrong because disabling JIT for the entire subscription removes the protection from all VMs and is an overly broad action that does not meet the requirement to exempt only a single VM from the recommendation.

732
MCQmedium

A company uses Microsoft Sentinel as its SIEM. The security team is investigating an incident that involves multiple alerts from different data sources. The team wants to see a timeline of all related activities across all data sources in one view. Which Microsoft Sentinel feature should they use?

A.Workbooks
B.Incident timeline
C.Investigation graph
D.Hunting page
AnswerB

The incident timeline aggregates alerts, bookmarks and entities from every connected data source into a single chronological view, satisfying the requirement to correlate related activities across sources during an investigation. Unlike hunting queries, which return raw results per query, it presents the whole incident's progression in one pane.

Why this answer

The Incident timeline in Microsoft Sentinel provides a unified chronological view of all alerts and events related to an incident. Option A is wrong because Workbooks are for custom dashboards and reporting, not for viewing incident timelines. Option C is wrong because the Investigation graph focuses on entity relationships, not a chronological timeline.

Option D is wrong because the Hunting page is for proactive threat hunting, not incident investigation.

733
MCQmedium

Your organization uses Microsoft Defender for Identity (MDI) to monitor on-premises Active Directory. You want to forward MDI alerts to Microsoft Sentinel. What should you configure?

A.Microsoft 365 Defender connector
B.Azure Advanced Threat Protection connector
C.Microsoft Defender for Cloud Apps connector
D.Microsoft Defender for Identity connector
AnswerD

The Microsoft Defender for Identity connector is the direct and supported data connector in Sentinel for ingesting identity security alerts from Microsoft Defender for Identity. It authenticates to the MDI API and pulls raw alerts—including suspected lateral movement, account enumeration, and domain controller compromise—into the SecurityAlert table with the provider name 'MicrosoftDefenderForIdentity', making it the correct choice for this organization.

Why this answer

Microsoft Defender for Identity (MDI) alerts are forwarded to Microsoft Sentinel by configuring the Microsoft Defender for Identity data connector. This connector ingests MDI security alerts, such as suspicious Kerberos activity or lateral movement attempts, directly into Sentinel for advanced correlation and incident response. The connector uses the Microsoft Graph Security API to pull alerts from the MDI service, enabling seamless integration without additional agents.

Exam trap

The trap here is that candidates confuse the Microsoft Defender for Identity connector with the Microsoft 365 Defender connector, assuming the unified portal connector is the correct way to forward MDI alerts, but the exam expects the specific product-named connector for direct integration.

How to eliminate wrong answers

Option A is wrong because the Microsoft 365 Defender connector ingests alerts from the unified Microsoft 365 Defender portal (which includes MDI, MDE, and MDCA), but it is not the specific connector for forwarding MDI alerts directly; using it would require enabling the broader M365D integration, which may include unrelated data. Option B is wrong because Azure Advanced Threat Protection (Azure ATP) is the predecessor to Microsoft Defender for Identity; the current product is MDI, and the connector name has been updated to reflect the rebranding, so selecting this option indicates confusion with the legacy name. Option C is wrong because the Microsoft Defender for Cloud Apps connector is designed to ingest alerts from Microsoft Defender for Cloud Apps (formerly Microsoft Cloud App Security), not from MDI; it handles shadow IT and SaaS app anomalies, not on-premises Active Directory threats.

734
MCQeasy

Which Microsoft Sentinel feature allows you to query data across multiple workspaces in a single KQL query?

A.The union operator with workspace names
B.The externaldata operator with workspace URLs
C.The workspace() function in KQL
D.The join operator with workspace identifiers
AnswerC

The workspace() function is a KQL table-scoping function that accepts a workspace name or resource ID and returns a table reference for that workspace, allowing cross-workspace queries in a single KQL statement. In Microsoft Sentinel, analysts commonly use workspace() with the union operator to combine security tables from multiple workspaces, for example: union workspace("sentinel-ws1").SecurityEvent, workspace("sentinel-ws2").SecurityEvent. This is the correct feature because it is purpose-built to reference other Log Analytics workspaces from within your query.

Why this answer

The workspace() function in KQL is specifically designed to reference a workspace by its identifier, allowing a single query to pull tables from multiple Microsoft Sentinel workspaces (or Log Analytics workspaces) without leaving the current query context. It is the documented cross-workspace query mechanism in Sentinel, and it can be combined with union to aggregate results across workspaces.

Exam trap

SC-200 often tests whether candidates confuse KQL operators (union, join, externaldata) with the workspace() function that actually provides cross-workspace scope — the trap is assuming union or join can name a workspace directly.

How to eliminate wrong answers

Option A is wrong because the union operator alone cannot resolve workspace names — it only combines result sets from tables/functions already in scope; you still need workspace() to reference the remote workspace. Option B is wrong because externaldata is used to pull data from external storage URIs (blobs, files) into a query, not to query another Sentinel/Log Analytics workspace. Option D is wrong because join is a row-combining operator that requires both sides to already be resolvable tables; it does not provide any cross-workspace resolution capability on its own.

735
Multi-Selecthard

A SOC analyst in Microsoft Sentinel needs to create an automation rule that triggers a playbook when a new incident is created and the incident severity is 'High'. Additionally, the playbook should only run if the incident is not already assigned to an analyst. Which two conditions must the analyst include in the automation rule? (Select all that apply.) (Choose 2.)

Select 2 answers
A.Condition: 'Severity' equals 'High'
B.Condition: 'Assigned to' equals 'null'
C.Condition: 'Status' equals 'New'
D.Condition: 'Provider' contains 'Microsoft Sentinel'
AnswersA, B

In Microsoft Sentinel, the Severity field on an incident reflects the impact level set by the analytics rule that generated it. Filtering on 'High' is meaningful because it limits the automation to incidents requiring urgent attention, which aligns with a SOC workflow that prioritizes critical alerts. This condition, however, does not address ownership, so it is a correct but partial filter for the playbook's purpose.

Why this answer

The automation rule must trigger only when the incident severity is 'High'. In Microsoft Sentinel, automation rules evaluate conditions against incident properties, and the 'Severity' condition filters incidents by their assigned severity level. This ensures the playbook runs exclusively for high-severity incidents, aligning with the SOC's requirement to prioritize critical alerts.

Exam trap

The trap here is that candidates often confuse the 'Status' condition with the 'Assigned to' condition, thinking a 'New' status is necessary, but the automation rule triggers on incident creation by default, and the 'Assigned to' null check is the precise way to enforce the unassigned requirement.

736
MCQmedium

Your organization uses Microsoft Defender for Identity. You need to monitor for potential lateral movement attacks using pass-the-hash techniques. Which entity type in Microsoft Defender for Identity should you focus on in the security alert timeline?

A.IP address
B.Account
C.Device
D.Computer
AnswerB

This is the correct answer because Defender for Identity's pass-the-hash detection is specifically designed to identify the identity (user account) whose NTLM hash was captured and then replayed to authenticate to another machine. The alert entry shows the compromised account as the primary entity, with supporting details such as the source and destination computers, protocols, and timestamps. The investigation should focus on resetting that account's credentials and hunting for other activities performed by it, since the account itself is the root of the lateral movement.

Why this answer

In Microsoft Defender for Identity, lateral movement attacks using pass-the-hash (PtH) techniques are tracked at the account entity level because the attacker reuses a stolen NTLM hash to authenticate as a specific user account across multiple devices. The security alert timeline groups related activities by the compromised account, enabling analysts to trace the attacker's steps from the initial breach to subsequent resource access. Focusing on the account entity provides the clearest view of the authentication attempts and successful logons that indicate PtH behavior.

Exam trap

The trap here is that candidates often choose 'Device' or 'Computer' because they think lateral movement is about moving between machines, but Microsoft explicitly tracks the stolen credential (account) as the primary entity in PtH alerts, since the attack follows the user identity, not the hardware.

How to eliminate wrong answers

Option A is wrong because an IP address is a network-layer identifier that can change or be spoofed; Defender for Identity correlates PtH alerts to the account that performed the authentication, not the ephemeral source IP. Option C is wrong because a device entity represents a specific machine, but PtH attacks follow the stolen credential (account) across multiple devices, so focusing on a single device would miss lateral movement to other hosts. Option D is wrong because 'Computer' is essentially synonymous with 'Device' in this context and suffers from the same limitation—it does not capture the cross-device credential reuse that defines PtH lateral movement.

737
MCQeasy

A security analyst is using KQL in Microsoft Sentinel to hunt for potential data exfiltration by a user who has been sending unusually large amounts of data to an external IP address. Which KQL operator should the analyst use to identify the top source IP addresses and total bytes sent over the last 7 days?

A.... | where SentBytes > 1000000 | project SourceIP, SentBytes
B.... | extend TotalBytes=SentBytes | summarize count() by SourceIP
C.... | project SourceIP, SentBytes | sort by SentBytes desc
D.... | summarize TotalBytes=sum(SentBytes) by SourceIP | top 10 by TotalBytes desc
AnswerD

This is the correct approach because the summarize operator groups all events by SourceIP and calculates TotalBytes as the sum of SentBytes for each group, converting row-level byte counts into a single aggregate metric per unique IP address. The subsequent top 10 by TotalBytes desc operator then sorts those aggregated results in descending order and returns only the first ten rows, which are the ten source IPs with the highest total outbound byte volume. Using 'top' after 'summarize' is also more efficient than 'sort' followed by 'take' because Kusto can discard non-top records during execution. This pipeline precisely satisfies the goal of identifying the top source IPs by total bytes sent and is the only option that combines both grouping and aggregation with a limiting operation.

Why this answer

To identify the top source IPs by total bytes sent over 7 days, the analyst needs to aggregate bytes per source IP and then rank them. `summarize TotalBytes=sum(SentBytes) by SourceIP | top 10 by TotalBytes desc` does exactly that: it sums SentBytes grouped by SourceIP and returns the top 10 by total bytes, which is the correct KQL pattern for this hunt.

Exam trap

SC-200 often tests whether candidates confuse `count()` with `sum()` in `summarize`, or use `project`/`sort` on raw rows instead of aggregating first — the exam wants the aggregation-then-rank pattern.

How to eliminate wrong answers

Option A is wrong because `where SentBytes > 1000000 | project SourceIP, SentBytes` only filters and projects individual rows — it does not aggregate total bytes per source IP, so it cannot show the top senders. Option B is wrong because `summarize count() by SourceIP` counts the number of events per source IP, not the total bytes sent, so it answers a different question. Option C is wrong because `project SourceIP, SentBytes | sort by SentBytes desc` sorts individual events, not aggregated totals, and does not limit to the top 10 source IPs by summed bytes.

738
MCQmedium

Your organization uses Microsoft Defender for Cloud Apps. You need to create a policy that alerts when a user downloads more than 10 files from SharePoint in 5 minutes. What type of policy should you create?

A.Activity policy
B.App permissions policy
C.Session policy
D.Anomaly detection policy
AnswerA

In Microsoft Defender for Cloud Apps, an activity policy is a policy type that lets you create custom detection rules based on specific user activities, with thresholds and parameters you define. For example, you can set a threshold for multiple failed sign-ins or unusual file downloads, and it triggers alerts when those conditions are met. Unlike built-in anomaly detection which uses machine learning, activity policies are fully customizable by the administrator to match your organization's risk requirements.

Why this answer

An Activity policy in Microsoft Defender for Cloud Apps is designed to monitor and respond to specific user activities, such as file downloads from SharePoint, based on predefined thresholds. By configuring the policy with a threshold of more than 10 downloads within 5 minutes, it triggers an alert when the activity exceeds this limit, enabling detection of potential data exfiltration or anomalous user behavior.

Exam trap

The trap here is that candidates often confuse Activity policies with Anomaly detection policies, assuming any threshold-based alert is 'anomaly detection,' but Activity policies use explicit, static thresholds while Anomaly detection policies use dynamic, machine-learned baselines.

How to eliminate wrong answers

Option B is wrong because an App permissions policy governs the permissions granted to third-party apps (e.g., OAuth apps) and does not monitor real-time user activities like file downloads. Option C is wrong because a Session policy controls user sessions in real time (e.g., blocking downloads or requiring authentication) but is not designed for threshold-based alerting on cumulative activities over a time window. Option D is wrong because an Anomaly detection policy uses machine learning to detect deviations from a user's baseline behavior, not a fixed threshold like 10 downloads in 5 minutes, and would not trigger on a simple count-based rule.

739
MCQhard

Your company uses Microsoft Defender XDR. A critical server is exhibiting signs of a potential ransomware attack, with files being encrypted and a ransom note appearing. The incident has been escalated to the security operations center (SOC). What is the most immediate action to contain the threat and prevent further spread?

A.Collect an investigation package for analysis
B.Disable the user account that was logged on
C.Initiate the 'Contain device' action from Microsoft Defender XDR
D.Run a full antivirus scan on the server
AnswerC

Contain device isolates the server from the network via Microsoft Defender XDR while preserving the live session for investigation, immediately halting encryption and lateral spread. This satisfies the stem's requirement for the most immediate containment action against active ransomware.

Why this answer

Initiate the 'Contain device' action from Microsoft Defender XDR. This action immediately isolates the compromised device from the network, preventing the ransomware from spreading to other systems. Option A is incorrect because collecting an investigation package is for forensic analysis, not containment.

Option B is incorrect because disabling the user account does not stop the ransomware process that is already running on the server. Option D is incorrect because running a full antivirus scan takes time and does not contain the threat; containment must happen first.

740
MCQeasy

A company manages multiple Azure subscriptions under a single management group. The security team wants to enable Microsoft Defender for Cloud's enhanced security features (e.g., Defender for Servers) for all subscriptions under that management group with minimal administrative effort. Which method should they use?

A.Enable the plans individually on each subscription
B.Enable the plans at the management group level
C.Use Azure Blueprints to assign the plans to each subscription
D.Create a custom Azure Policy that enforces the installation of the Log Analytics agent
AnswerB

Enabling plans at the management group level applies Defender for Servers across every subscription beneath it through inheritance, satisfying the minimal-effort constraint. Individual subscription enablement would require repeated configuration per subscription, and Microsoft Entra ID plays no role in Defender plan scoping.

Why this answer

Enabling Microsoft Defender for Cloud's enhanced security features at the management group level applies the plans to all current and future subscriptions under that management group with a single action, minimizing administrative effort. This is the most efficient method because Defender for Cloud supports inheritance of security policies and plans from the management group down to subscriptions, eliminating the need for per-subscription configuration.

Exam trap

The trap here is that candidates may think Azure Blueprints or custom policies are required for bulk enablement, but Defender for Cloud natively supports enabling plans at the management group level, which is the simplest and most direct method.

How to eliminate wrong answers

Option A is wrong because enabling plans individually on each subscription requires repeated manual effort and does not scale, failing the 'minimal administrative effort' requirement. Option C is wrong because Azure Blueprints are used for deploying consistent resource configurations (e.g., ARM templates, policies, role assignments) but cannot directly enable Defender for Cloud plans; they would require a custom policy or initiative to achieve this, which is more complex than enabling at the management group. Option D is wrong because creating a custom Azure Policy to enforce the Log Analytics agent installation does not enable Defender for Cloud's enhanced security features (e.g., Defender for Servers); it only ensures agent deployment, which is a prerequisite but not the same as enabling the security plan.

741
Multi-Selectmedium

Which TWO actions should an analyst take when a user reports receiving a suspicious email with an attachment? (Select TWO.)

Select 2 answers
A.Submit the email to Microsoft for analysis using the Submissions page in Microsoft 365 Defender.
B.Run a PowerShell script to automatically forward the email to IT.
C.Delete the email from the user's mailbox using Microsoft 365 Defender.
D.Open the attachment to verify if it is malicious.
E.Block the sender in the user's Outlook settings.
AnswersA, C

Submitting the suspicious email via the Submissions page sends the original message and attachments to Microsoft for detonation and signature analysis, satisfying the need to report and analyse the threat. This enables Microsoft to tune detection and block similar messages across the tenant.

Why this answer

Option A is correct because submitting the suspicious email via the Submissions page in Microsoft 365 Defender sends the message, including its attachment, to Microsoft for analysis, allowing the service to detonate and inspect it and then update its threat intelligence and filtering. Option C is correct because an analyst can use Microsoft 365 Defender (for example, via Threat Explorer or the Email entity page) to soft-delete or hard-delete the malicious message from the user's mailbox, removing the threat and preventing further user interaction. Option B is wrong because automatically forwarding a potentially malicious email with a live attachment to IT spreads the threat and is not a standard containment action.

Option D is wrong because opening the attachment could execute malicious code and compromise the analyst's workstation. Option E is wrong because blocking the sender only in the user's Outlook settings is a weak, local action that does not remove the message or protect the organization, and sender addresses are easily spoofed.

Exam trap

SC-200 often tests the correct incident response actions for suspicious emails. The trap is choosing actions that are either dangerous (opening attachment) or ineffective (blocking sender locally) instead of the proper submission and deletion procedures.

742
MCQmedium

You are a security operations analyst for a company that uses Microsoft Sentinel. The SOC manager wants to reduce alert fatigue by automatically closing incidents that are known false positives. The incidents are created from a custom analytics rule that generates a specific alert name, 'Suspicious PowerShell Download'. You need to create an automation rule that automatically closes these incidents with a classification of 'BenignPositive'. What should you do?

A.Use a workbook to monitor incidents with that alert name and manually close them in bulk.
B.Modify the analytics rule to set the incident severity to 'Informational' and enable automatic closure after 24 hours.
C.Create an automation rule with the condition 'Alert name' contains 'Suspicious PowerShell Download', and set the action to 'Close incident' with classification 'BenignPositive'.
D.Create a playbook that uses the 'Close incident' action and attach it to the analytics rule that generates the alert.
AnswerC

Automation rules in Microsoft Sentinel can trigger on incident creation and evaluate conditions such as alert name. Setting the action to close the incident with a specific classification directly addresses the requirement to auto-close known false positives. This reduces manual effort and ensures consistent handling of these incidents, aligning with the SOC manager's goal.

Why this answer

Automation rules in Microsoft Sentinel are designed to automate incident handling tasks such as assignment, status changes, and classification. By creating an automation rule that triggers on incident creation and uses a condition based on the alert name, you can automatically close incidents with the desired classification. This is the most efficient and native method to achieve the SOC manager's objective.

Exam trap

The trap here is assuming that playbooks are required for incident closure, but automation rules can directly close incidents without a playbook.

743
Multi-Selecthard

Which TWO of the following are key indicators of a potential DCSync attack that a threat hunter should look for in Microsoft Sentinel? (Select two.)

Select 2 answers
A.Failed logon attempts from a single IP
B.A new user account created with domain admin privileges
C.Event ID 4662 with access mask for DS-Replication-Get-Changes
D.Multiple Kerberos ticket requests from a single user
E.Directory replication requests from non-domain controller accounts
AnswersC, E

Event ID 4662 with the DS-Replication-Get-Changes access mask directly satisfies the stem's replication-permission indicator: DCSync abuses directory replication rights to harvest credential hashes. Monitoring this in Microsoft Sentinel detects non-domain-controller accounts requesting replication, the defining anomaly of DCSync activity.

Why this answer

Option C is correct because DCSync abuse is detected through Windows Security Event ID 4662, which records access to Active Directory objects; the telltale sign is an access mask containing the DS-Replication-Get-Changes (and often DS-Replication-Get-Changes-All) control access right on the domain object, indicating replication data was requested. Option E is correct because legitimate directory replication is performed only by domain controllers, so replication requests (the same 4662/DS-Replication rights, or DRSUAPI replication traffic) originating from non-domain-controller accounts or workstations strongly indicate a DCSync attack using tools like Mimikatz or Impacket's secretsdump. Option A does not belong because failed logons from one IP indicate brute-force or password-spray activity, not replication abuse.

Option B does not belong because creating a domain-admin account is a persistence or privilege-escalation action, not the replication-rights access pattern characteristic of DCSync. Option D does not belong because multiple Kerberos ticket requests suggest Kerberoasting or ticket harvesting, which is unrelated to the DS-Replication-Get-Changes access that defines DCSync.

744
MCQhard

A security analyst is investigating a sophisticated attack chain that started with a user clicking a link in a phishing email, which led to a drive-by download from a malicious website. The analyst wants to see the full list of URLs visited from the user's browser on the device. Which Advanced Hunting table contains this information?

A.DeviceEvents
B.DeviceNetworkEvents
C.DeviceProcessEvents
D.DeviceFileEvents
AnswerA

DeviceEvents is the correct choice because the Advanced Hunting schema includes browser telemetry events such as UrlClicked, which explicitly record the full URL visited by the user. This table aggregates security-relevant events from Microsoft Defender for Endpoint components, including SmartScreen, and preserves the complete URL with its path and query string. For an investigation into a sophisticated attack that likely started with a user navigating to a malicious link, DeviceEvents provides the direct evidence of the exact visited resource, making it the most precise and source-of-truth table for URL-level browsing activity.

Why this answer

DeviceEvents in Microsoft Defender XDR captures browser-based activities, including URL visits, via the 'ActionType' field (e.g., 'BrowserUrlClicked' or 'BrowserUrlNavigation'). This table is specifically designed to log web navigation events from browsers like Microsoft Edge or Chrome, making it the correct source for the full list of URLs visited during the phishing attack chain.

Exam trap

The trap here is that candidates often confuse DeviceNetworkEvents (which shows network connections) with browser URL tracking, but DeviceNetworkEvents lacks the URL-level detail needed for web navigation analysis, while DeviceEvents is the dedicated table for browser activity.

How to eliminate wrong answers

Option B (DeviceNetworkEvents) is wrong because it logs network-level connections (IP addresses, ports, protocols) but does not capture the full URL path or browser navigation context; it focuses on raw network flows, not HTTP/HTTPS URL details. Option C (DeviceProcessEvents) is wrong because it records process creation and termination events (e.g., executable launches, command lines) but does not include browser URL navigation data; it would show the browser process starting but not the specific URLs visited. Option D (DeviceFileEvents) is wrong because it tracks file creation, modification, and deletion events on the filesystem, which is irrelevant to browser URL history; it would capture downloaded files but not the URLs that led to them.

745
MCQhard

A SOC analyst needs to create an automated response in Microsoft Sentinel that, when a specific type of incident is created, automatically creates a ticket in ServiceNow and blocks the source IP address in Azure Firewall. The analyst already has a playbook that performs these actions. What is the correct configuration to trigger this playbook?

A.Attach the playbook to an automation rule that includes the condition for the target incident type.
B.Configure the playbook to run on a scheduled recurrence every 5 minutes.
C.Add the playbook to the incident's comments as a quick link.
D.Use a separate Power Automate flow with a trigger that watches for new Sentinel incidents.
AnswerA

Automation rules are the native, event-driven mechanism in Microsoft Sentinel that invoke playbooks automatically when an incident is created or updated. By including a condition for the specific incident type, the rule triggers the playbook immediately upon a match, enabling real-time response without analyst intervention. This is the recommended and supported method for automated incident response in Sentinel.

Why this answer

Automation rules in Microsoft Sentinel are the correct mechanism to trigger a playbook automatically when an incident is created. By attaching the playbook to an automation rule with a condition that matches the specific incident type (e.g., based on incident title or tag), the rule executes the playbook immediately upon incident creation, fulfilling the requirement without manual intervention.

Exam trap

The trap here is that candidates may confuse automation rules (which trigger on incident lifecycle events) with scheduled playbooks or external flows, overlooking that automation rules are the native, event-driven mechanism for incident-triggered automation in Sentinel.

How to eliminate wrong answers

Option B is wrong because configuring the playbook on a scheduled recurrence every 5 minutes would run it periodically regardless of incident creation, leading to unnecessary executions and failing to trigger specifically on new incidents. Option C is wrong because adding the playbook as a quick link in incident comments only provides a manual clickable action for analysts, not an automated trigger. Option D is wrong because while a separate Power Automate flow can watch for new Sentinel incidents via the connector, it is an indirect, less integrated approach compared to using native automation rules, which are the designed and recommended method for automated incident-triggered playbook execution.

746
MCQhard

Your organization uses Microsoft Defender for Cloud Apps to monitor SaaS application usage. You need to generate an alert when a user performs more than 50 failed login attempts in 10 minutes, and the alert must be based on a built-in anomaly detection policy. What should you do?

A.Create a data loss prevention (DLP) policy in Microsoft Purview that triggers on failed logins.
B.Deploy a session policy in Defender for Cloud Apps that blocks after 50 failed logins.
C.Configure an app connector for each SaaS app and then create a custom activity policy.
D.Enable the 'Multiple failed login attempts' anomaly detection policy in Defender for Cloud Apps.
AnswerD

The 'Multiple failed login attempts' policy is a built-in anomaly detection policy in Defender for Cloud Apps that uses machine learning/UEBA to establish a per-user or per-tenant baseline and then flags abnormal spikes in failed sign-ins. Enabling this template automatically generates alerts when the anomaly is detected, and you can tune sensitivity and notification recipients. This is the correct, native way to meet the requirement without building custom activity rules or DLP policies.

Why this answer

Microsoft Defender for Cloud Apps includes a built-in anomaly detection policy named 'Multiple failed login attempts' that specifically monitors for a high volume of failed logins from a single user within a short time window. This policy is enabled by default and can be customized to trigger alerts when the threshold (e.g., more than 50 failed attempts in 10 minutes) is exceeded, without requiring any additional configuration or custom policy creation.

Exam trap

The trap here is that candidates often confuse the purpose of session policies (which control real-time access) with anomaly detection policies (which detect behavioral patterns), leading them to incorrectly select Option B, or they assume a custom policy is always required (Option C) when a built-in policy already exists for this exact scenario.

How to eliminate wrong answers

Option A is wrong because data loss prevention (DLP) policies in Microsoft Purview are designed to detect and protect sensitive information (e.g., credit card numbers, PII) in content, not to monitor or alert on failed login attempts. Option B is wrong because session policies in Defender for Cloud Apps control real-time access and actions during a user session (e.g., blocking downloads), but they cannot be used to block after a specific number of failed logins; that logic belongs to anomaly detection policies. Option C is wrong because while app connectors are required to collect activity logs from SaaS apps, creating a custom activity policy would require manual definition of the detection logic; the question explicitly asks for a built-in anomaly detection policy, making a custom policy unnecessary and incorrect.

747
MCQeasy

You are a SOC analyst in Microsoft Defender XDR. An incident has been created that includes alerts from Microsoft Defender for Endpoint and Microsoft Defender for Office 365. You need to assign the incident to a colleague and add a note about initial findings. What should you do?

A.Export the incident to a CSV file and email it to your colleague, then close the incident.
B.Open the incident, use the 'Assign to' option to select your colleague, and add a comment in the incident's activity log.
C.Use the 'Manage incident' option to change the status to 'In progress' and set the 'Assigned to' field to your colleague's email address.
D.Create a new incident manually and copy the alerts from the original incident, then assign the new incident to your colleague.
AnswerB

In Microsoft Defender XDR, you can assign an incident to a specific user directly from the incident page, and you can add comments to the incident timeline. This action notifies the assignee and records your findings for collaboration. It is the standard way to hand off an incident while preserving context.

Why this answer

Microsoft Defender XDR provides built-in incident assignment and commenting. Assigning the incident to a colleague from the incident page ensures they are notified and can take ownership. Adding a comment in the activity log documents initial findings without altering the incident's alert correlation.

This maintains a clear audit trail and supports efficient collaboration.

Exam trap

The trap here is assuming you must export or recreate the incident to share it, rather than using the native assignment and commenting features.

748
MCQmedium

Refer to the exhibit. You are reviewing an Azure Security Center automation (now Microsoft Defender for Cloud) that should automatically trigger a Logic App when an alert is generated. However, the automation is not triggering. What is the most likely cause?

A.The action type is incorrect; it should be 'EventHub'
B.The logicAppResourceId is missing
C.The apiVersion is invalid
D.The automation is missing the 'triggers' property to filter on specific alert types
AnswerD

The automation is missing the `triggers` property, which is mandatory in Microsoft.Security/automations to filter on specific alert types or other conditions. Without a trigger, the automation has no event criteria to evaluate, so it will never fire the Logic App. The `triggers` property defines which alerts, severities, or states activate the action, making it essential for the rule to function.

Why this answer

Microsoft Defender for Cloud automation requires a 'triggers' property to define which alert types should invoke the Logic App. Without this property, the automation is created but never fires, as it has no conditions to match incoming alerts. The exhibit shows the automation resource is configured, but missing the triggers array means no alerts will trigger the Logic App.

Exam trap

The trap here is that candidates assume the automation will trigger on all alerts by default, but Microsoft Defender for Cloud requires explicit trigger conditions; otherwise, the automation exists but never fires.

How to eliminate wrong answers

Option A is wrong because the action type 'LogicApp' is correct for invoking a Logic App; 'EventHub' would be used to send alerts to an event hub, not to trigger a Logic App. Option B is wrong because the logicAppResourceId is present in the exhibit (it is a required property and shown in the JSON), so its absence is not the issue. Option C is wrong because the apiVersion '2019-01-01-preview' is a valid and supported version for Microsoft Defender for Cloud automation resources; an invalid apiVersion would cause a deployment error, not a silent failure to trigger.

749
MCQmedium

You are investigating a potential data exfiltration using Microsoft Defender for Cloud Apps. You find that a user downloaded a large number of files from SharePoint Online to a personal device. Which anomaly detection policy type would have detected this?

A.Activity anomaly detection policy
B.File anomaly detection policy
C.Cloud Discovery anomaly detection policy
D.OAuth app anomaly detection policy
AnswerA

Activity anomaly detection policies in Microsoft Defender for Cloud Apps baseline each user's typical file download volume and alert when behaviour deviates sharply. A mass SharePoint Online download to a personal device exceeds that learned baseline, matching the exfiltration scenario precisely.

Why this answer

Activity anomaly detection policies detect unusual download volumes. Option B is wrong because File anomaly policies focus on file types and metadata. Option C is wrong because Cloud Discovery anomaly policies focus on shadow IT.

Option D is wrong because OAuth app anomaly policies focus on app permissions.

750
MCQhard

An organization uses Microsoft Purview Communication Compliance to detect insider trading. An alert is generated for a user who sent a message containing sensitive financial data. The compliance officer needs to initiate a legal hold on the user's mailbox to preserve evidence. Which role must the officer have to perform this action?

A.Communication Compliance admin
B.Compliance Administrator (Global)
C.eDiscovery Manager (Legal Hold)
D.Exchange Online Mailbox Search role
AnswerC

The eDiscovery Manager role group has a sub-role for Legal Hold that specifically allows managing holds on mailboxes and sites. This is the required identity to place a mailbox on hold in the Microsoft Purview compliance portal. Without this sub-role, even other eDiscovery roles cannot place holds.

Why this answer

Legal hold requires the 'Legal Hold' role in Microsoft Purview (eDiscovery). Communication Compliance roles alone do not include hold capabilities. Exchange Online roles may not have cross-functional hold.

Page 9

Page 10 of 18

Page 11