100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 330
A malicious attachment campaign delivered the same document name with different hashes to dozens of mailboxes. The proposed configuration is: Join the appropriate Advanced Hunting EmailEvents and EmailAttachmentInfo on their common message identifier. Which operational step implements the chosen approach?
- Start from the confirmed entity and expand connected nodes with their underlying event and time-window context.
- 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.
- Filter the suspected delivery window and join on NetworkMessageId, then project recipient and attachment metadata.
Explanation
Correct Answer
D:Message-level keys avoid incorrect cross-mailbox joins by filename alone.
Incorrect Answers
A:An account adjacency is a lead, not automatically proof of compromise. The scenario calls for joining Defender XDR email and attachment evidence, not that separate action.
B:The graph should represent actual entity evidence, not every same-subnet device. That addresses creating a blast-radius hunting graph from observed entities, not the stated need for joining Defender XDR email and attachment evidence.
C:Detections based on one common command name produce noisy results. That is relevant to turning a hypothesis into a repeatable Defender XDR hunting query, whereas this requirement concerns joining Defender XDR email and attachment evidence.
Question 331
A malicious attachment campaign delivered the same document name with different hashes to dozens of mailboxes. The security team selected: Join the appropriate Advanced Hunting EmailEvents and EmailAttachmentInfo on their common message identifier. What outcome would best validate the implementation?
- Verify joined message identifiers and recipients against one known delivery in email investigation tools.
- Compare one interval's unique-device estimate with raw distinct device IDs to check the aggregation meaning.
- Compare extracted values with the original raw event on representative cases with and without the field.
- Verify the initiating process, network destination and execution timing align on the affected endpoint.
Explanation
Correct Answer
A:An incorrect join can manufacture apparently widespread exposure.
Incorrect Answers
B:Counts without a sampling check can hide duplicated events. That is relevant to counting distinct affected devices in time windows, whereas this requirement concerns joining Defender XDR email and attachment evidence.
C:Null and type-handling checks identify brittle parsing. It does not establish joining Defender XDR email and attachment evidence, which is the specific issue in this case.
D:A co-occurring device connection is not proof the target process initiated it. The scenario calls for joining Defender XDR email and attachment evidence, not that separate action.
Question 332
A malicious attachment campaign delivered the same document name with different hashes to dozens of mailboxes. The control has been deployed. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review identity telemetry ingestion coverage and exclusion thresholds after authentication-policy changes.
- Update the IOC inventory when a new script hash or false-positive exception is confirmed.
- Review approved software polling intervals and network-event field availability as exclusions evolve.
- Revalidate table schemas and selected columns after changes to Defender email telemetry.
Explanation
Correct Answer
D:Queries depending on retired fields can silently lose coverage.
Incorrect Answers
A:MFA and VPN changes can shift normal failure rates. That is relevant to hunting unusual privileged identity logon sequences, whereas this requirement concerns joining Defender XDR email and attachment evidence.
B:Attackers can change content without changing script function. It does not establish joining Defender XDR email and attachment evidence, which is the specific issue in this case.
C:Normal updaters can resemble C2 beacons. The scenario calls for joining Defender XDR email and attachment evidence, not that separate action.
Question 333
A privileged identity shows repeated failed logons followed by one success on a server not usually accessed by that account. What should the administrator configure to address this exact situation?
- Use Sentinel Graph to investigate supported entity relationships and pivot to source evidence for observed connections.
- Create a focused Advanced Hunting KQL query to test the technique hypothesis against relevant endpoint events.
- Use DeviceNetworkEvents and time-window aggregations to investigate repeated outbound connection periodicity.
- Use the appropriate Defender XDR identity sign-in or logon hunting table to correlate failure-to-success sequences.
Explanation
Correct Answer
D:Account, target and timestamp evidence can reveal suspicious authentication attempts.
Incorrect Answers
A:Graph relationships help scope threat hunting across heterogeneous security data. It does not establish hunting unusual privileged identity logon sequences, 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 hunting unusual privileged identity logon sequences, not that separate action.
C:Network event timing can distinguish potential command-and-control beacons from normal browsing. That addresses detecting possible endpoint beaconing patterns, not the stated need for hunting unusual privileged identity logon sequences.
Question 334
A privileged identity shows repeated failed logons followed by one success on a server not usually accessed by that account. The control design uses: Use the appropriate Defender XDR identity sign-in or logon hunting table to correlate failure-to-success sequences. Which operational step implements the chosen approach?
- Join relevant process and network records on DeviceId and available process identity plus constrained timestamps.
- Filter for the privileged identity and join or summarize outcomes by account and target within a short timeframe.
- Parse the AdditionalFields value, inspect its keys and convert selected nested properties to the required types.
- Filter the exact tool indicator and group by the one-hour time bin before counting distinct DeviceIds.
Explanation
Correct Answer
B:Sequence matters more than total failure count across unrelated users.
Incorrect Answers
A:Matching only a common hostname would overstate the process attribution. The scenario calls for hunting unusual privileged identity logon sequences, not that separate action.
C:Schema inspection prevents treating all dynamic values as strings. That is relevant to extracting nested values safely in KQL hunting, whereas this requirement concerns hunting unusual privileged identity logon sequences.
D:The grouping should represent affected devices per interval, not event total. It does not establish hunting unusual privileged identity logon sequences, which is the specific issue in this case.
Question 335
A privileged identity shows repeated failed logons followed by one success on a server not usually accessed by that account. The control being evaluated is: Use the appropriate Defender XDR identity sign-in or logon hunting table to correlate failure-to-success sequences. Which TWO actions together implement this solution and verify the desired outcome? Choose TWO.
- Join relevant process and network records on DeviceId and available process identity plus constrained timestamps.
- Verify each apparent campaign match against the observed process, DNS or connection events in the tenant.
- Use Sentinel Graph to investigate supported entity relationships and pivot to source evidence for observed connections.
- Filter for the privileged identity and join or summarize outcomes by account and target within a short timeframe.
- Check that the success follows failures for the same account and destination and corroborate the source device.
Explanation
Correct Answers
D:Sequence matters more than total failure count across unrelated users.
E:Without correlation, benign failures and a separate success may look like one attack.
Incorrect Answers
A:Matching only a common hostname would overstate the process attribution. That addresses correlating process launches with endpoint network connections, not the stated need for hunting unusual privileged identity logon sequences.
B:A list of known hostile domains is not a list of infected machines. That is relevant to pivoting from XDR threat analytics into actual observed hunting results, whereas this requirement concerns hunting unusual privileged identity logon sequences.
C:Graph relationships help scope threat hunting across heterogeneous security data. It does not establish hunting unusual privileged identity logon sequences, which is the specific issue in this case.
Question 336
A privileged identity shows repeated failed logons followed by one success on a server not usually accessed by that account. Six months after deployment, the system has changed. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review query assumptions when sensor fields or attack command-line obfuscation patterns change.
- Review identity telemetry ingestion coverage and exclusion thresholds after authentication-policy changes.
- Revalidate table schemas and selected columns after changes to Defender email telemetry.
- Review approved software polling intervals and network-event field availability as exclusions evolve.
Explanation
Correct Answer
B:MFA and VPN changes can shift normal failure rates.
Incorrect Answers
A:A stale string filter may stop seeing the technique. That is relevant to hunting suspicious process command lines in Defender XDR, whereas this requirement concerns hunting unusual privileged identity logon sequences.
C:Queries depending on retired fields can silently lose coverage. The scenario calls for hunting unusual privileged identity logon sequences, not that separate action.
D:Normal updaters can resemble C2 beacons. That addresses detecting possible endpoint beaconing patterns, not the stated need for hunting unusual privileged identity logon sequences.
Question 337
The SOC has a verified SHA-256 of a malicious script and needs all endpoints that created or modified that file. What should the administrator configure to address this exact situation?
- Use KQL summarize dcount(DeviceId) with bin(Timestamp, 1h) on the targeted process events.
- Correlate DeviceProcessEvents and DeviceNetworkEvents using device and suitable process identifiers.
- Use KQL parse_json() with appropriate dynamic field access for supported structured event details.
- Query Defender XDR DeviceFileEvents for the confirmed SHA256 and relevant file actions.
Explanation
Correct Answer
D:File event records can locate devices where the same content was written or modified.
Incorrect Answers
A:Distinct-device aggregation avoids inflating impact from repeated launches on one host. It does not establish hunting malicious file activity by exact SHA-256, which is the specific issue in this case.
B:Process-network linkage can attribute traffic to the process that generated it. The scenario calls for hunting malicious file activity by exact SHA-256, not that separate action.
C:Nested properties must be explicitly decoded before reliable filtering. That addresses extracting nested values safely in KQL hunting, not the stated need for hunting malicious file activity by exact SHA-256.
Question 338
The SOC has a verified SHA-256 of a malicious script and needs all endpoints that created or modified that file. The planned solution is: Query Defender XDR DeviceFileEvents for the confirmed SHA256 and relevant file actions. Which operational step implements the chosen approach?
- Filter Advanced Hunting data for relevant indicators and affected time range while preserving device and identity attribution.
- Start from the confirmed entity and expand connected nodes with their underlying event and time-window context.
- Filter the supported SHA256 field and project DeviceId, Timestamp, FolderPath and ActionType.
- Add verified device and identity relationships from hunting results and avoid including unobserved inferred links.
Explanation
Correct Answer
C:Hash-based matching avoids relying on changeable filenames.
Incorrect Answers
A:An indicator should be paired with observed local activity. The scenario calls for hunting malicious file activity by exact SHA-256, not that separate action.
B:An account adjacency is a lead, not automatically proof of compromise. That addresses traversing validated entity relationships in Sentinel Graph, not the stated need for hunting malicious file activity by exact SHA-256.
D:The graph should represent actual entity evidence, not every same-subnet device. It does not establish hunting malicious file activity by exact SHA-256, which is the specific issue in this case.
Question 339
The SOC has a verified SHA-256 of a malicious script and needs all endpoints that created or modified that file. The deployed approach is: Query Defender XDR DeviceFileEvents for the confirmed SHA256 and relevant file actions. What outcome would best validate the implementation?
- Compare a returned file hash and device action with an endpoint investigation sample.
- Verify the initiating process, network destination and execution timing align on the affected endpoint.
- Check that the success follows failures for the same account and destination and corroborate the source device.
- Verify joined message identifiers and recipients against one known delivery in email investigation tools.
Explanation
Correct Answer
A:A hash hit needs context to decide whether the file executed.
Incorrect Answers
B:A co-occurring device connection is not proof the target process initiated it. That is relevant to correlating process launches with endpoint network connections, whereas this requirement concerns hunting malicious file activity by exact SHA-256.
C:Without correlation, benign failures and a separate success may look like one attack. It does not establish hunting malicious file activity by exact SHA-256, which is the specific issue in this case.
D:An incorrect join can manufacture apparently widespread exposure. The scenario calls for hunting malicious file activity by exact SHA-256, not that separate action.
Question 340
The SOC has a verified SHA-256 of a malicious script and needs all endpoints that created or modified that file. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Revalidate table schemas and selected columns after changes to Defender email telemetry.
- Review query assumptions when sensor fields or attack command-line obfuscation patterns change.
- Update the IOC inventory when a new script hash or false-positive exception is confirmed.
- Review approved software polling intervals and network-event field availability as exclusions evolve.
Explanation
Correct Answer
C:Attackers can change content without changing script function.
Incorrect Answers
A:Queries depending on retired fields can silently lose coverage. That is relevant to joining Defender XDR email and attachment evidence, whereas this requirement concerns hunting malicious file activity by exact SHA-256.
B:A stale string filter may stop seeing the technique. It does not establish hunting malicious file activity by exact SHA-256, which is the specific issue in this case.
D:Normal updaters can resemble C2 beacons. That addresses detecting possible endpoint beaconing patterns, not the stated need for hunting malicious file activity by exact SHA-256.
Microsoft Security Operations Analyst (SC-200) Practice Tests