100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 360
A responder needs to visualize how a compromised workstation, user account and related process evidence connect to a ransomware incident. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review time-bin definitions and field availability after alert scheduling changes.
- Monitor changes in event JSON property names and guard the query against missing fields.
- Review graph data scope and remove stale or disproven entity links when the incident evolves.
- Version the KQL and revisit assumptions after technique variants or schema changes.
Explanation
Correct Answer
C:Uncorrected links may overstate affected infrastructure.
Incorrect Answers
A:Inconsistent windows can distort trends across weeks. That is relevant to counting distinct affected devices in time windows, whereas this requirement concerns creating a blast-radius hunting graph from observed entities.
B:Optional nested attributes can disappear after sensor updates. It does not establish creating a blast-radius hunting graph from observed entities, which is the specific issue in this case.
D:Hunting queries require maintenance as attacks and logs evolve. That addresses turning a hypothesis into a repeatable Defender XDR hunting query, not the stated need for creating a blast-radius hunting graph from observed entities.
Question 361
A Sentinel Graph analyst needs to trace a suspicious identity to cloud resources and endpoint processes without assuming all neighboring objects are compromised. What should the administrator configure to address this exact situation?
- Join the appropriate Advanced Hunting EmailEvents and EmailAttachmentInfo on their common message identifier.
- Create a focused Advanced Hunting KQL query to test the technique hypothesis against relevant endpoint events.
- Use Sentinel Graph to investigate supported entity relationships and pivot to source evidence for observed connections.
- Use the appropriate Defender XDR identity sign-in or logon hunting table to correlate failure-to-success sequences.
Explanation
Correct Answer
C:Graph relationships help scope threat hunting across heterogeneous security data.
Incorrect Answers
A:A message-to-attachment join reveals campaign attachment properties alongside recipients. It does not establish traversing validated entity relationships in Sentinel Graph, which is the specific issue in this case.
B:A hypothesis-driven hunt specifies both behavior and the evidence that would confirm it. The scenario calls for traversing validated entity relationships in Sentinel Graph, not that separate action.
D:Account, target and timestamp evidence can reveal suspicious authentication attempts. That is relevant to hunting unusual privileged identity logon sequences, whereas this requirement concerns traversing validated entity relationships in Sentinel Graph.
Question 362
A Sentinel Graph analyst needs to trace a suspicious identity to cloud resources and endpoint processes without assuming all neighboring objects are compromised. The team has selected: Use Sentinel Graph to investigate supported entity relationships and pivot to source evidence for observed connections. Which operational step implements the chosen approach?
- Add verified device and identity relationships from hunting results and avoid including unobserved inferred links.
- Filter the selected event tables by supported command and process fields, then add device and time context.
- Start from the confirmed entity and expand connected nodes with their underlying event and time-window context.
- Filter Advanced Hunting data for relevant indicators and affected time range while preserving device and identity attribution.
Explanation
Correct Answer
C:An account adjacency is a lead, not automatically proof of compromise.
Incorrect Answers
A:The graph should represent actual entity evidence, not every same-subnet device. The scenario calls for traversing validated entity relationships in Sentinel Graph, not that separate action.
B:Detections based on one common command name produce noisy results. That addresses turning a hypothesis into a repeatable Defender XDR hunting query, not the stated need for traversing validated entity relationships in Sentinel Graph.
D:An indicator should be paired with observed local activity. It does not establish traversing validated entity relationships in Sentinel Graph, which is the specific issue in this case.
Question 363
A Sentinel Graph analyst needs to trace a suspicious identity to cloud resources and endpoint processes without assuming all neighboring objects are compromised. The team implements: Use Sentinel Graph to investigate supported entity relationships and pivot to source evidence for observed connections. What outcome would best validate the implementation?
- Correlate a matching process event with its device timeline and parent Office process to verify actual execution.
- Confirm regular outbound connections and supporting endpoint process evidence on a sampled affected device.
- Verify joined message identifiers and recipients against one known delivery in email investigation tools.
- Validate a suspected identity-to-resource edge against the relevant audit or sign-in event.
Explanation
Correct Answer
D:Every escalated graph link should be supported by an actual record.
Incorrect Answers
A:A string match alone may include harmless scheduled administration. That addresses hunting suspicious process command lines in Defender XDR, not the stated need for traversing validated entity relationships in Sentinel Graph.
B:Periodic traffic alone is not proof of a malicious beacon. That is relevant to detecting possible endpoint beaconing patterns, whereas this requirement concerns traversing validated entity relationships in Sentinel Graph.
C:An incorrect join can manufacture apparently widespread exposure. It does not establish traversing validated entity relationships in Sentinel Graph, which is the specific issue in this case.
Question 364
A Sentinel Graph analyst needs to trace a suspicious identity to cloud resources and endpoint processes without assuming all neighboring objects are compromised. The setting is now in production. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review graph data scope and remove stale or disproven entity links when the incident evolves.
- Review time-bin definitions and field availability after alert scheduling changes.
- Restrict the breadth of graph pivots and review newly ingested relation types after connector changes.
- Refresh indicator intelligence as campaigns rotate infrastructure and retire stale indicators.
Explanation
Correct Answer
C:Unbounded neighbor expansion can swamp analysts with unrelated associations.
Incorrect Answers
A:Uncorrected links may overstate affected infrastructure. That is relevant to creating a blast-radius hunting graph from observed entities, whereas this requirement concerns traversing validated entity relationships in Sentinel Graph.
B:Inconsistent windows can distort trends across weeks. It does not establish traversing validated entity relationships in Sentinel Graph, which is the specific issue in this case.
D:A static indicator can outlive the associated attack campaign. That addresses pivoting from XDR threat analytics into actual observed hunting results, not the stated need for traversing validated entity relationships in Sentinel Graph.
Question 365
An analyst needs a proactive search for a newly published technique that appears as unusual command sequences across a fleet. What should the administrator configure to address this exact situation?
- Use the appropriate Defender XDR identity sign-in or logon hunting table to correlate failure-to-success sequences.
- Query Defender XDR DeviceFileEvents for the confirmed SHA256 and relevant file actions.
- Create a focused Advanced Hunting KQL query to test the technique hypothesis against relevant endpoint events.
- Correlate DeviceProcessEvents and DeviceNetworkEvents using device and suitable process identifiers.
Explanation
Correct Answer
C:A hypothesis-driven hunt specifies both behavior and the evidence that would confirm it.
Incorrect Answers
A:Account, target and timestamp evidence can reveal suspicious authentication attempts. It does not establish turning a hypothesis into a repeatable Defender XDR hunting query, which is the specific issue in this case.
B:File event records can locate devices where the same content was written or modified. The scenario calls for turning a hypothesis into a repeatable Defender XDR hunting query, not that separate action.
D:Process-network linkage can attribute traffic to the process that generated it. That is relevant to correlating process launches with endpoint network connections, whereas this requirement concerns turning a hypothesis into a repeatable Defender XDR hunting query.
Question 366
An analyst needs a proactive search for a newly published technique that appears as unusual command sequences across a fleet. The project chooses: Create a focused Advanced Hunting KQL query to test the technique hypothesis against relevant endpoint events. Which operational step implements the chosen approach?
- Filter for the privileged identity and join or summarize outcomes by account and target within a short timeframe.
- Filter the supported SHA256 field and project DeviceId, Timestamp, FolderPath and ActionType.
- Filter the suspected delivery window and join on NetworkMessageId, then project recipient and attachment metadata.
- Filter the selected event tables by supported command and process fields, then add device and time context.
Explanation
Correct Answer
D:Detections based on one common command name produce noisy results.
Incorrect Answers
A:Sequence matters more than total failure count across unrelated users. The scenario calls for turning a hypothesis into a repeatable Defender XDR hunting query, not that separate action.
B:Hash-based matching avoids relying on changeable filenames. That addresses hunting malicious file activity by exact SHA-256, not the stated need for turning a hypothesis into a repeatable Defender XDR hunting query.
C:Message-level keys avoid incorrect cross-mailbox joins by filename alone. That is relevant to joining Defender XDR email and attachment evidence, whereas this requirement concerns turning a hypothesis into a repeatable Defender XDR hunting query.
Question 367
An analyst needs a proactive search for a newly published technique that appears as unusual command sequences across a fleet. The intended configuration is: Create a focused Advanced Hunting KQL query to test the technique hypothesis against relevant endpoint events. Which TWO actions together implement this solution and verify the desired outcome? Choose TWO.
- Compare extracted values with the original raw event on representative cases with and without the field.
- Run positive and negative example events and compare findings with verified endpoint timelines.
- Use the appropriate Defender XDR identity sign-in or logon hunting table to correlate failure-to-success sequences.
- Filter the selected event tables by supported command and process fields, then add device and time context.
- Filter the suspected delivery window and join on NetworkMessageId, then project recipient and attachment metadata.
Explanation
Correct Answers
B:A useful query separates the threat pattern from normal administration.
D:Detections based on one common command name produce noisy results.
Incorrect Answers
A:Null and type-handling checks identify brittle parsing. That addresses extracting nested values safely in KQL hunting, not the stated need for turning a hypothesis into a repeatable Defender XDR hunting query.
C:Account, target and timestamp evidence can reveal suspicious authentication attempts. It does not establish turning a hypothesis into a repeatable Defender XDR hunting query, which is the specific issue in this case.
E:Message-level keys avoid incorrect cross-mailbox joins by filename alone. That addresses joining Defender XDR email and attachment evidence, not the stated need for turning a hypothesis into a repeatable Defender XDR hunting query.
Question 368
An analyst needs a proactive search for a newly published technique that appears as unusual command sequences across a fleet. After rollout, the organization wants continuing assurance. Which ongoing control best addresses the risk that the protection may become ineffective?
- Restrict the breadth of graph pivots and review newly ingested relation types after connector changes.
- Review query assumptions when sensor fields or attack command-line obfuscation patterns change.
- Review approved software polling intervals and network-event field availability as exclusions evolve.
- Version the KQL and revisit assumptions after technique variants or schema changes.
Explanation
Correct Answer
D:Hunting queries require maintenance as attacks and logs evolve.
Incorrect Answers
A:Unbounded neighbor expansion can swamp analysts with unrelated associations. That is relevant to traversing validated entity relationships in Sentinel Graph, whereas this requirement concerns turning a hypothesis into a repeatable Defender XDR hunting query.
B:A stale string filter may stop seeing the technique. It does not establish turning a hypothesis into a repeatable Defender XDR hunting query, which is the specific issue in this case.
C:Normal updaters can resemble C2 beacons. The scenario calls for turning a hypothesis into a repeatable Defender XDR hunting query, not that separate action.
Question 369
A Sentinel analyst repeatedly searches for unusual sign-in activity across multiple workspaces and wants teammates to reuse the hunt. What should the administrator configure to address this exact situation?
- Use a supported KQL cross-workspace query with explicit workspace references and normalized columns.
- Use Microsoft Sentinel summary rules to aggregate source events into a suitable analytics-tier summary table.
- Use a filtered KQL data-lake job with an intentionally narrow destination schema and selected high-risk results.
- Create a saved Microsoft Sentinel hunting query with the KQL and appropriate ATT&CK context.
Explanation
Correct Answer
D:Saved hunting content makes hypotheses repeatable across analysts.
Incorrect Answers
A:Cross-workspace queries can correlate security events without copying all raw tables into one store. It does not establish maintaining reusable Sentinel hunting queries, which is the specific issue in this case.
B:Summary rules provide recurring reductions instead of rescanning every raw record. The scenario calls for maintaining reusable Sentinel hunting queries, not that separate action.
C:Promoting only useful findings reduces analytics-tier storage and downstream query costs. That addresses controlling KQL job output scope and cost, not the stated need for maintaining reusable Sentinel hunting queries.
Question 370
A Sentinel analyst repeatedly searches for unusual sign-in activity across multiple workspaces and wants teammates to reuse the hunt. The proposed configuration is: Create a saved Microsoft Sentinel hunting query with the KQL and appropriate ATT&CK context. Which operational step implements the chosen approach?
- Configure the documented MCP connection and validate allowed tool calls against the target Sentinel environment.
- Store the query with its description, applicable event table and query parameters in supported Sentinel hunting tools.
- Filter the historical events and project required columns before selecting the analytics destination table.
- Configure the notebook's approved identity and data access, then execute the Python analysis against the intended subset.
Explanation
Correct Answer
B:Clear scope documents why the query should match.
Incorrect Answers
A:The tool endpoint and authentication must be explicitly approved. The scenario calls for maintaining reusable Sentinel hunting queries, not that separate action.
C:Unfiltered broad exports create unnecessary cost and sensitive-data exposure. That is relevant to controlling KQL job output scope and cost, whereas this requirement concerns maintaining reusable Sentinel hunting queries.
D:Temporary credentials should not be embedded in shared notebook code. It does not establish maintaining reusable Sentinel hunting queries, which is the specific issue in this case.
Microsoft Security Operations Analyst (SC-200) Practice Tests