Microsoft SC-200 Practice Test 57
Question 560
A phishing alert and Endpoint malware alert share an indicator but not a timestamp. After the initial control is implemented, the shared IP is confirmed as a common public proxy. What is the best follow-up action?
- Assume shared IP address alone proves identical malicious actors
- Reduce confidence in IP-only matches and prioritize stronger entity evidence
- Results tie the file SHA1 or path to devices and event times
- Correlate evidence using entities, indicators and event times with appropriate tolerance
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: The shared IP is confirmed as a common public proxy. Therefore Reduce confidence in IP-only matches and prioritize stronger entity evidence is appropriate for A phishing alert and Endpoint malware alert share an indicator but not a timestamp, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because shared cloud or NAT addresses can yield unrelated activity. It also fails after the change affecting A phishing alert and Endpoint malware alert share an indicator but not a timestamp.
C:An observation is not the additional configuration or response action requested. The change is The shared IP is confirmed as a common public proxy, so the proper follow-up must address it rather than merely note Results tie the file SHA1 or path to devices and event times.
D:This was the original control already implemented: Correlate evidence using entities, indicators and event times with appropriate tolerance. Its original rationale was: Multiple supporting relationships help determine whether alerts belong to the same intrusion. For the initial setting (A phishing alert and Endpoint malware alert share an indicator but not a timestamp), that does not itself meet the new condition: The shared IP is confirmed as a common public proxy.
Question 561
A Defender incident spans cloud and on-prem signals across a prolonged campaign. Which action BEST addresses this Microsoft security operations requirement?
- Correlate evidence using entities, indicators and event times with appropriate tolerance
- Reduce confidence in IP-only matches and prioritize stronger entity evidence
- Assume shared IP address alone proves identical malicious actors
- Use parse_json and mv-expand with explicit type handling in KQL
Explanation
Correct Answer
A:Multiple supporting relationships help determine whether alerts belong to the same intrusion. The selected action is: Correlate evidence using entities, indicators and event times with appropriate tolerance.
Incorrect Answers
B:This action would become suitable if a later condition arose: The shared IP is confirmed as a common public proxy. It is not the immediate answer to A Defender incident spans cloud and on-prem signals across a prolonged campaign.
C:Shared cloud or NAT addresses can yield unrelated activity. The shortcut Assume shared IP address alone proves identical malicious actors does not resolve the case involving A Defender incident spans cloud and on-prem signals across a prolonged campaign.
D:That action serves a separate case (A hunter needs to inspect fields inside a JSON array stored in an event column) in the Perform threat hunting domain. It does not specifically address the initial case.
Question 562
A Defender incident spans cloud and on-prem signals across a prolonged campaign. A colleague suggests: Assume shared IP address alone proves identical malicious actors. What is the MOST important technical defect in this suggestion?
- Unparsed nested data cannot reliably expose each indicator value
- Shared cloud or NAT addresses can yield unrelated activity
- Multiple supporting relationships help determine whether alerts belong to the same intrusion
- A familiar product name alone establishes that the proposal is safe.
Explanation
Correct Answer
B:Shared cloud or NAT addresses can yield unrelated activity. This directly explains the defect in Assume shared IP address alone proves identical malicious actors for A Defender incident spans cloud and on-prem signals across a prolonged campaign.
Incorrect Answers
A:That concern applies to another security scenario (A hunter needs to inspect fields inside a JSON array stored in an event column). Here, A Defender incident spans cloud and on-prem signals across a prolonged campaign, the specified proposal fails because shared cloud or NAT addresses can yield unrelated activity.
C:This describes the reason for the preferred control, Correlate evidence using entities, indicators and event times with appropriate tolerance: Multiple supporting relationships help determine whether alerts belong to the same intrusion. It is not the direct defect in the proposed shortcut for A Defender incident spans cloud and on-prem signals across a prolonged campaign.
D:Product-name familiarity cannot validate a proposed security action. For A Defender incident spans cloud and on-prem signals across a prolonged campaign, the actual issue is that shared cloud or NAT addresses can yield unrelated activity.
Question 563
A Defender incident spans cloud and on-prem signals across a prolonged campaign. After implementing Correlate evidence using entities, indicators and event times with appropriate tolerance, what result would BEST establish that it worked?
- A test event expands into expected per-indicator rows and columns
- The investigator documents corroborating account or device ties before merging
- The team schedules a future check of whether the investigator documents corroborating account or device ties before merging, without recording any observed result.
- The SOC approves Correlate evidence using entities, indicators and event times with appropriate tolerance on paper but has not tested its operation.
Explanation
Correct Answer
B:Correct observed evidence. The investigator documents corroborating account or device ties before merging. Given the original requirement, that result would substantiate the selected action, Correlate evidence using entities, indicators and event times with appropriate tolerance.
Incorrect Answers
A:This observation fits another setting (A hunter needs to inspect fields inside a JSON array stored in an event column). It does not verify Correlate evidence using entities, indicators and event times with appropriate tolerance against the original need.
C:A future validation plan is not an observed result. The actual verification should establish that the investigator documents corroborating account or device ties before merging, in the scenario involving A Defender incident spans cloud and on-prem signals across a prolonged campaign.
D:Approval records intent but not actual protection or investigation. For A Defender incident spans cloud and on-prem signals across a prolonged campaign, an operational outcome must demonstrate that the investigator documents corroborating account or device ties before merging.
Question 564
A Defender incident spans cloud and on-prem signals across a prolonged campaign. The original measure is in place. A new requirement arises: The shared IP is confirmed as a common public proxy. Which ADDITIONAL action BEST fits?
- Assume shared IP address alone proves identical malicious actors
- The investigator documents corroborating account or device ties before merging
- Reduce confidence in IP-only matches and prioritize stronger entity evidence
- Correlate evidence using entities, indicators and event times with appropriate tolerance
Explanation
Correct Answer
C:Correct follow-up. The requirement changed to: The shared IP is confirmed as a common public proxy. Therefore Reduce confidence in IP-only matches and prioritize stronger entity evidence is appropriate for A Defender incident spans cloud and on-prem signals across a prolonged campaign, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because shared cloud or NAT addresses can yield unrelated activity. It also fails after the change affecting A Defender incident spans cloud and on-prem signals across a prolonged campaign.
B:An observation is not the additional configuration or response action requested. The change is The shared IP is confirmed as a common public proxy, so the proper follow-up must address it rather than merely note The investigator documents corroborating account or device ties before merging.
D:This was the original control already implemented: Correlate evidence using entities, indicators and event times with appropriate tolerance. Its original rationale was: Multiple supporting relationships help determine whether alerts belong to the same intrusion. For the initial setting (A Defender incident spans cloud and on-prem signals across a prolonged campaign), that does not itself meet the new condition: The shared IP is confirmed as a common public proxy.
Question 565
A security operations analyst must handle this situation: An Exchange incident contains malicious messages with many affected recipients. What is the BEST initial response?
- Create an appropriately scoped Sentinel data-lake KQL job with confirmed retention and billing
- Investigate and remove the unauthorized rule and examine mailbox audit history
- Remove only the alert email from the analyst inbox
- Search the incident's email evidence and remediate all confirmed malicious mail in scope
Explanation
Correct Answer
D:Recipient and message evidence allow targeted cleanup and containment across mailboxes. The selected action is: Search the incident's email evidence and remediate all confirmed malicious mail in scope.
Incorrect Answers
A:That action serves a separate case (A hunter wants an asynchronous historical join across multiple low-touch event tables) in the Perform threat hunting domain. It does not specifically address the initial case.
B:This action would become suitable if a later condition arose: The attacker configured a malicious inbox forwarding rule. It is not the immediate answer to An Exchange incident contains malicious messages with many affected recipients.
C:That action leaves other targeted users and copied messages exposed. The shortcut Remove only the alert email from the analyst inbox does not resolve the case involving An Exchange incident contains malicious messages with many affected recipients.
Question 566
An Exchange incident contains malicious messages with many affected recipients. Why should the SOC reject the proposed shortcut: Remove only the alert email from the analyst inbox?
- Recipient and message evidence allow targeted cleanup and containment across mailboxes
- That action leaves other targeted users and copied messages exposed
- Real-time analytics rules are not the general query path for lake-only historical tables
- A familiar product name alone establishes that the proposal is safe.
Explanation
Correct Answer
B:That action leaves other targeted users and copied messages exposed. This directly explains the defect in Remove only the alert email from the analyst inbox for An Exchange incident contains malicious messages with many affected recipients.
Incorrect Answers
A:This describes the reason for the preferred control, Search the incident's email evidence and remediate all confirmed malicious mail in scope: Recipient and message evidence allow targeted cleanup and containment across mailboxes. It is not the direct defect in the proposed shortcut for An Exchange incident contains malicious messages with many affected recipients.
C:That concern applies to another security scenario (A hunter wants an asynchronous historical join across multiple low-touch event tables). Here, An Exchange incident contains malicious messages with many affected recipients, the specified proposal fails because that action leaves other targeted users and copied messages exposed.
D:Product-name familiarity cannot validate a proposed security action. For An Exchange incident contains malicious messages with many affected recipients, the actual issue is that that action leaves other targeted users and copied messages exposed.
Question 567
An Exchange incident contains malicious messages with many affected recipients. The SOC implements Search the incident's email evidence and remediate all confirmed malicious mail in scope. Which observed result provides credible confirmation?
- The SOC approves Search the incident's email evidence and remediate all confirmed malicious mail in scope on paper but has not tested its operation.
- No confirmed malicious copies remain accessible in sampled affected mailboxes
- The team schedules a future check of whether no confirmed malicious copies remain accessible in sampled affected mailboxes, without recording any observed result.
- The completed job returns relevant historical records with a reproducible query
Explanation
Correct Answer
B:Correct observed evidence. No confirmed malicious copies remain accessible in sampled affected mailboxes. Given the original requirement, that result would substantiate the selected action, Search the incident's email evidence and remediate all confirmed malicious mail in scope.
Incorrect Answers
A:Approval records intent but not actual protection or investigation. For An Exchange incident contains malicious messages with many affected recipients, an operational outcome must demonstrate that no confirmed malicious copies remain accessible in sampled affected mailboxes.
C:A future validation plan is not an observed result. The actual verification should establish that no confirmed malicious copies remain accessible in sampled affected mailboxes, in the scenario involving An Exchange incident contains malicious messages with many affected recipients.
D:This observation fits another setting (A hunter wants an asynchronous historical join across multiple low-touch event tables). It does not verify Search the incident's email evidence and remediate all confirmed malicious mail in scope against the original need.
Question 568
The original problem was: An Exchange incident contains malicious messages with many affected recipients. The solution is operating, but the attacker configured a malicious inbox forwarding rule. What should change next?
- Remove only the alert email from the analyst inbox
- The completed job returns relevant historical records with a reproducible query
- Investigate and remove the unauthorized rule and examine mailbox audit history
- Search the incident's email evidence and remediate all confirmed malicious mail in scope
Explanation
Correct Answer
C:Correct follow-up. The requirement changed to: The attacker configured a malicious inbox forwarding rule. Therefore Investigate and remove the unauthorized rule and examine mailbox audit history is appropriate for An Exchange incident contains malicious messages with many affected recipients, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because that action leaves other targeted users and copied messages exposed. It also fails after the change affecting An Exchange incident contains malicious messages with many affected recipients.
B:An observation is not the additional configuration or response action requested. The change is The attacker configured a malicious inbox forwarding rule, so the proper follow-up must address it rather than merely note The completed job returns relevant historical records with a reproducible query.
D:This was the original control already implemented: Search the incident's email evidence and remediate all confirmed malicious mail in scope. Its original rationale was: Recipient and message evidence allow targeted cleanup and containment across mailboxes. For the initial setting (An Exchange incident contains malicious messages with many affected recipients), that does not itself meet the new condition: The attacker configured a malicious inbox forwarding rule.
Question 569
An attacker sent internal follow-up messages after compromising one mailbox. Which configuration or investigation step is MOST appropriate?
- Remove only the alert email from the analyst inbox
- Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields
- Search the incident's email evidence and remediate all confirmed malicious mail in scope
- Investigate and remove the unauthorized rule and examine mailbox audit history
Explanation
Correct Answer
C:Recipient and message evidence allow targeted cleanup and containment across mailboxes. The selected action is: Search the incident's email evidence and remediate all confirmed malicious mail in scope.
Incorrect Answers
A:That action leaves other targeted users and copied messages exposed. The shortcut Remove only the alert email from the analyst inbox does not resolve the case involving An attacker sent internal follow-up messages after compromising one mailbox.
B:That action serves a separate case (A SOC queries which process created a suspicious script interpreter on Windows endpoints) in the Perform threat hunting domain. It does not specifically address the initial case.
D:This action would become suitable if a later condition arose: The attacker configured a malicious inbox forwarding rule. It is not the immediate answer to An attacker sent internal follow-up messages after compromising one mailbox.
Question 570
An attacker sent internal follow-up messages after compromising one mailbox. Which statement BEST explains why the proposed approach (Remove only the alert email from the analyst inbox) fails?
- Email delivery events do not contain complete process-creation telemetry
- That action leaves other targeted users and copied messages exposed
- A familiar product name alone establishes that the proposal is safe.
- Recipient and message evidence allow targeted cleanup and containment across mailboxes
Explanation
Correct Answer
B:That action leaves other targeted users and copied messages exposed. This directly explains the defect in Remove only the alert email from the analyst inbox for An attacker sent internal follow-up messages after compromising one mailbox.
Incorrect Answers
A:That concern applies to another security scenario (A SOC queries which process created a suspicious script interpreter on Windows endpoints). Here, An attacker sent internal follow-up messages after compromising one mailbox, the specified proposal fails because that action leaves other targeted users and copied messages exposed.
C:Product-name familiarity cannot validate a proposed security action. For An attacker sent internal follow-up messages after compromising one mailbox, the actual issue is that that action leaves other targeted users and copied messages exposed.
D:This describes the reason for the preferred control, Search the incident's email evidence and remediate all confirmed malicious mail in scope: Recipient and message evidence allow targeted cleanup and containment across mailboxes. It is not the direct defect in the proposed shortcut for An attacker sent internal follow-up messages after compromising one mailbox.