100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 20
Defender XDR automated investigation has evaluated a malicious file, and policy requires review before remediation on a sensitive server group. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Audit device group membership and approvals after server onboarding or SOC role changes.
- Monitor Logic Apps run history and rotate expired connector credentials proactively.
- Monitor hit rates and tune the query when legitimate administration command lines change.
- Recheck playbook resource-group access after moving playbooks or changing resource ownership.
Explanation
Correct Answer
A:A misplaced server can receive unintended automated remediation.
Incorrect Answers
B:Automation can silently stop when integrations lose authorization. It does not establish governing automated remediation on sensitive servers, which is the specific issue in this case.
C:New tooling can increase false positives and hide high-value events. The scenario calls for governing automated remediation on sensitive servers, not that separate action.
D:Moved or newly scoped Logic Apps can break automation authorization. That addresses granting Sentinel permission to run a playbook, not the stated need for governing automated remediation on sensitive servers.
Question 21
An active ransomware incident shows correlated compromised accounts and devices that should be contained rapidly by Microsoft Defender XDR. What should the administrator configure to address this exact situation?
- Use Defender for Endpoint device group automation levels with approval for remediation where required.
- Create a Microsoft Sentinel automation rule that assigns incidents matching explicit conditions.
- Use Microsoft Defender XDR automatic attack disruption with the applicable protection prerequisites.
- Enable the supported custom data collection capability for the required Defender for Endpoint evidence.
Explanation
Correct Answer
C:Automatic disruption coordinates supported containment across correlated attack entities.
Incorrect Answers
A:Device groups can separate fully automated response from actions that require approval. It does not establish using automatic attack disruption for a correlated attack, which is the specific issue in this case.
B:Automation rules can perform incident management actions without an external workflow. The scenario calls for using automatic attack disruption for a correlated attack, not that separate action.
D:Custom collection must match available device and sensor capabilities. That is relevant to configuring targeted endpoint telemetry collection, whereas this requirement concerns using automatic attack disruption for a correlated attack.
Question 22
An active ransomware incident shows correlated compromised accounts and devices that should be contained rapidly by Microsoft Defender XDR. The team has selected: Use Microsoft Defender XDR automatic attack disruption with the applicable protection prerequisites. Which operational step implements the chosen approach?
- Set incident-created conditions, ordering and assignment action in a Sentinel automation rule.
- Confirm the required Defender components, supported licensing and device or identity coverage before relying on disruption.
- Place sensitive servers in a scoped group with the chosen automation level and appropriate permissions.
- Build a Logic Apps playbook with supported Sentinel incident trigger and authorized ITSM or Teams actions.
Explanation
Correct Answer
B:Incomplete prerequisites prevent automated cross-domain response.
Incorrect Answers
A:The rule maps eligible incidents to the correct owner consistently. The scenario calls for using automatic attack disruption for a correlated attack, not that separate action.
C:A controlled level determines whether proposed remediation waits for a responder. That is relevant to governing automated remediation on sensitive servers, whereas this requirement concerns using automatic attack disruption for a correlated attack.
D:Connected actions require the correct identity permissions and trigger schema. It does not establish using automatic attack disruption for a correlated attack, which is the specific issue in this case.
Question 23
An active ransomware incident shows correlated compromised accounts and devices that should be contained rapidly by Microsoft Defender XDR. The team implements: Use Microsoft Defender XDR automatic attack disruption with the applicable protection prerequisites. What outcome would best validate the implementation?
- Inspect the incident action history for supported automatic containment of the affected device or identity.
- Run the playbook on a test incident and confirm one ticket and one correctly populated notification.
- Test the query with known sample events and confirm its generated custom detection alert.
- Run a matching incident rule and verify the playbook starts successfully in Logic Apps history.
Explanation
Correct Answer
A:Evidence should show an actual automated action, not simply an alert.
Incorrect Answers
B:End-to-end tests catch connector failures and repeated actions. That is relevant to orchestrating cross-system Sentinel incident actions, whereas this requirement concerns using automatic attack disruption for a correlated attack.
C:A result in a hunting query alone does not establish the alert rule works. It does not establish using automatic attack disruption for a correlated attack, which is the specific issue in this case.
D:A triggered run establishes that both automation and permissions work. The scenario calls for using automatic attack disruption for a correlated attack, not that separate action.
Question 24
An active ransomware incident shows correlated compromised accounts and devices that should be contained rapidly by Microsoft Defender XDR. The setting is now in production. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review disruption coverage whenever identity connectors or endpoint onboarding change.
- Monitor collection health and storage overhead after sensor and operating-system updates.
- Review rule conditions after analytics rule renames and incident routing changes.
- Audit device group membership and approvals after server onboarding or SOC role changes.
Explanation
Correct Answer
A:Missing identities or sensors can leave gaps in disruption reach.
Incorrect Answers
B:Collection gaps or excessive volume can make investigations unreliable. It does not establish using automatic attack disruption for a correlated attack, which is the specific issue in this case.
C:Changed metadata can cause otherwise valid incidents to miss automation. The scenario calls for using automatic attack disruption for a correlated attack, not that separate action.
D:A misplaced server can receive unintended automated remediation. That addresses governing automated remediation on sensitive servers, not the stated need for using automatic attack disruption for a correlated attack.
Question 25
A SOC wants Sentinel incidents assigned to the right analyst group immediately based on analytics rule name and severity. What should the administrator configure to address this exact situation?
- Use a Microsoft Sentinel playbook backed by Azure Logic Apps for multi-service orchestration.
- Authorize Microsoft Sentinel automation to invoke the playbook in its relevant Logic Apps resource group.
- Create a Defender XDR custom detection rule from a validated Advanced Hunting query.
- Create a Microsoft Sentinel automation rule that assigns incidents matching explicit conditions.
Explanation
Correct Answer
D:Automation rules can perform incident management actions without an external workflow.
Incorrect Answers
A:Playbooks provide conditional connectors and external workflow actions beyond basic automation rules. It does not establish automatically assigning Sentinel incidents, which is the specific issue in this case.
B:Playbooks are separate resources and their execution needs explicit permissions. The scenario calls for automatically assigning Sentinel incidents, not that separate action.
C:Custom detections promote compatible hunting logic into repeatable alert generation. That addresses creating a Defender XDR custom detection, not the stated need for automatically assigning Sentinel incidents.
Question 26
A SOC wants Sentinel incidents assigned to the right analyst group immediately based on analytics rule name and severity. The project chooses: Create a Microsoft Sentinel automation rule that assigns incidents matching explicit conditions. Which operational step implements the chosen approach?
- Pilot the rule, inspect audit events and then enforce Block on eligible device groups.
- Set incident-created conditions, ordering and assignment action in a Sentinel automation rule.
- Confirm the required Defender components, supported licensing and device or identity coverage before relying on disruption.
- Build a Logic Apps playbook with supported Sentinel incident trigger and authorized ITSM or Teams actions.
Explanation
Correct Answer
B:The rule maps eligible incidents to the correct owner consistently.
Incorrect Answers
A:Staged enforcement reduces interference with legitimate macros and integrations. The scenario calls for automatically assigning Sentinel incidents, not that separate action.
C:Incomplete prerequisites prevent automated cross-domain response. That is relevant to using automatic attack disruption for a correlated attack, whereas this requirement concerns automatically assigning Sentinel incidents.
D:Connected actions require the correct identity permissions and trigger schema. It does not establish automatically assigning Sentinel incidents, which is the specific issue in this case.
Question 27
A SOC wants Sentinel incidents assigned to the right analyst group immediately based on analytics rule name and severity. The intended configuration is: Create a Microsoft Sentinel automation rule that assigns incidents matching explicit conditions. What outcome would best validate the implementation?
- Trigger a controlled high-severity test incident and confirm only the intended mailbox receives an email.
- Inspect ASR audit events and validate expected scripts before switching eligible devices to Block.
- Create a sample matching incident and verify its owner is set while unrelated incidents are unchanged.
- Replay known benign and malicious samples and confirm only the authorized activity is suppressed.
Explanation
Correct Answer
C:Comparison detects incorrect rule filters or ordering.
Incorrect Answers
A:A delivery test validates both event selection and notification recipients. That addresses routing high-severity XDR incident emails, not the stated need for automatically assigning Sentinel incidents.
B:Audit telemetry shows whether legitimate business workflows are affected. That is relevant to piloting endpoint attack surface reduction rules, whereas this requirement concerns automatically assigning Sentinel incidents.
D:Both negative and positive controls reveal overbroad alert tuning. The scenario calls for automatically assigning Sentinel incidents, not that separate action.
Question 28
A SOC wants Sentinel incidents assigned to the right analyst group immediately based on analytics rule name and severity. After rollout, the organization wants continuing assurance. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review rule conditions after analytics rule renames and incident routing changes.
- Reevaluate ASR exclusions after applications or managed device membership change.
- Review suppression rule matches when script versions or administrator device scopes change.
- Review notification recipients and rules after on-call rotations or alert taxonomy changes.
Explanation
Correct Answer
A:Changed metadata can cause otherwise valid incidents to miss automation.
Incorrect Answers
B:Outdated exclusions can weaken protection or disrupt software upgrades. It does not establish automatically assigning Sentinel incidents, which is the specific issue in this case.
C:A stale exception can unintentionally hide malicious activity. The scenario calls for automatically assigning Sentinel incidents, not that separate action.
D:Stale addresses can silently remove the response team from the notification path. That addresses routing high-severity XDR incident emails, not the stated need for automatically assigning Sentinel incidents.
Question 29
A complex Sentinel incident workflow must create a ServiceNow ticket and notify a Teams channel with incident entities. What should the administrator configure to address this exact situation?
- Create a Defender XDR custom detection rule from a validated Advanced Hunting query.
- Tune the relevant Defender XDR detection or alert suppression configuration narrowly to the approved activity.
- Use a Microsoft Sentinel playbook backed by Azure Logic Apps for multi-service orchestration.
- Create a Microsoft Sentinel automation rule that assigns incidents matching explicit conditions.
Explanation
Correct Answer
C:Playbooks provide conditional connectors and external workflow actions beyond basic automation rules.
Incorrect Answers
A:Custom detections promote compatible hunting logic into repeatable alert generation. It does not establish orchestrating cross-system Sentinel incident actions, which is the specific issue in this case.
B:A bounded suppression prevents repeated known noise without silencing other malicious behavior. The scenario calls for orchestrating cross-system Sentinel incident actions, not that separate action.
D:Automation rules can perform incident management actions without an external workflow. That is relevant to automatically assigning Sentinel incidents, whereas this requirement concerns orchestrating cross-system Sentinel incident actions.
Question 30
A complex Sentinel incident workflow must create a ServiceNow ticket and notify a Teams channel with incident entities. The proposed configuration is: Use a Microsoft Sentinel playbook backed by Azure Logic Apps for multi-service orchestration. Which operational step implements the chosen approach?
- Target the pilot group through the endpoint security policy and select Audit for the specific ASR rule.
- Constrain the rule to the verified script indicators or device scope rather than suppressing the entire alert type.
- Build a Logic Apps playbook with supported Sentinel incident trigger and authorized ITSM or Teams actions.
- Pilot the rule, inspect audit events and then enforce Block on eligible device groups.
Explanation
Correct Answer
C:Connected actions require the correct identity permissions and trigger schema.
Incorrect Answers
A:Scoped audit collects decision evidence with less disruption than immediate block everywhere. The scenario calls for orchestrating cross-system Sentinel incident actions, not that separate action.
B:Specific context distinguishes an approved runbook from later abuse of the same alert family. That addresses reducing known benign XDR alert noise, not the stated need for orchestrating cross-system Sentinel incident actions.
D:Staged enforcement reduces interference with legitimate macros and integrations. It does not establish orchestrating cross-system Sentinel incident actions, which is the specific issue in this case.
Microsoft Security Operations Analyst (SC-200) Practice Tests