Microsoft SC-200 Practice Test 70
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.
Question 691
An analyst wants process lineage and command-line context rather than malware name alone. Which operational finding would validate the selected solution, Inspect DeviceProcessEvents with command-line and initiating process fields?
- The output shows expected hourly counts per investigated account
- 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 SOC approves Inspect DeviceProcessEvents with command-line and initiating process fields on paper but has not tested its operation.
- 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 (An analyst needs counts of failed sign-ins per account over one-hour buckets). It does not verify Inspect DeviceProcessEvents with command-line and initiating process fields against the original need.
B: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 An analyst wants process lineage and command-line context rather than malware name alone.
C:Approval records intent but not actual protection or investigation. For An analyst wants process lineage and command-line context rather than malware name alone, an operational outcome must demonstrate that the matching process creation record exposes parent process and command line.
Question 692
An analyst wants process lineage and command-line context rather than malware name alone. After the initial control is implemented, the process also downloaded a remote script. What is the best follow-up action?
- Inspect DeviceProcessEvents with command-line and initiating process fields
- The matching process creation record exposes parent process and command line
- Correlate the process key and time with the network-event table
- Query only DeviceNetworkEvents and assume it includes every process creation
Explanation
Correct Answer
C: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 An analyst wants process lineage and command-line context rather than malware name alone, 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 (An analyst wants process lineage and command-line context rather than malware name alone), that does not itself meet the new condition: The process also downloaded a remote script.
B: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 The matching process creation record exposes parent process and command line.
D: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 An analyst wants process lineage and command-line context rather than malware name alone.
Question 693
An endpoint reported an unexpected outbound connection to a suspicious IP. Which action BEST addresses this Microsoft security operations requirement?
- Infer the destination from a local file hash without any network telemetry
- Use relevant DeviceNetworkEvents and join to process evidence using reliable keys
- Create a supported hunting bookmark or incident evidence link with context
- Validate signed process identity and approved network destination before disposition
Explanation
Correct Answer
B:Network telemetry records remote endpoints and initiator context for device connections. The selected action is: Use relevant DeviceNetworkEvents and join to process evidence using reliable keys.
Incorrect Answers
A:A file hash is not a substitute for an observed connection record. The shortcut Infer the destination from a local file hash without any network telemetry does not resolve the case involving An endpoint reported an unexpected outbound connection to a suspicious IP.
C:That action serves a separate case (A SOC wants to preserve noteworthy query results for a continuing investigation) 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 connection is associated with a scheduled management agent. It is not the immediate answer to An endpoint reported an unexpected outbound connection to a suspicious IP.
Question 694
An endpoint reported an unexpected outbound connection to a suspicious IP. A colleague suggests: Infer the destination from a local file hash without any network telemetry. What is the MOST important technical defect in this suggestion?
- A familiar product name alone establishes that the proposal is safe.
- Network telemetry records remote endpoints and initiator context for device connections
- A file hash is not a substitute for an observed connection record
- Unlinked images can lose query provenance and source event detail
Explanation
Correct Answer
C:A file hash is not a substitute for an observed connection record. This directly explains the defect in Infer the destination from a local file hash without any network telemetry for An endpoint reported an unexpected outbound connection to a suspicious IP.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For An endpoint reported an unexpected outbound connection to a suspicious IP, the actual issue is that a file hash is not a substitute for an observed connection record.
B:This describes the reason for the preferred control, Use relevant DeviceNetworkEvents and join to process evidence using reliable keys: Network telemetry records remote endpoints and initiator context for device connections. It is not the direct defect in the proposed shortcut for An endpoint reported an unexpected outbound connection to a suspicious IP.
D:That concern applies to another security scenario (A SOC wants to preserve noteworthy query results for a continuing investigation). Here, An endpoint reported an unexpected outbound connection to a suspicious IP, the specified proposal fails because a file hash is not a substitute for an observed connection record.
Question 695
An endpoint reported an unexpected outbound connection to a suspicious IP. After implementing Use relevant DeviceNetworkEvents and join to process evidence using reliable keys, what result would BEST establish that it worked?
- The SOC approves Use relevant DeviceNetworkEvents and join to process evidence using reliable keys on paper but has not tested its operation.
- The case preserves selected event identifiers, query and time range
- The team schedules a future check of whether evidence identifies source device, remote IP and originating executable, without recording any observed result.
- Evidence identifies source device, remote IP and originating executable
Explanation
Correct Answer
D:Correct observed evidence. Evidence identifies source device, remote IP and originating executable. Given the original requirement, that result would substantiate the selected action, Use relevant DeviceNetworkEvents and join to process evidence using reliable keys.
Incorrect Answers
A:Approval records intent but not actual protection or investigation. For An endpoint reported an unexpected outbound connection to a suspicious IP, an operational outcome must demonstrate that evidence identifies source device, remote IP and originating executable.
B:This observation fits another setting (A SOC wants to preserve noteworthy query results for a continuing investigation). It does not verify Use relevant DeviceNetworkEvents and join to process evidence using reliable keys against the original need.
C:A future validation plan is not an observed result. The actual verification should establish that evidence identifies source device, remote IP and originating executable, in the scenario involving An endpoint reported an unexpected outbound connection to a suspicious IP.
Question 696
An endpoint reported an unexpected outbound connection to a suspicious IP. The original measure is in place. A new requirement arises: The connection is associated with a scheduled management agent. Which ADDITIONAL action BEST fits?
- Validate signed process identity and approved network destination before disposition
- The case preserves selected event identifiers, query and time range
- Use relevant DeviceNetworkEvents and join to process evidence using reliable keys
- Infer the destination from a local file hash without any network telemetry
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: The connection is associated with a scheduled management agent. Therefore Validate signed process identity and approved network destination before disposition is appropriate for An endpoint reported an unexpected outbound connection to a suspicious IP, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is The connection is associated with a scheduled management agent, so the proper follow-up must address it rather than merely note The case preserves selected event identifiers, query and time range.
C:This was the original control already implemented: Use relevant DeviceNetworkEvents and join to process evidence using reliable keys. Its original rationale was: Network telemetry records remote endpoints and initiator context for device connections. For the initial setting (An endpoint reported an unexpected outbound connection to a suspicious IP), that does not itself meet the new condition: The connection is associated with a scheduled management agent.
D:This was already unsuitable under the original condition because a file hash is not a substitute for an observed connection record. It also fails after the change affecting An endpoint reported an unexpected outbound connection to a suspicious IP.
Question 697
A responder wants the originating process and destination fields for lateral-movement review. Select THREE entries that identify the recommended control, its supporting technical rationale, and a reliable verification outcome. (Select THREE.)
- Configure supported Sentinel notebook and MCP integration with authenticated scope and tool validation
- Use relevant DeviceNetworkEvents and join to process evidence using reliable keys
- Network telemetry records remote endpoints and initiator context for device connections
- Validate signed process identity and approved network destination before disposition
- Evidence identifies source device, remote IP and originating executable
- Infer the destination from a local file hash without any network telemetry
Explanation
Correct Answers
B:Network telemetry records remote endpoints and initiator context for device connections. The selected action is: Use relevant DeviceNetworkEvents and join to process evidence using reliable keys.
C:Correct technical justification. Network telemetry records remote endpoints and initiator context for device connections. That rationale supports the recommended control, Use relevant DeviceNetworkEvents and join to process evidence using reliable keys, for the scenario involving A responder wants the originating process and destination fields for lateral-movement review.
E:Correct validation criterion. Evidence identifies source device, remote IP and originating executable. This observable finding confirms the goal in the scenario: A responder wants the originating process and destination fields for lateral-movement review.
Incorrect Answers
A:That action serves a separate case (A SOC wants to use a Jupyter notebook with the Sentinel MCP Server) 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 connection is associated with a scheduled management agent. It is not the immediate answer to A responder wants the originating process and destination fields for lateral-movement review.
F:A file hash is not a substitute for an observed connection record. The shortcut Infer the destination from a local file hash without any network telemetry does not resolve the case involving A responder wants the originating process and destination fields for lateral-movement review.
Question 698
A responder wants the originating process and destination fields for lateral-movement review. Why should the SOC reject the proposed shortcut: Infer the destination from a local file hash without any network telemetry?
- A familiar product name alone establishes that the proposal is safe.
- A file hash is not a substitute for an observed connection record
- Network telemetry records remote endpoints and initiator context for device connections
- Untrusted tool access can expose security data and credentials
Explanation
Correct Answer
B:A file hash is not a substitute for an observed connection record. This directly explains the defect in Infer the destination from a local file hash without any network telemetry for A responder wants the originating process and destination fields for lateral-movement review.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A responder wants the originating process and destination fields for lateral-movement review, the actual issue is that a file hash is not a substitute for an observed connection record.
C:This describes the reason for the preferred control, Use relevant DeviceNetworkEvents and join to process evidence using reliable keys: Network telemetry records remote endpoints and initiator context for device connections. It is not the direct defect in the proposed shortcut for A responder wants the originating process and destination fields for lateral-movement review.
D:That concern applies to another security scenario (A SOC wants to use a Jupyter notebook with the Sentinel MCP Server). Here, A responder wants the originating process and destination fields for lateral-movement review, the specified proposal fails because a file hash is not a substitute for an observed connection record.
Question 699
A responder wants the originating process and destination fields for lateral-movement review. The SOC implements Use relevant DeviceNetworkEvents and join to process evidence using reliable keys. Which observed result provides credible confirmation?
- Evidence identifies source device, remote IP and originating executable
- The team schedules a future check of whether evidence identifies source device, remote IP and originating executable, without recording any observed result.
- The SOC approves Use relevant DeviceNetworkEvents and join to process evidence using reliable keys on paper but has not tested its operation.
- The authorized notebook invokes the expected tool and records its provenance
Explanation
Correct Answer
A:Correct observed evidence. Evidence identifies source device, remote IP and originating executable. Given the original requirement, that result would substantiate the selected action, Use relevant DeviceNetworkEvents and join to process evidence using reliable keys.
Incorrect Answers
B:A future validation plan is not an observed result. The actual verification should establish that evidence identifies source device, remote IP and originating executable, in the scenario involving A responder wants the originating process and destination fields for lateral-movement review.
C:Approval records intent but not actual protection or investigation. For A responder wants the originating process and destination fields for lateral-movement review, an operational outcome must demonstrate that evidence identifies source device, remote IP and originating executable.
D:This observation fits another setting (A SOC wants to use a Jupyter notebook with the Sentinel MCP Server). It does not verify Use relevant DeviceNetworkEvents and join to process evidence using reliable keys against the original need.
Question 700
The original problem was: A responder wants the originating process and destination fields for lateral-movement review. The solution is operating, but the connection is associated with a scheduled management agent. What should change next?
- Evidence identifies source device, remote IP and originating executable
- Use relevant DeviceNetworkEvents and join to process evidence using reliable keys
- Infer the destination from a local file hash without any network telemetry
- Validate signed process identity and approved network destination before disposition
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: The connection is associated with a scheduled management agent. Therefore Validate signed process identity and approved network destination before disposition is appropriate for A responder wants the originating process and destination fields for lateral-movement review, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is The connection is associated with a scheduled management agent, so the proper follow-up must address it rather than merely note Evidence identifies source device, remote IP and originating executable.
B:This was the original control already implemented: Use relevant DeviceNetworkEvents and join to process evidence using reliable keys. Its original rationale was: Network telemetry records remote endpoints and initiator context for device connections. For the initial setting (A responder wants the originating process and destination fields for lateral-movement review), that does not itself meet the new condition: The connection is associated with a scheduled management agent.
C:This was already unsuitable under the original condition because a file hash is not a substitute for an observed connection record. It also fails after the change affecting A responder wants the originating process and destination fields for lateral-movement review.