100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 110
A proprietary appliance emits JSON audit events that are not covered by a built-in Sentinel table. The proposed configuration is: Create a supported custom Log Analytics table and an ingestion mapping for the appliance JSON. Which operational step implements the chosen approach?
- Map required analytics event IDs to the chosen DCR filters and pilot the change.
- Enable the specific resource log categories and choose the Sentinel-connected workspace destination.
- Define the schema and configure a supported collection pipeline or DCR transformation.
- Authorize the indicator feed and ensure the expected indicator format and expiry fields are mapped.
Explanation
Correct Answer
C:The schema must map real incoming JSON fields to appropriate column types.
Incorrect Answers
A:Event IDs used by rules must remain part of the collected set. The scenario calls for storing proprietary security events in a custom log table, not that separate action.
B:The source controls which diagnostic event categories are emitted. That addresses collecting Azure resource diagnostic categories, not the stated need for storing proprietary security events in a custom log table.
D:Mappings prevent stale or misclassified intelligence from polluting detections. It does not establish storing proprietary security events in a custom log table, which is the specific issue in this case.
Question 111
A proprietary appliance emits JSON audit events that are not covered by a built-in Sentinel table. The security team selected: Create a supported custom Log Analytics table and an ingestion mapping for the appliance JSON. Which TWO actions together implement this solution and verify the desired outcome? Choose TWO.
- Enable the specific resource log categories and choose the Sentinel-connected workspace destination.
- Define the schema and configure a supported collection pipeline or DCR transformation.
- Submit representative sample events and query the custom table for expected typed fields.
- Configure Azure resource diagnostic settings to send selected log categories to the intended Log Analytics workspace.
- Measure the delay distribution over normal and peak load before tuning analytics lookback.
Explanation
Correct Answers
B:The schema must map real incoming JSON fields to appropriate column types.
C:The test catches incorrect parsing or transformation.
Incorrect Answers
A:The source controls which diagnostic event categories are emitted. That addresses collecting Azure resource diagnostic categories, not the stated need for storing proprietary security events in a custom log table.
D:Resource diagnostics can include data-plane information not represented in Activity logs. The scenario calls for storing proprietary security events in a custom log table, not that separate action.
E:Delay quantiles reveal how much late-arriving data may be missed. That addresses distinguishing source event time from ingestion time, not the stated need for storing proprietary security events in a custom log table.
Question 112
A proprietary appliance emits JSON audit events that are not covered by a built-in Sentinel table. The control has been deployed. Which ongoing control best addresses the risk that the protection may become ineffective?
- Review connector enrollment whenever new subscriptions are created or moved.
- Alert on connector ingestion gaps and plan credential rotation ahead of expiration.
- Monitor parser failures and device firmware changes that modify CEF extensions.
- Monitor custom schema drift when the appliance firmware is upgraded.
Explanation
Correct Answer
D:New field types can cause silent loss or ingestion failures.
Incorrect Answers
A:New subscriptions may otherwise lack investigation coverage. That is relevant to collecting Azure subscription Activity log events, whereas this requirement concerns storing proprietary security events in a custom log table.
B:Authentication failures can otherwise leave quiet periods in security telemetry. It does not establish storing proprietary security events in a custom log table, which is the specific issue in this case.
C:Vendor format drift can break detection field mappings. The scenario calls for storing proprietary security events in a custom log table, not that separate action.
Question 113
A security engineer has to reduce collected Windows event volume while retaining the event IDs used by critical detection rules. What should the administrator configure to address this exact situation?
- Use an AMA DCR event selection strategy aligned to detector requirements rather than collecting every security event.
- Create a supported custom Log Analytics table and an ingestion mapping for the appliance JSON.
- Adapt affected rules for WindowsEvent or use the Windows Security Events via AMA connector where SecurityEvent is required.
- Document the difference between TimeGenerated and ingestion_time() for the collected events.
Explanation
Correct Answer
A:Selective collection reduces volume without indiscriminately dropping high-value events.
Incorrect Answers
B:Custom tables preserve source-specific fields needed for subsequent analysis. The scenario calls for filtering Windows security event sets deliberately, not that separate action.
C:Detection queries must use the actual table populated by the chosen connector. That addresses repairing table-specific Windows forwarded detection coverage, not the stated need for filtering Windows security event sets deliberately.
D:Source and ingestion timestamps answer different questions about event freshness. That is relevant to distinguishing source event time from ingestion time, whereas this requirement concerns filtering Windows security event sets deliberately.
Question 114
A security engineer has to reduce collected Windows event volume while retaining the event IDs used by critical detection rules. The control design uses: Use an AMA DCR event selection strategy aligned to detector requirements rather than collecting every security event. Which operational step implements the chosen approach?
- Inspect the rule query table reference and the actual collection path before changing either.
- Renew the credential or consent in the connector and verify scopes match the log source.
- Compare sample TimeGenerated values with ingestion_time() to measure pipeline latency.
- Map required analytics event IDs to the chosen DCR filters and pilot the change.
Explanation
Correct Answer
D:Event IDs used by rules must remain part of the collected set.
Incorrect Answers
A:Correct diagnosis avoids unnecessary relaying or ingestion duplication. The scenario calls for filtering Windows security event sets deliberately, not that separate action.
B:The connector must be able to authenticate to the intended source. That addresses restoring authenticated connector ingestion, not the stated need for filtering Windows security event sets deliberately.
C:Observed lag helps set appropriate detection scheduling windows. That is relevant to distinguishing source event time from ingestion time, whereas this requirement concerns filtering Windows security event sets deliberately.
Question 115
A security engineer has to reduce collected Windows event volume while retaining the event IDs used by critical detection rules. The control being evaluated is: Use an AMA DCR event selection strategy aligned to detector requirements rather than collecting every security event. What outcome would best validate the implementation?
- Generate a representative resource event and verify it reaches the appropriate destination table.
- Perform a test resource change and find the expected entry in AzureActivity.
- Find a known benign test indicator in the workspace threat intelligence data.
- Compare detection-required EventIDs before and after the new DCR filter in SecurityEvent.
Explanation
Correct Answer
D:The comparison identifies loss of critical evidence.
Incorrect Answers
A:End-to-end validation separates diagnostic setting errors from rule logic. That addresses collecting Azure resource diagnostic categories, not the stated need for filtering Windows security event sets deliberately.
B:A targeted change proves the connector captures the required operation. That is relevant to collecting Azure subscription Activity log events, whereas this requirement concerns filtering Windows security event sets deliberately.
C:A controlled indicator confirms authorized ingestion and parsed fields. It does not establish filtering Windows security event sets deliberately, which is the specific issue in this case.
Question 116
A security engineer has to reduce collected Windows event volume while retaining the event IDs used by critical detection rules. Six months after deployment, the system has changed. Which ongoing control best addresses the risk that the protection may become ineffective?
- Maintain a table mapping inventory when switching between WEF and direct AMA collection.
- Revisit DCR event filters when new analytics templates are deployed.
- Monitor ingestion delay percentiles after connector or API changes.
- Alert on connector ingestion gaps and plan credential rotation ahead of expiration.
Explanation
Correct Answer
B:New templates may depend on previously uncollected events.
Incorrect Answers
A:Collector changes can invalidate many dependent analytics rules. That is relevant to repairing table-specific Windows forwarded detection coverage, whereas this requirement concerns filtering Windows security event sets deliberately.
C:Growth in ingestion lag may cause seemingly healthy rules to miss incidents. The scenario calls for filtering Windows security event sets deliberately, not that separate action.
D:Authentication failures can otherwise leave quiet periods in security telemetry. That addresses restoring authenticated connector ingestion, not the stated need for filtering Windows security event sets deliberately.
Question 117
A Windows Event Forwarding deployment sends events into WindowsEvent, but legacy Sentinel rules query SecurityEvent and show no matches. What should the administrator configure to address this exact situation?
- Adapt affected rules for WindowsEvent or use the Windows Security Events via AMA connector where SecurityEvent is required.
- Update or rotate the connector authorization with the supported identity mechanism.
- Deploy the Common Event Format via AMA connector with a supported Linux forwarding collector.
- Document the difference between TimeGenerated and ingestion_time() for the collected events.
Explanation
Correct Answer
A:Detection queries must use the actual table populated by the chosen connector.
Incorrect Answers
B:A credential failure blocks ingestion even when event production continues. The scenario calls for repairing table-specific Windows forwarded detection coverage, not that separate action.
C:CEF provides normalized fields for compatible vendor security logs. That addresses ingesting third-party firewall CEF records, not the stated need for repairing table-specific Windows forwarded detection coverage.
D:Source and ingestion timestamps answer different questions about event freshness. That is relevant to distinguishing source event time from ingestion time, whereas this requirement concerns repairing table-specific Windows forwarded detection coverage.
Question 118
A Windows Event Forwarding deployment sends events into WindowsEvent, but legacy Sentinel rules query SecurityEvent and show no matches. The planned solution is: Adapt affected rules for WindowsEvent or use the Windows Security Events via AMA connector where SecurityEvent is required. Which operational step implements the chosen approach?
- Enable the specific resource log categories and choose the Sentinel-connected workspace destination.
- Authorize the indicator feed and ensure the expected indicator format and expiry fields are mapped.
- Define the schema and configure a supported collection pipeline or DCR transformation.
- Inspect the rule query table reference and the actual collection path before changing either.
Explanation
Correct Answer
D:Correct diagnosis avoids unnecessary relaying or ingestion duplication.
Incorrect Answers
A:The source controls which diagnostic event categories are emitted. The scenario calls for repairing table-specific Windows forwarded detection coverage, not that separate action.
B:Mappings prevent stale or misclassified intelligence from polluting detections. That addresses ingesting external threat intelligence indicators, not the stated need for repairing table-specific Windows forwarded detection coverage.
C:The schema must map real incoming JSON fields to appropriate column types. That is relevant to storing proprietary security events in a custom log table, whereas this requirement concerns repairing table-specific Windows forwarded detection coverage.
Question 119
A Windows Event Forwarding deployment sends events into WindowsEvent, but legacy Sentinel rules query SecurityEvent and show no matches. The deployed approach is: Adapt affected rules for WindowsEvent or use the Windows Security Events via AMA connector where SecurityEvent is required. What outcome would best validate the implementation?
- Find a known benign test indicator in the workspace threat intelligence data.
- Submit representative sample events and query the custom table for expected typed fields.
- Compare detection-required EventIDs before and after the new DCR filter in SecurityEvent.
- Replay a matching forwarded event and verify the modified rule now produces the expected detection.
Explanation
Correct Answer
D:Real rule execution proves the table mapping repair.
Incorrect Answers
A:A controlled indicator confirms authorized ingestion and parsed fields. That addresses ingesting external threat intelligence indicators, not the stated need for repairing table-specific Windows forwarded detection coverage.
B:The test catches incorrect parsing or transformation. That is relevant to storing proprietary security events in a custom log table, whereas this requirement concerns repairing table-specific Windows forwarded detection coverage.
C:The comparison identifies loss of critical evidence. It does not establish repairing table-specific Windows forwarded detection coverage, which is the specific issue in this case.
Question 120
A Windows Event Forwarding deployment sends events into WindowsEvent, but legacy Sentinel rules query SecurityEvent and show no matches. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Monitor ingestion delay percentiles after connector or API changes.
- Alert on connector ingestion gaps and plan credential rotation ahead of expiration.
- Maintain a table mapping inventory when switching between WEF and direct AMA collection.
- Check Linux syslog daemon forwarding and AMA health after operating-system updates.
Explanation
Correct Answer
C:Collector changes can invalidate many dependent analytics rules.
Incorrect Answers
A:Growth in ingestion lag may cause seemingly healthy rules to miss incidents. That is relevant to distinguishing source event time from ingestion time, whereas this requirement concerns repairing table-specific Windows forwarded detection coverage.
B:Authentication failures can otherwise leave quiet periods in security telemetry. It does not establish repairing table-specific Windows forwarded detection coverage, which is the specific issue in this case.
D:Local daemon configuration can break ingestion despite a valid workspace. That addresses collecting Linux Syslog using AMA, not the stated need for repairing table-specific Windows forwarded detection coverage.
Microsoft Security Operations Analyst (SC-200) Practice Tests