Microsoft SC-200 Practice Test 69
Question 680
Defender XDR automatically disrupts an attack by containing a compromised host. After the initial control is implemented, forensics prove the machine is clean and ready for restoration. What is the best follow-up action?
- Use the documented release or recovery workflow with monitoring
- Each device appears once with its verified newest timestamp
- Release the compromised machine simply because the alert count fell
- Investigate the automatic disruption action and verify containment state and prerequisites
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: Forensics prove the machine is clean and ready for restoration. Therefore Use the documented release or recovery workflow with monitoring is appropriate for Defender XDR automatically disrupts an attack by containing a compromised host, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is Forensics prove the machine is clean and ready for restoration, so the proper follow-up must address it rather than merely note Each device appears once with its verified newest timestamp.
C:This was already unsuitable under the original condition because reduced alerts do not establish that the infection was eradicated. It also fails after the change affecting Defender XDR automatically disrupts an attack by containing a compromised host.
D:This was the original control already implemented: Investigate the automatic disruption action and verify containment state and prerequisites. Its original rationale was: High-confidence attack disruption records show affected entity and the protective action performed. For the initial setting (Defender XDR automatically disrupts an attack by containing a compromised host), that does not itself meet the new condition: Forensics prove the machine is clean and ready for restoration.
Question 681
An endpoint response team receives evidence of attack disruption on a machine during ransomware response. Which action BEST addresses this Microsoft security operations requirement?
- Use the documented release or recovery workflow with monitoring
- Investigate the automatic disruption action and verify containment state and prerequisites
- Use a supported cross-workspace KQL query with explicit workspace scope and permission checks
- Release the compromised machine simply because the alert count fell
Explanation
Correct Answer
B:High-confidence attack disruption records show affected entity and the protective action performed. The selected action is: Investigate the automatic disruption action and verify containment state and prerequisites.
Incorrect Answers
A:This action would become suitable if a later condition arose: Forensics prove the machine is clean and ready for restoration. It is not the immediate answer to An endpoint response team receives evidence of attack disruption on a machine during ransomware response.
C:That action serves a separate case (A regional SOC investigates linked activity from two authorized subsidiaries) in the Perform threat hunting domain. It does not specifically address the initial case.
D:Reduced alerts do not establish that the infection was eradicated. The shortcut Release the compromised machine simply because the alert count fell does not resolve the case involving An endpoint response team receives evidence of attack disruption on a machine during ransomware response.
Question 682
An endpoint response team receives evidence of attack disruption on a machine during ransomware response. A colleague suggests: Release the compromised machine simply because the alert count fell. What is the MOST important technical defect in this suggestion?
- A familiar product name alone establishes that the proposal is safe.
- Credential copying is unnecessary and risks unauthorized access
- High-confidence attack disruption records show affected entity and the protective action performed
- Reduced alerts do not establish that the infection was eradicated
Explanation
Correct Answer
D:Reduced alerts do not establish that the infection was eradicated. This directly explains the defect in Release the compromised machine simply because the alert count fell for An endpoint response team receives evidence of attack disruption on a machine during ransomware response.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For An endpoint response team receives evidence of attack disruption on a machine during ransomware response, the actual issue is that reduced alerts do not establish that the infection was eradicated.
B:That concern applies to another security scenario (A regional SOC investigates linked activity from two authorized subsidiaries). Here, An endpoint response team receives evidence of attack disruption on a machine during ransomware response, the specified proposal fails because reduced alerts do not establish that the infection was eradicated.
C:This describes the reason for the preferred control, Investigate the automatic disruption action and verify containment state and prerequisites: High-confidence attack disruption records show affected entity and the protective action performed. It is not the direct defect in the proposed shortcut for An endpoint response team receives evidence of attack disruption on a machine during ransomware response.
Question 683
An endpoint response team receives evidence of attack disruption on a machine during ransomware response. After implementing Investigate the automatic disruption action and verify containment state and prerequisites, what result would BEST establish that it worked?
- The team schedules a future check of whether the action audit records containment and follow-up evidence confirms risk reduction, without recording any observed result.
- The SOC approves Investigate the automatic disruption action and verify containment state and prerequisites on paper but has not tested its operation.
- The result includes expected records from each authorized workspace
- The action audit records containment and follow-up evidence confirms risk reduction
Explanation
Correct Answer
D:Correct observed evidence. The action audit records containment and follow-up evidence confirms risk reduction. Given the original requirement, that result would substantiate the selected action, Investigate the automatic disruption action and verify containment state and prerequisites.
Incorrect Answers
A:A future validation plan is not an observed result. The actual verification should establish that the action audit records containment and follow-up evidence confirms risk reduction, in the scenario involving An endpoint response team receives evidence of attack disruption on a machine during ransomware response.
B:Approval records intent but not actual protection or investigation. For An endpoint response team receives evidence of attack disruption on a machine during ransomware response, an operational outcome must demonstrate that the action audit records containment and follow-up evidence confirms risk reduction.
C:This observation fits another setting (A regional SOC investigates linked activity from two authorized subsidiaries). It does not verify Investigate the automatic disruption action and verify containment state and prerequisites against the original need.
Question 684
An endpoint response team receives evidence of attack disruption on a machine during ransomware response. The original measure is in place. A new requirement arises: Forensics prove the machine is clean and ready for restoration. Which ADDITIONAL action BEST fits?
- Release the compromised machine simply because the alert count fell
- Use the documented release or recovery workflow with monitoring
- Investigate the automatic disruption action and verify containment state and prerequisites
- The action audit records containment and follow-up evidence confirms risk reduction
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: Forensics prove the machine is clean and ready for restoration. Therefore Use the documented release or recovery workflow with monitoring is appropriate for An endpoint response team receives evidence of attack disruption on a machine during ransomware response, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because reduced alerts do not establish that the infection was eradicated. It also fails after the change affecting An endpoint response team receives evidence of attack disruption on a machine during ransomware response.
C:This was the original control already implemented: Investigate the automatic disruption action and verify containment state and prerequisites. Its original rationale was: High-confidence attack disruption records show affected entity and the protective action performed. For the initial setting (An endpoint response team receives evidence of attack disruption on a machine during ransomware response), that does not itself meet the new condition: Forensics prove the machine is clean and ready for restoration.
D:An observation is not the additional configuration or response action requested. The change is Forensics prove the machine is clean and ready for restoration, so the proper follow-up must address it rather than merely note The action audit records containment and follow-up evidence confirms risk reduction.
Question 685
A security operations analyst must handle this situation: A suspicious PowerShell chain spawned from a user-facing document. What is the BEST initial response?
- Inspect DeviceProcessEvents with command-line and initiating process fields
- Correlate the process key and time with the network-event table
- Build an appropriate scheduled summary output or KQL job based on the needed detail and tier
- Query only DeviceNetworkEvents and assume it includes every process creation
Explanation
Correct Answer
A:Process-creation records support causal investigation of child and parent execution. The selected action is: Inspect DeviceProcessEvents with command-line and initiating process fields.
Incorrect Answers
B:This action would become suitable if a later condition arose: The process also downloaded a remote script. It is not the immediate answer to A suspicious PowerShell chain spawned from a user-facing document.
C:That action serves a separate case (A SOC wants to reduce investigation latency for commonly searched historical indicators) in the Perform threat hunting domain. It does not specifically address the initial case.
D:Network events and process-creation events contain different primary telemetry. The shortcut Query only DeviceNetworkEvents and assume it includes every process creation does not resolve the case involving A suspicious PowerShell chain spawned from a user-facing document.
Question 686
A suspicious PowerShell chain spawned from a user-facing document. Why should the SOC reject the proposed shortcut: Query only DeviceNetworkEvents and assume it includes every process creation?
- Network events and process-creation events contain different primary telemetry
- A familiar product name alone establishes that the proposal is safe.
- Process-creation records support causal investigation of child and parent execution
- Summaries may omit forensic detail and cannot replace required source retention
Explanation
Correct Answer
A:Network events and process-creation events contain different primary telemetry. This directly explains the defect in Query only DeviceNetworkEvents and assume it includes every process creation for A suspicious PowerShell chain spawned from a user-facing document.
Incorrect Answers
B:Product-name familiarity cannot validate a proposed security action. For A suspicious PowerShell chain spawned from a user-facing document, the actual issue is that network events and process-creation events contain different primary telemetry.
C:This describes the reason for the preferred control, Inspect DeviceProcessEvents with command-line and initiating process fields: Process-creation records support causal investigation of child and parent execution. It is not the direct defect in the proposed shortcut for A suspicious PowerShell chain spawned from a user-facing document.
D:That concern applies to another security scenario (A SOC wants to reduce investigation latency for commonly searched historical indicators). Here, A suspicious PowerShell chain spawned from a user-facing document, the specified proposal fails because network events and process-creation events contain different primary telemetry.
Question 687
A suspicious PowerShell chain spawned from a user-facing document. The SOC implements Inspect DeviceProcessEvents with command-line and initiating process fields. Which observed result provides credible confirmation?
- A sample report uses the summary output while underlying retained evidence remains available
- The SOC approves Inspect DeviceProcessEvents with command-line and initiating process fields on paper but has not tested its operation.
- The team schedules a future check of whether the matching process creation record exposes parent process and command line, without recording any observed result.
- The matching process creation record exposes parent process and command line
Explanation
Correct Answer
D:Correct observed evidence. The matching process creation record exposes parent process and command line. Given the original requirement, that result would substantiate the selected action, Inspect DeviceProcessEvents with command-line and initiating process fields.
Incorrect Answers
A:This observation fits another setting (A SOC wants to reduce investigation latency for commonly searched historical indicators). It does not verify Inspect DeviceProcessEvents with command-line and initiating process fields against the original need.
B:Approval records intent but not actual protection or investigation. For A suspicious PowerShell chain spawned from a user-facing document, an operational outcome must demonstrate that the matching process creation record exposes parent process and command line.
C:A future validation plan is not an observed result. The actual verification should establish that the matching process creation record exposes parent process and command line, in the scenario involving A suspicious PowerShell chain spawned from a user-facing document.
Question 688
The original problem was: A suspicious PowerShell chain spawned from a user-facing document. The solution is operating, but the process also downloaded a remote script. What should change next?
- Inspect DeviceProcessEvents with command-line and initiating process fields
- Query only DeviceNetworkEvents and assume it includes every process creation
- A sample report uses the summary output while underlying retained evidence remains available
- Correlate the process key and time with the network-event table
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: The process also downloaded a remote script. Therefore Correlate the process key and time with the network-event table is appropriate for A suspicious PowerShell chain spawned from a user-facing document, in addition to the previous measure.
Incorrect Answers
A:This was the original control already implemented: Inspect DeviceProcessEvents with command-line and initiating process fields. Its original rationale was: Process-creation records support causal investigation of child and parent execution. For the initial setting (A suspicious PowerShell chain spawned from a user-facing document), that does not itself meet the new condition: The process also downloaded a remote script.
B:This was already unsuitable under the original condition because network events and process-creation events contain different primary telemetry. It also fails after the change affecting A suspicious PowerShell chain spawned from a user-facing document.
C:An observation is not the additional configuration or response action requested. The change is The process also downloaded a remote script, so the proper follow-up must address it rather than merely note A sample report uses the summary output while underlying retained evidence remains available.
Question 689
An analyst wants process lineage and command-line context rather than malware name alone. Which configuration or investigation step is MOST appropriate?
- Use KQL summarize count by account and bin of the event timestamp
- Inspect DeviceProcessEvents with command-line and initiating process fields
- Query only DeviceNetworkEvents and assume it includes every process creation
- Correlate the process key and time with the network-event table
Explanation
Correct Answer
B:Process-creation records support causal investigation of child and parent execution. The selected action is: Inspect DeviceProcessEvents with command-line and initiating process fields.
Incorrect Answers
A:That action serves a separate case (An analyst needs counts of failed sign-ins per account over one-hour buckets) in the Perform threat hunting domain. It does not specifically address the initial case.
C:Network events and process-creation events contain different primary telemetry. The shortcut Query only DeviceNetworkEvents and assume it includes every process creation does not resolve the case involving An analyst wants process lineage and command-line context rather than malware name alone.
D:This action would become suitable if a later condition arose: The process also downloaded a remote script. It is not the immediate answer to An analyst wants process lineage and command-line context rather than malware name alone.
Question 690
An analyst wants process lineage and command-line context rather than malware name alone. Which statement BEST explains why the proposed approach (Query only DeviceNetworkEvents and assume it includes every process creation) fails?
- Network events and process-creation events contain different primary telemetry
- Sorting individual events does not compute grouped counts
- A familiar product name alone establishes that the proposal is safe.
- Process-creation records support causal investigation of child and parent execution
Explanation
Correct Answer
A:Network events and process-creation events contain different primary telemetry. This directly explains the defect in Query only DeviceNetworkEvents and assume it includes every process creation for An analyst wants process lineage and command-line context rather than malware name alone.
Incorrect Answers
B:That concern applies to another security scenario (An analyst needs counts of failed sign-ins per account over one-hour buckets). Here, An analyst wants process lineage and command-line context rather than malware name alone, the specified proposal fails because network events and process-creation events contain different primary telemetry.
C:Product-name familiarity cannot validate a proposed security action. For An analyst wants process lineage and command-line context rather than malware name alone, the actual issue is that network events and process-creation events contain different primary telemetry.
D:This describes the reason for the preferred control, Inspect DeviceProcessEvents with command-line and initiating process fields: Process-creation records support causal investigation of child and parent execution. It is not the direct defect in the proposed shortcut for An analyst wants process lineage and command-line context rather than malware name alone.