Microsoft SC-200 Practice Test 79
Question 780
A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs. The original measure is in place. A new requirement arises: A new identity log identifies an additional session associated with the actor. Which ADDITIONAL action BEST fits?
- A verified actor or application link ties the two event streams into a timeline
- Extend correlation to supported Entra sign-in evidence and reassess incident scope
- Merge unrelated events solely by identical minute without checking entity identifiers
- Normalize timestamps and correlate operation, app ID, account and target across both sources
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: A new identity log identifies an additional session associated with the actor. Therefore Extend correlation to supported Entra sign-in evidence and reassess incident scope is appropriate for A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is A new identity log identifies an additional session associated with the actor, so the proper follow-up must address it rather than merely note A verified actor or application link ties the two event streams into a timeline.
C:This was already unsuitable under the original condition because time proximity alone does not establish a causal connection. It also fails after the change affecting A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs.
D:This was the original control already implemented: Normalize timestamps and correlate operation, app ID, account and target across both sources. Its original rationale was: Joining distinct audit streams can reveal application access followed by mailbox changes. For the initial setting (A threat hunter needs a unified chronology from Purview Audit and Microsoft Graph activity logs), that does not itself meet the new condition: A new identity log identifies an additional session associated with the actor.
Question 781
A security operations analyst must handle this situation: An analyst wants to find endpoints that launched a suspicious executable from a temporary directory. What is the BEST initial response?
- Correlate process records with network activity using reliable device and process identifiers
- Query only EmailEvents and infer all endpoint process execution from message delivery
- Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields
- Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings
Explanation
Correct Answer
C:DeviceProcessEvents holds endpoint process creation records including executable and parent context. The selected action is: Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields.
Incorrect Answers
A:This action would become suitable if a later condition arose: The process contacted a suspicious external address. It is not the immediate answer to An analyst wants to find endpoints that launched a suspicious executable from a temporary directory.
B:Email delivery events do not contain complete process-creation telemetry. The shortcut Query only EmailEvents and infer all endpoint process execution from message delivery does not resolve the case involving An analyst wants to find endpoints that launched a suspicious executable from a temporary directory.
D:That action serves a separate case (An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel) in the Manage a security operations environment domain. It does not specifically address the initial case.
Question 782
An analyst wants to find endpoints that launched a suspicious executable from a temporary directory. Why should the SOC reject the proposed shortcut: Query only EmailEvents and infer all endpoint process execution from message delivery?
- A workbook title does not ingest or normalize indicator records
- A familiar product name alone establishes that the proposal is safe.
- DeviceProcessEvents holds endpoint process creation records including executable and parent context
- Email delivery events do not contain complete process-creation telemetry
Explanation
Correct Answer
D:Email delivery events do not contain complete process-creation telemetry. This directly explains the defect in Query only EmailEvents and infer all endpoint process execution from message delivery for An analyst wants to find endpoints that launched a suspicious executable from a temporary directory.
Incorrect Answers
A:That concern applies to another security scenario (An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel). Here, An analyst wants to find endpoints that launched a suspicious executable from a temporary directory, the specified proposal fails because email delivery events do not contain complete process-creation telemetry.
B:Product-name familiarity cannot validate a proposed security action. For An analyst wants to find endpoints that launched a suspicious executable from a temporary directory, the actual issue is that email delivery events do not contain complete process-creation telemetry.
C:This describes the reason for the preferred control, Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields: DeviceProcessEvents holds endpoint process creation records including executable and parent context. It is not the direct defect in the proposed shortcut for An analyst wants to find endpoints that launched a suspicious executable from a temporary directory.
Question 783
An analyst wants to find endpoints that launched a suspicious executable from a temporary directory. The SOC implements Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields. Which observed result provides credible confirmation?
- Sample approved indicators appear with type, confidence and provenance fields
- The SOC approves Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields on paper but has not tested its operation.
- The team schedules a future check of whether matching records show executable, device, timestamp and parent process fields, without recording any observed result.
- Matching records show executable, device, timestamp and parent process fields
Explanation
Correct Answer
D:Correct observed evidence. Matching records show executable, device, timestamp and parent process fields. Given the original requirement, that result would substantiate the selected action, Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields.
Incorrect Answers
A:This observation fits another setting (An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel). It does not verify Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields against the original need.
B:Approval records intent but not actual protection or investigation. For An analyst wants to find endpoints that launched a suspicious executable from a temporary directory, an operational outcome must demonstrate that matching records show executable, device, timestamp and parent process fields.
C:A future validation plan is not an observed result. The actual verification should establish that matching records show executable, device, timestamp and parent process fields, in the scenario involving An analyst wants to find endpoints that launched a suspicious executable from a temporary directory.
Question 784
The original problem was: An analyst wants to find endpoints that launched a suspicious executable from a temporary directory. The solution is operating, but the process contacted a suspicious external address. What should change next?
- Query only EmailEvents and infer all endpoint process execution from message delivery
- Sample approved indicators appear with type, confidence and provenance fields
- Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields
- Correlate process records with network activity using reliable device and process identifiers
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: The process contacted a suspicious external address. Therefore Correlate process records with network activity using reliable device and process identifiers is appropriate for An analyst wants to find endpoints that launched a suspicious executable from a temporary directory, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because email delivery events do not contain complete process-creation telemetry. It also fails after the change affecting An analyst wants to find endpoints that launched a suspicious executable from a temporary directory.
B:An observation is not the additional configuration or response action requested. The change is The process contacted a suspicious external address, so the proper follow-up must address it rather than merely note Sample approved indicators appear with type, confidence and provenance fields.
C:This was the original control already implemented: Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields. Its original rationale was: DeviceProcessEvents holds endpoint process creation records including executable and parent context. For the initial setting (An analyst wants to find endpoints that launched a suspicious executable from a temporary directory), that does not itself meet the new condition: The process contacted a suspicious external address.
Question 785
A SOC queries which process created a suspicious script interpreter on Windows endpoints. Which configuration or investigation step is MOST appropriate?
- Create a scheduled Sentinel analytics rule with KQL, timing, entity mapping, and grouping settings
- Query only EmailEvents and infer all endpoint process execution from message delivery
- Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields
- Correlate process records with network activity using reliable device and process identifiers
Explanation
Correct Answer
C:DeviceProcessEvents holds endpoint process creation records including executable and parent context. The selected action is: Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields.
Incorrect Answers
A:That action serves a separate case (A Sentinel team needs a periodic correlation of suspicious sign-ins and network traffic) in the Manage a security operations environment domain. It does not specifically address the initial case.
B:Email delivery events do not contain complete process-creation telemetry. The shortcut Query only EmailEvents and infer all endpoint process execution from message delivery does not resolve the case involving A SOC queries which process created a suspicious script interpreter on Windows endpoints.
D:This action would become suitable if a later condition arose: The process contacted a suspicious external address. It is not the immediate answer to A SOC queries which process created a suspicious script interpreter on Windows endpoints.
Question 786
A SOC queries which process created a suspicious script interpreter on Windows endpoints. Which statement BEST explains why the proposed approach (Query only EmailEvents and infer all endpoint process execution from message delivery) fails?
- A familiar product name alone establishes that the proposal is safe.
- Email delivery events do not contain complete process-creation telemetry
- Workbook charts do not inherently create analytic rule detections
- DeviceProcessEvents holds endpoint process creation records including executable and parent context
Explanation
Correct Answer
B:Email delivery events do not contain complete process-creation telemetry. This directly explains the defect in Query only EmailEvents and infer all endpoint process execution from message delivery for A SOC queries which process created a suspicious script interpreter on Windows endpoints.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A SOC queries which process created a suspicious script interpreter on Windows endpoints, the actual issue is that email delivery events do not contain complete process-creation telemetry.
C:That concern applies to another security scenario (A Sentinel team needs a periodic correlation of suspicious sign-ins and network traffic). Here, A SOC queries which process created a suspicious script interpreter on Windows endpoints, the specified proposal fails because email delivery events do not contain complete process-creation telemetry.
D:This describes the reason for the preferred control, Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields: DeviceProcessEvents holds endpoint process creation records including executable and parent context. It is not the direct defect in the proposed shortcut for A SOC queries which process created a suspicious script interpreter on Windows endpoints.
Question 787
A SOC queries which process created a suspicious script interpreter on Windows endpoints. Which operational finding would validate the selected solution, Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields?
- The SOC approves Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields on paper but has not tested its operation.
- The team schedules a future check of whether matching records show executable, device, timestamp and parent process fields, without recording any observed result.
- Matching test records create an alert with correctly mapped user and IP entities
- Matching records show executable, device, timestamp and parent process fields
Explanation
Correct Answer
D:Correct observed evidence. Matching records show executable, device, timestamp and parent process fields. Given the original requirement, that result would substantiate the selected action, Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields.
Incorrect Answers
A:Approval records intent but not actual protection or investigation. For A SOC queries which process created a suspicious script interpreter on Windows endpoints, an operational outcome must demonstrate that matching records show executable, device, timestamp and parent process fields.
B:A future validation plan is not an observed result. The actual verification should establish that matching records show executable, device, timestamp and parent process fields, in the scenario involving A SOC queries which process created a suspicious script interpreter on Windows endpoints.
C:This observation fits another setting (A Sentinel team needs a periodic correlation of suspicious sign-ins and network traffic). It does not verify Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields against the original need.
Question 788
A SOC queries which process created a suspicious script interpreter on Windows endpoints. After the initial control is implemented, the process contacted a suspicious external address. What is the best follow-up action?
- Matching records show executable, device, timestamp and parent process fields
- Correlate process records with network activity using reliable device and process identifiers
- Query only EmailEvents and infer all endpoint process execution from message delivery
- Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: The process contacted a suspicious external address. Therefore Correlate process records with network activity using reliable device and process identifiers is appropriate for A SOC queries which process created a suspicious script interpreter on Windows endpoints, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is The process contacted a suspicious external address, so the proper follow-up must address it rather than merely note Matching records show executable, device, timestamp and parent process fields.
C:This was already unsuitable under the original condition because email delivery events do not contain complete process-creation telemetry. It also fails after the change affecting A SOC queries which process created a suspicious script interpreter on Windows endpoints.
D:This was the original control already implemented: Query Defender XDR DeviceProcessEvents with appropriate time, file and initiating-process fields. Its original rationale was: DeviceProcessEvents holds endpoint process creation records including executable and parent context. For the initial setting (A SOC queries which process created a suspicious script interpreter on Windows endpoints), that does not itself meet the new condition: The process contacted a suspicious external address.
Question 789
A threat hunter must identify network requests to a known command-and-control destination. Which action BEST addresses this Microsoft security operations requirement?
- Correlate destination with process, URL and other evidence before classifying maliciousness
- Look only at DeviceFileEvents as a substitute for network connection records
- Configure appropriate analytics alert grouping and incident creation settings
- Query Defender XDR DeviceNetworkEvents for remote-address and initiating-process context
Explanation
Correct Answer
D:DeviceNetworkEvents stores network connection evidence from onboarded Defender endpoints. The selected action is: Query Defender XDR DeviceNetworkEvents for remote-address and initiating-process context.
Incorrect Answers
A:This action would become suitable if a later condition arose: The IP address is shared by a common content delivery service. It is not the immediate answer to A threat hunter must identify network requests to a known command-and-control destination.
B:File-operation events do not directly establish remote connection attempts. The shortcut Look only at DeviceFileEvents as a substitute for network connection records does not resolve the case involving A threat hunter must identify network requests to a known command-and-control destination.
C:That action serves a separate case (A SOC wants investigation-friendly grouping without combining unrelated tenants) in the Manage a security operations environment domain. It does not specifically address the initial case.
Question 790
A threat hunter must identify network requests to a known command-and-control destination. A colleague suggests: Look only at DeviceFileEvents as a substitute for network connection records. What is the MOST important technical defect in this suggestion?
- A familiar product name alone establishes that the proposal is safe.
- Overbroad grouping obscures responsibility and investigation scope
- File-operation events do not directly establish remote connection attempts
- DeviceNetworkEvents stores network connection evidence from onboarded Defender endpoints
Explanation
Correct Answer
C:File-operation events do not directly establish remote connection attempts. This directly explains the defect in Look only at DeviceFileEvents as a substitute for network connection records for A threat hunter must identify network requests to a known command-and-control destination.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A threat hunter must identify network requests to a known command-and-control destination, the actual issue is that file-operation events do not directly establish remote connection attempts.
B:That concern applies to another security scenario (A SOC wants investigation-friendly grouping without combining unrelated tenants). Here, A threat hunter must identify network requests to a known command-and-control destination, the specified proposal fails because file-operation events do not directly establish remote connection attempts.
D:This describes the reason for the preferred control, Query Defender XDR DeviceNetworkEvents for remote-address and initiating-process context: DeviceNetworkEvents stores network connection evidence from onboarded Defender endpoints. It is not the direct defect in the proposed shortcut for A threat hunter must identify network requests to a known command-and-control destination.