100% Latest & Updated Microsoft SC-200 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 100
A security team must bring Azure subscription administrative operations into Sentinel for investigation. The control is active. Which ongoing control best addresses the risk that the protection may become ineffective?
- Monitor AMA extension and DCR associations when virtual machines are rebuilt.
- Check collector subscription status and adapt detections that still query SecurityEvent.
- Review connector enrollment whenever new subscriptions are created or moved.
- Check Linux syslog daemon forwarding and AMA health after operating-system updates.
Explanation
Correct Answer
C:New subscriptions may otherwise lack investigation coverage.
Incorrect Answers
A:Unassociated VMs stop sending events without changing detector configuration. That is relevant to collecting Windows SecurityEvent telemetry via AMA, whereas this requirement concerns collecting Azure subscription Activity log events.
B:Built-in rules expecting SecurityEvent will miss forwarded events stored only in WindowsEvent. It does not establish collecting Azure subscription Activity log events, 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 collecting Azure subscription Activity log events.
Question 101
A storage engineer wants high-value resource diagnostic logs rather than only Azure subscription Activity records. 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.
- Configure an appropriate threat intelligence ingestion connector and indicator source in Microsoft Sentinel.
- Configure Azure resource diagnostic settings to send selected log categories to the intended Log Analytics workspace.
- Create a supported custom Log Analytics table and an ingestion mapping for the appliance JSON.
Explanation
Correct Answer
C:Resource diagnostics can include data-plane information not represented in Activity logs.
Incorrect Answers
A:Selective collection reduces volume without indiscriminately dropping high-value events. It does not establish collecting Azure resource diagnostic categories, which is the specific issue in this case.
B:Indicators extend detections with external suspicious IP, domain or file intelligence. The scenario calls for collecting Azure resource diagnostic categories, not that separate action.
D:Custom tables preserve source-specific fields needed for subsequent analysis. That is relevant to storing proprietary security events in a custom log table, whereas this requirement concerns collecting Azure resource diagnostic categories.
Question 102
A storage engineer wants high-value resource diagnostic logs rather than only Azure subscription Activity records. The team has selected: Configure Azure resource diagnostic settings to send selected log categories to the intended Log Analytics workspace. Which operational step implements the chosen approach?
- Enable the specific resource log categories and choose the Sentinel-connected workspace destination.
- Configure the required policy assignment and connector onboarding for the intended subscriptions.
- Renew the credential or consent in the connector and verify scopes match the log source.
- Authorize the indicator feed and ensure the expected indicator format and expiry fields are mapped.
Explanation
Correct Answer
A:The source controls which diagnostic event categories are emitted.
Incorrect Answers
B:The subscription must be included in the desired collection scope. That addresses collecting Azure subscription Activity log events, not the stated need for collecting Azure resource diagnostic categories.
C:The connector must be able to authenticate to the intended source. That is relevant to restoring authenticated connector ingestion, whereas this requirement concerns collecting Azure resource diagnostic categories.
D:Mappings prevent stale or misclassified intelligence from polluting detections. It does not establish collecting Azure resource diagnostic categories, which is the specific issue in this case.
Question 103
A storage engineer wants high-value resource diagnostic logs rather than only Azure subscription Activity records. The team implements: Configure Azure resource diagnostic settings to send selected log categories to the intended Log Analytics workspace. What outcome would best validate the implementation?
- Perform a test resource change and find the expected entry in AzureActivity.
- Find a known benign test indicator in the workspace threat intelligence data.
- Generate a representative resource event and verify it reaches the appropriate destination table.
- Send a vendor test alert and verify its parsed fields appear in CommonSecurityLog.
Explanation
Correct Answer
C:End-to-end validation separates diagnostic setting errors from rule logic.
Incorrect Answers
A:A targeted change proves the connector captures the required operation. That addresses collecting Azure subscription Activity log events, not the stated need for collecting Azure resource diagnostic categories.
B:A controlled indicator confirms authorized ingestion and parsed fields. That is relevant to ingesting external threat intelligence indicators, whereas this requirement concerns collecting Azure resource diagnostic categories.
D:Parsing and field attribution matter more than receipt of unstructured Syslog alone. The scenario calls for collecting Azure resource diagnostic categories, not that separate action.
Question 104
A storage engineer wants high-value resource diagnostic logs rather than only Azure subscription Activity records. The setting is now in production. Which ongoing control best addresses the risk that the protection may become ineffective?
- Monitor custom schema drift when the appliance firmware is upgraded.
- Monitor diagnostic settings after resource recreation or region migration.
- Alert on connector ingestion gaps and plan credential rotation ahead of expiration.
- Revisit DCR event filters when new analytics templates are deployed.
Explanation
Correct Answer
B:Replacement resources may not inherit the previous logging configuration.
Incorrect Answers
A:New field types can cause silent loss or ingestion failures. That is relevant to storing proprietary security events in a custom log table, whereas this requirement concerns collecting Azure resource diagnostic categories.
C:Authentication failures can otherwise leave quiet periods in security telemetry. The scenario calls for collecting Azure resource diagnostic categories, not that separate action.
D:New templates may depend on previously uncollected events. That addresses filtering Windows security event sets deliberately, not the stated need for collecting Azure resource diagnostic categories.
Question 105
A SOC must receive threat indicators from an authorized threat intelligence platform for use in Sentinel correlation. 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.
- Configure an appropriate threat intelligence ingestion connector and indicator source in Microsoft Sentinel.
- Adapt affected rules for WindowsEvent or use the Windows Security Events via AMA connector where SecurityEvent is required.
- Create a supported custom Log Analytics table and an ingestion mapping for the appliance JSON.
Explanation
Correct Answer
B:Indicators extend detections with external suspicious IP, domain or file intelligence.
Incorrect Answers
A:Selective collection reduces volume without indiscriminately dropping high-value events. It does not establish ingesting external threat intelligence indicators, which is the specific issue in this case.
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 ingesting external threat intelligence indicators.
D:Custom tables preserve source-specific fields needed for subsequent analysis. That is relevant to storing proprietary security events in a custom log table, whereas this requirement concerns ingesting external threat intelligence indicators.
Question 106
A SOC must receive threat indicators from an authorized threat intelligence platform for use in Sentinel correlation. The project chooses: Configure an appropriate threat intelligence ingestion connector and indicator source in Microsoft Sentinel. Which operational step implements the chosen approach?
- 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.
- Renew the credential or consent in the connector and verify scopes match the log source.
- Map required analytics event IDs to the chosen DCR filters and pilot the change.
Explanation
Correct Answer
A:Mappings prevent stale or misclassified intelligence from polluting detections.
Incorrect Answers
B:The schema must map real incoming JSON fields to appropriate column types. That addresses storing proprietary security events in a custom log table, not the stated need for ingesting external threat intelligence indicators.
C:The connector must be able to authenticate to the intended source. That is relevant to restoring authenticated connector ingestion, whereas this requirement concerns ingesting external threat intelligence indicators.
D:Event IDs used by rules must remain part of the collected set. It does not establish ingesting external threat intelligence indicators, which is the specific issue in this case.
Question 107
A SOC must receive threat indicators from an authorized threat intelligence platform for use in Sentinel correlation. The intended configuration is: Configure an appropriate threat intelligence ingestion connector and indicator source in Microsoft Sentinel. What outcome would best validate the implementation?
- Replay a matching forwarded event and verify the modified rule now produces the expected detection.
- Find a known benign test indicator in the workspace threat intelligence data.
- Check connector health and confirm new event timestamps appear in its destination table.
- Measure the delay distribution over normal and peak load before tuning analytics lookback.
Explanation
Correct Answer
B:A controlled indicator confirms authorized ingestion and parsed fields.
Incorrect Answers
A:Real rule execution proves the table mapping repair. That addresses repairing table-specific Windows forwarded detection coverage, not the stated need for ingesting external threat intelligence indicators.
C:Old historical rows alone do not prove ingestion resumed. It does not establish ingesting external threat intelligence indicators, which is the specific issue in this case.
D:Delay quantiles reveal how much late-arriving data may be missed. The scenario calls for ingesting external threat intelligence indicators, not that separate action.
Question 108
A SOC must receive threat indicators from an authorized threat intelligence platform for use in Sentinel correlation. After rollout, the organization wants continuing assurance. Which ongoing control best addresses the risk that the protection may become ineffective?
- Check collector subscription status and adapt detections that still query SecurityEvent.
- Monitor ingestion delay percentiles after connector or API changes.
- Alert on connector ingestion gaps and plan credential rotation ahead of expiration.
- Enforce indicator expiration and remove feeds that repeatedly deliver stale data.
Explanation
Correct Answer
D:Outdated indicators inflate false-positive correlations.
Incorrect Answers
A:Built-in rules expecting SecurityEvent will miss forwarded events stored only in WindowsEvent. That is relevant to ingesting forwarded Windows events through a collector, whereas this requirement concerns ingesting external threat intelligence indicators.
B:Growth in ingestion lag may cause seemingly healthy rules to miss incidents. It does not establish ingesting external threat intelligence indicators, which is the specific issue in this case.
C:Authentication failures can otherwise leave quiet periods in security telemetry. The scenario calls for ingesting external threat intelligence indicators, not that separate action.
Question 109
A proprietary appliance emits JSON audit events that are not covered by a built-in Sentinel table. What should the administrator configure to address this exact situation?
- Configure an appropriate threat intelligence ingestion connector and indicator source in Microsoft Sentinel.
- Create a supported custom Log Analytics table and an ingestion mapping for the appliance JSON.
- Use an AMA DCR event selection strategy aligned to detector requirements rather than collecting every security event.
- Enable the specific resource log categories and choose the Sentinel-connected workspace destination.
Explanation
Correct Answer
B:Custom tables preserve source-specific fields needed for subsequent analysis.
Incorrect Answers
A:Indicators extend detections with external suspicious IP, domain or file intelligence. It does not establish storing proprietary security events in a custom log table, which is the specific issue in this case.
C:Selective collection reduces volume without indiscriminately dropping high-value events. That addresses filtering Windows security event sets deliberately, not the stated need for storing proprietary security events in a custom log table.
D:The source controls which diagnostic event categories are emitted. That is relevant to collecting Azure resource diagnostic categories, whereas this requirement concerns storing proprietary security events in a custom log table.
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.
Microsoft Security Operations Analyst (SC-200) Practice Tests