100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 320
A department mailbox unexpectedly grants another employee Full Access permission shortly after a suspected attacker sign-in. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Audit eDiscovery case access and preserve documented query parameters for repeatability.
- Monitor future mailbox permission changes and require approval for privileged delegation.
- Check audit ingestion delay and policy retention before concluding no additional downloads occurred.
- Monitor graph API call-rate spikes and connector health after application onboarding.
Explanation
Correct Answer
B:Unreviewed grants can silently re-open mail access.
Incorrect Answers
A:Case discovery must remain defensible and least privileged. That is relevant to locating Microsoft 365 evidence through Purview eDiscovery content search, whereas this requirement concerns tracing mailbox delegation and permission changes.
C:Late-arriving or expired events can make an investigation incomplete. The scenario calls for tracing mailbox delegation and permission changes, not that separate action.
D:A silent activity feed can hide renewed automated exfiltration. That addresses investigating Microsoft Graph activity logs for API access, not the stated need for tracing mailbox delegation and permission changes.
Question 321
A hunter needs to identify suspicious encoded PowerShell commands launched by Word across managed Windows devices during the last day. What should the administrator configure to address this exact situation?
- Use supported Defender XDR hunting graph or incident entity relationships to visualize the observed blast radius.
- 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.
- Query Defender XDR Advanced Hunting DeviceProcessEvents for Office-spawned PowerShell with suspect command-line indicators.
Explanation
Correct Answer
D:Process event data includes the executable and relevant process-parent context for this hunt.
Incorrect Answers
A:A graph can expose connections that are hard to follow in separate tables. It does not establish hunting suspicious process command lines in Defender XDR, 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 suspicious process command lines in Defender XDR, not that separate action.
C:Graph relationships help scope threat hunting across heterogeneous security data. That addresses traversing validated entity relationships in Sentinel Graph, not the stated need for hunting suspicious process command lines in Defender XDR.
Question 322
A hunter needs to identify suspicious encoded PowerShell commands launched by Word across managed Windows devices during the last day. The team has selected: Query Defender XDR Advanced Hunting DeviceProcessEvents for Office-spawned PowerShell with suspect command-line indicators. Which operational step implements the chosen approach?
- Filter the exact tool indicator and group by the one-hour time bin before counting distinct DeviceIds.
- Join relevant process and network records on DeviceId and available process identity plus constrained timestamps.
- Parse the AdditionalFields value, inspect its keys and convert selected nested properties to the required types.
- Filter by Timestamp and FileName, inspect ProcessCommandLine and initiating process fields, and project the device identifiers.
Explanation
Correct Answer
D:A targeted query avoids confusing all PowerShell execution with malicious activity.
Incorrect Answers
A:The grouping should represent affected devices per interval, not event total. The scenario calls for hunting suspicious process command lines in Defender XDR, not that separate action.
B: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 suspicious process command lines in Defender XDR.
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 suspicious process command lines in Defender XDR.
Question 323
A hunter needs to identify suspicious encoded PowerShell commands launched by Word across managed Windows devices during the last day. The team implements: Query Defender XDR Advanced Hunting DeviceProcessEvents for Office-spawned PowerShell with suspect command-line indicators. What outcome would best validate the implementation?
- Validate a suspected identity-to-resource edge against the relevant audit or sign-in event.
- Verify each apparent campaign match against the observed process, DNS or connection events in the tenant.
- Cross-check graph edges against source event IDs and timestamps from the investigation.
- Correlate a matching process event with its device timeline and parent Office process to verify actual execution.
Explanation
Correct Answer
D:A string match alone may include harmless scheduled administration.
Incorrect Answers
A:Every escalated graph link should be supported by an actual record. That addresses traversing validated entity relationships in Sentinel Graph, not the stated need for hunting suspicious process command lines in Defender XDR.
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 suspicious process command lines in Defender XDR.
C:A visually connected graph can still contain a false match. It does not establish hunting suspicious process command lines in Defender XDR, which is the specific issue in this case.
Question 324
A hunter needs to identify suspicious encoded PowerShell commands launched by Word across managed Windows devices during the last day. The setting is now in production. 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 time-bin definitions and field availability after alert scheduling changes.
- Refresh indicator intelligence as campaigns rotate infrastructure and retire stale indicators.
- Monitor changes in event JSON property names and guard the query against missing fields.
Explanation
Correct Answer
A:A stale string filter may stop seeing the technique.
Incorrect Answers
B:Inconsistent windows can distort trends across weeks. It does not establish hunting suspicious process command lines in Defender XDR, which is the specific issue in this case.
C:A static indicator can outlive the associated attack campaign. The scenario calls for hunting suspicious process command lines in Defender XDR, not that separate action.
D:Optional nested attributes can disappear after sensor updates. That addresses extracting nested values safely in KQL hunting, not the stated need for hunting suspicious process command lines in Defender XDR.
Question 325
Multiple workstations appear to contact the same uncommon external destination at almost regular intervals overnight. What should the administrator configure to address this exact situation?
- Use Defender threat analytics campaign context to construct evidence-based hunting pivots for tenant indicators.
- Use DeviceNetworkEvents and time-window aggregations to investigate repeated outbound connection periodicity.
- Use KQL summarize dcount(DeviceId) with bin(Timestamp, 1h) on the targeted process events.
- Use supported Defender XDR hunting graph or incident entity relationships to visualize the observed blast radius.
Explanation
Correct Answer
B:Network event timing can distinguish potential command-and-control beacons from normal browsing.
Incorrect Answers
A:Published campaign descriptions help scope a hunt but do not prove local compromise. It does not establish detecting possible endpoint beaconing patterns, which is the specific issue in this case.
C:Distinct-device aggregation avoids inflating impact from repeated launches on one host. That addresses counting distinct affected devices in time windows, not the stated need for detecting possible endpoint beaconing patterns.
D:A graph can expose connections that are hard to follow in separate tables. That is relevant to creating a blast-radius hunting graph from observed entities, whereas this requirement concerns detecting possible endpoint beaconing patterns.
Question 326
Multiple workstations appear to contact the same uncommon external destination at almost regular intervals overnight. The project chooses: Use DeviceNetworkEvents and time-window aggregations to investigate repeated outbound connection periodicity. Which operational step implements the chosen approach?
- Filter the exact tool indicator and group by the one-hour time bin before counting distinct DeviceIds.
- Parse the AdditionalFields value, inspect its keys and convert selected nested properties to the required types.
- Group observed device-destination pairs into time bins and compare intervals while excluding documented services.
- Filter Advanced Hunting data for relevant indicators and affected time range while preserving device and identity attribution.
Explanation
Correct Answer
C:Consistent periodicity should be assessed per device and remote endpoint.
Incorrect Answers
A:The grouping should represent affected devices per interval, not event total. The scenario calls for detecting possible endpoint beaconing patterns, not that separate action.
B:Schema inspection prevents treating all dynamic values as strings. That addresses extracting nested values safely in KQL hunting, not the stated need for detecting possible endpoint beaconing patterns.
D:An indicator should be paired with observed local activity. It does not establish detecting possible endpoint beaconing patterns, which is the specific issue in this case.
Question 327
Multiple workstations appear to contact the same uncommon external destination at almost regular intervals overnight. The intended configuration is: Use DeviceNetworkEvents and time-window aggregations to investigate repeated outbound connection periodicity. What outcome would best validate the implementation?
- 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.
- Check that the success follows failures for the same account and destination and corroborate the source device.
- Correlate a matching process event with its device timeline and parent Office process to verify actual execution.
Explanation
Correct Answer
A:Periodic traffic alone is not proof of a malicious beacon.
Incorrect Answers
B:An incorrect join can manufacture apparently widespread exposure. That is relevant to joining Defender XDR email and attachment evidence, whereas this requirement concerns detecting possible endpoint beaconing patterns.
C:Without correlation, benign failures and a separate success may look like one attack. It does not establish detecting possible endpoint beaconing patterns, which is the specific issue in this case.
D:A string match alone may include harmless scheduled administration. The scenario calls for detecting possible endpoint beaconing patterns, not that separate action.
Question 328
Multiple workstations appear to contact the same uncommon external destination at almost regular intervals overnight. After rollout, the organization wants continuing assurance. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review approved software polling intervals and network-event field availability as exclusions evolve.
- Refresh indicator intelligence as campaigns rotate infrastructure and retire stale indicators.
- 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.
Explanation
Correct Answer
A:Normal updaters can resemble C2 beacons.
Incorrect Answers
B:A static indicator can outlive the associated attack campaign. It does not establish detecting possible endpoint beaconing patterns, which is the specific issue in this case.
C:Inconsistent windows can distort trends across weeks. The scenario calls for detecting possible endpoint beaconing patterns, not that separate action.
D:Optional nested attributes can disappear after sensor updates. That addresses extracting nested values safely in KQL hunting, not the stated need for detecting possible endpoint beaconing patterns.
Question 329
A malicious attachment campaign delivered the same document name with different hashes to dozens of mailboxes. What should the administrator configure to address this exact situation?
- Use KQL parse_json() with appropriate dynamic field access for supported structured event details.
- Correlate DeviceProcessEvents and DeviceNetworkEvents using device and suitable process identifiers.
- Query Defender XDR DeviceFileEvents for the confirmed SHA256 and relevant file actions.
- Join the appropriate Advanced Hunting EmailEvents and EmailAttachmentInfo on their common message identifier.
Explanation
Correct Answer
D:A message-to-attachment join reveals campaign attachment properties alongside recipients.
Incorrect Answers
A:Nested properties must be explicitly decoded before reliable filtering. It does not establish joining Defender XDR email and attachment evidence, 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 joining Defender XDR email and attachment evidence, not that separate action.
C:File event records can locate devices where the same content was written or modified. That addresses hunting malicious file activity by exact SHA-256, not the stated need for joining Defender XDR email and attachment evidence.
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.
Microsoft Security Operations Analyst (SC-200) Practice Tests