100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 130
A defender team must alert when a signed administrative utility unexpectedly spawns a credential-dumping tool on endpoints. The proposed configuration is: Create a Microsoft Defender XDR custom detection using an Advanced Hunting query over process events. Which operational step implements the chosen approach?
- Project the required account or host columns and map them to supported entity identifiers in the rule.
- Write the query on DeviceProcessEvents with explicit initiating process, file and timing predicates.
- Measure pipeline delay then configure frequency, lookback and overlap to account for delayed events.
- Choose an appropriate grouping window and related-entity criteria in the rule.
Explanation
Correct Answer
B:The query must identify the suspicious process chain and the affected device.
Incorrect Answers
A:Without compatible query fields the mapping cannot resolve reliably. The scenario calls for creating targeted Defender XDR advanced hunting detections, not that separate action.
C:Proper windows reduce both missed data and repeated detections. That is relevant to correcting analytics rules for ingestion delay, whereas this requirement concerns creating targeted Defender XDR advanced hunting detections.
D:Grouping should follow incident semantics rather than arbitrarily merging all tenants. It does not establish creating targeted Defender XDR advanced hunting detections, which is the specific issue in this case.
Question 131
A defender team must alert when a signed administrative utility unexpectedly spawns a credential-dumping tool on endpoints. The security team selected: Create a Microsoft Defender XDR custom detection using an Advanced Hunting query over process events. What outcome would best validate the implementation?
- Generate a permitted synthetic indicator match and confirm the alert includes the matching network entity.
- Compare a known asset's criticality in the resulting alert with the source watchlist row.
- Run controlled process-event tests and verify both the query match and generated custom alert.
- Replay a delayed event and ensure the scheduled rule still generates the expected alert.
Explanation
Correct Answer
C:A hunt result alone does not prove a configured detection fires.
Incorrect Answers
A:A test proves normalization and correlation work end-to-end. That addresses correlating indicators in Sentinel analytics rules, not the stated need for creating targeted Defender XDR advanced hunting detections.
B:A test reveals key normalization and join errors. That is relevant to enriching incident context using watchlists, whereas this requirement concerns creating targeted Defender XDR advanced hunting detections.
D:A backdated event exposes window gaps that interactive queries hide. The scenario calls for creating targeted Defender XDR advanced hunting detections, not that separate action.
Question 132
A defender team must alert when a signed administrative utility unexpectedly spawns a credential-dumping tool on endpoints. The control has been deployed. Which ongoing control best addresses the risk that the protection may become ineffective?
- Retest mapped columns after query refactors or source schema changes.
- Track future latency changes and revalidate the rule when a connector is replaced.
- Review false positives when the approved administration tool is updated.
- Audit incident grouping after rules gain new entities or customer scopes.
Explanation
Correct Answer
C:Legitimate tooling changes can affect process-chain detection fidelity.
Incorrect Answers
A:Renaming a projected column can silently remove investigation context. That is relevant to enriching Sentinel analytics rule entity mappings, whereas this requirement concerns creating targeted Defender XDR advanced hunting detections.
B:Connector changes can invalidate time assumptions. It does not establish creating targeted Defender XDR advanced hunting detections, which is the specific issue in this case.
D:Changed correlations can reduce signal visibility. That addresses reducing duplicate incident creation without losing source evidence, not the stated need for creating targeted Defender XDR advanced hunting detections.
Question 133
An attacker may create bursty login failures followed by success across several identities and the SOC needs periodic Sentinel detection. What should the administrator configure to address this exact situation?
- Create a Microsoft Defender XDR custom detection using an Advanced Hunting query over process events.
- Use mapped Microsoft Sentinel or Defender detections and the MITRE ATT&CK coverage view to assess gaps.
- Create a scheduled Microsoft Sentinel analytics rule using a validated KQL query and threshold.
- Use applicable Microsoft Sentinel anomaly detection capabilities and suitable event baselines.
Explanation
Correct Answer
C:Scheduled rules support lookback windows and repeatable correlation logic.
Incorrect Answers
A:Endpoint process creation telemetry can reveal suspicious parent-child behavior. It does not establish detecting login bursts through scheduled analytics, which is the specific issue in this case.
B:Technique mapping exposes missing adversary behaviors beyond raw rule counts. The scenario calls for detecting login bursts through scheduled analytics, not that separate action.
D:Anomalies identify deviations that fixed thresholds may miss. That is relevant to detecting unusual activity with Sentinel anomaly signals, whereas this requirement concerns detecting login bursts through scheduled analytics.
Question 134
An attacker may create bursty login failures followed by success across several identities and the SOC needs periodic Sentinel detection. The control design uses: Create a scheduled Microsoft Sentinel analytics rule using a validated KQL query and threshold. Which operational step implements the chosen approach?
- Configure query lookback, frequency and grouping so the failed-then-success pattern is preserved.
- Write the query on DeviceProcessEvents with explicit initiating process, file and timing predicates.
- Build an NRT query that stays within supported limitations and projects required entities.
- Ingest active indicators and enable the corresponding TI rule with correct entity mappings.
Explanation
Correct Answer
A:Ingestion delay and alert grouping influence which sessions become incidents.
Incorrect Answers
B:The query must identify the suspicious process chain and the affected device. That addresses creating targeted Defender XDR advanced hunting detections, not the stated need for detecting login bursts through scheduled analytics.
C:Excessive fields or unsupported query design can make alert output unhelpful. That is relevant to using a Sentinel near-real-time analytics rule, whereas this requirement concerns detecting login bursts through scheduled analytics.
D:Detection logic requires both observed events and the indicator source. It does not establish detecting login bursts through scheduled analytics, which is the specific issue in this case.
Question 135
An attacker may create bursty login failures followed by success across several identities and the SOC needs periodic Sentinel detection. The control being evaluated is: Create a scheduled Microsoft Sentinel analytics rule using a validated KQL query and threshold. What outcome would best validate the implementation?
- Replay clustered and unrelated tests and verify the intended incident grouping.
- Run controlled process-event tests and verify both the query match and generated custom alert.
- Replay a controlled event set and confirm a Sentinel alert with the expected account entities.
- Validate the detected spike against a known legitimate surge and a synthetic suspicious surge.
Explanation
Correct Answer
C:Entity validation prevents unassigned incidents and misdirected response.
Incorrect Answers
A:The test guards against merging separate attacks into one case. That addresses reducing duplicate incident creation without losing source evidence, not the stated need for detecting login bursts through scheduled analytics.
B:A hunt result alone does not prove a configured detection fires. That is relevant to creating targeted Defender XDR advanced hunting detections, whereas this requirement concerns detecting login bursts through scheduled analytics.
D:Controls reveal whether an anomaly is actionable. The scenario calls for detecting login bursts through scheduled analytics, not that separate action.
Question 136
An attacker may create bursty login failures followed by success across several identities and the SOC needs periodic Sentinel detection. Six months after deployment, the system has changed. Which ongoing control best addresses the risk that the protection may become ineffective?
- Retest mapped columns after query refactors or source schema changes.
- Tune scheduled lookback and ingestion-lag handling after connector latency changes.
- Audit incident grouping after rules gain new entities or customer scopes.
- Refresh watchlist entries when assets are added, renamed, or retired.
Explanation
Correct Answer
B:A narrow window can miss late events even when the source is healthy.
Incorrect Answers
A:Renaming a projected column can silently remove investigation context. That is relevant to enriching Sentinel analytics rule entity mappings, whereas this requirement concerns detecting login bursts through scheduled analytics.
C:Changed correlations can reduce signal visibility. The scenario calls for detecting login bursts through scheduled analytics, not that separate action.
D:Stale asset context can misprioritize otherwise correct incidents. That addresses enriching incident context using watchlists, not the stated need for detecting login bursts through scheduled analytics.
Question 137
A high-value security table needs an alert close to ingestion time, using a supported one-minute Sentinel rule cadence. What should the administrator configure to address this exact situation?
- Use a Microsoft Sentinel watchlist with an appropriate SearchKey in the enrichment query.
- Adjust the scheduled rule query time window using known ingestion latency and supported lookback settings.
- Configure a supported Microsoft Sentinel near-real-time analytics rule for the narrowly scoped condition.
- Use mapped Microsoft Sentinel or Defender detections and the MITRE ATT&CK coverage view to assess gaps.
Explanation
Correct Answer
C:NRT rules evaluate recent ingested data at a fixed high-frequency cadence.
Incorrect Answers
A:Watchlists can join maintained business context such as criticality to event entities. It does not establish using a Sentinel near-real-time analytics rule, which is the specific issue in this case.
B:A detection must cover events even when ingestion lags event creation. The scenario calls for using a Sentinel near-real-time analytics rule, not that separate action.
D:Technique mapping exposes missing adversary behaviors beyond raw rule counts. That is relevant to assessing detection coverage against MITRE ATT&CK, whereas this requirement concerns using a Sentinel near-real-time analytics rule.
Question 138
A high-value security table needs an alert close to ingestion time, using a supported one-minute Sentinel rule cadence. The planned solution is: Configure a supported Microsoft Sentinel near-real-time analytics rule for the narrowly scoped condition. Which operational step implements the chosen approach?
- Confirm the baseline input data and evaluate the anomaly output against representative time windows.
- Ingest active indicators and enable the corresponding TI rule with correct entity mappings.
- Build an NRT query that stays within supported limitations and projects required entities.
- Map relevant analytics rules to appropriate MITRE tactics and techniques consistently.
Explanation
Correct Answer
C:Excessive fields or unsupported query design can make alert output unhelpful.
Incorrect Answers
A:Bad or sparse baseline data undermines anomaly meaning. The scenario calls for using a Sentinel near-real-time analytics rule, not that separate action.
B:Detection logic requires both observed events and the indicator source. That addresses correlating indicators in Sentinel analytics rules, not the stated need for using a Sentinel near-real-time analytics rule.
D:Incorrect tags give false confidence in coverage. It does not establish using a Sentinel near-real-time analytics rule, which is the specific issue in this case.
Question 139
A high-value security table needs an alert close to ingestion time, using a supported one-minute Sentinel rule cadence. The deployed approach is: Configure a supported Microsoft Sentinel near-real-time analytics rule for the narrowly scoped condition. What outcome would best validate the implementation?
- Compare mapped techniques against the organization's prioritized threat model and identify uncovered techniques.
- Generate a test event and confirm a timely NRT alert and mapped entities.
- Generate a permitted synthetic indicator match and confirm the alert includes the matching network entity.
- Validate the detected spike against a known legitimate surge and a synthetic suspicious surge.
Explanation
Correct Answer
B:Measured result time distinguishes fast detection from ordinary scheduled checks.
Incorrect Answers
A:Coverage must be judged against actual threats and required telemetry. That addresses assessing detection coverage against MITRE ATT&CK, not the stated need for using a Sentinel near-real-time analytics rule.
C:A test proves normalization and correlation work end-to-end. It does not establish using a Sentinel near-real-time analytics rule, which is the specific issue in this case.
D:Controls reveal whether an anomaly is actionable. The scenario calls for using a Sentinel near-real-time analytics rule, not that separate action.
Question 140
A high-value security table needs an alert close to ingestion time, using a supported one-minute Sentinel rule cadence. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Monitor indicator expiration and rule false positives when feeds change.
- Review false positives when the approved administration tool is updated.
- Monitor NRT rule health and limits when incident volume or connector delay rises.
- Tune scheduled lookback and ingestion-lag handling after connector latency changes.
Explanation
Correct Answer
C:Near-real-time detection depends on timely ingestion.
Incorrect Answers
A:Stale indicators create noise without improving threat detection. That is relevant to correlating indicators in Sentinel analytics rules, whereas this requirement concerns using a Sentinel near-real-time analytics rule.
B:Legitimate tooling changes can affect process-chain detection fidelity. It does not establish using a Sentinel near-real-time analytics rule, which is the specific issue in this case.
D:A narrow window can miss late events even when the source is healthy. That addresses detecting login bursts through scheduled analytics, not the stated need for using a Sentinel near-real-time analytics rule.
Microsoft Security Operations Analyst (SC-200) Practice Tests