Microsoft SC-200 Practice Test 95
Question 940
The original problem was: A hunter wants an asynchronous historical join across multiple low-touch event tables. The solution is operating, but the historical query becomes a recurring daily enrichment task. What should change next?
- Schedule the KQL job with approved scope and cost controls
- The completed job returns relevant historical records with a reproducible query
- Create an appropriately scoped Sentinel data-lake KQL job with confirmed retention and billing
- Run a near-real-time analytics rule directly over cold historical data
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: The historical query becomes a recurring daily enrichment task. Therefore Schedule the KQL job with approved scope and cost controls is appropriate for A hunter wants an asynchronous historical join across multiple low-touch event tables, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is The historical query becomes a recurring daily enrichment task, so the proper follow-up must address it rather than merely note The completed job returns relevant historical records with a reproducible query.
C:This was the original control already implemented: Create an appropriately scoped Sentinel data-lake KQL job with confirmed retention and billing. Its original rationale was: KQL jobs support scheduled or ad-hoc historical queries over data lake tables including joins. For the initial setting (A hunter wants an asynchronous historical join across multiple low-touch event tables), that does not itself meet the new condition: The historical query becomes a recurring daily enrichment task.
D:This was already unsuitable under the original condition because real-time analytics rules are not the general query path for lake-only historical tables. It also fails after the change affecting A hunter wants an asynchronous historical join across multiple low-touch event tables.
Question 941
A SOC wants retrospective TI scans against a year of retained archive data. Which configuration or investigation step is MOST appropriate?
- Use a governed Sentinel data-lake KQL job for historical indicator matching
- Increase an NRT analytics rule's time window to scan a year of cold telemetry
- Build an approved scheduled job and document data-scan costs
- Deploy supported ASR rules first in audit mode and review impact before enforcement
Explanation
Correct Answer
A:Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data. The selected action is: Use a governed Sentinel data-lake KQL job for historical indicator matching.
Incorrect Answers
B:NRT detection is not a supported substitute for historical lake jobs. The shortcut Increase an NRT analytics rule's time window to scan a year of cold telemetry does not resolve the case involving A SOC wants retrospective TI scans against a year of retained archive data.
C:This action would become suitable if a later condition arose: The indicator dataset changes and must be checked weekly. It is not the immediate answer to A SOC wants retrospective TI scans against a year of retained archive data.
D:That action serves a separate case (An enterprise wants Attack Surface Reduction rules assessed before aggressive enforcement) in the Manage a security operations environment domain. It does not specifically address the initial case.
Question 942
A SOC wants retrospective TI scans against a year of retained archive data. Which statement BEST explains why the proposed approach (Increase an NRT analytics rule's time window to scan a year of cold telemetry) fails?
- NRT detection is not a supported substitute for historical lake jobs
- Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data
- Unreviewed enforcement may disrupt legitimate workflows or bypass necessary exclusions
- A familiar product name alone establishes that the proposal is safe.
Explanation
Correct Answer
A:NRT detection is not a supported substitute for historical lake jobs. This directly explains the defect in Increase an NRT analytics rule's time window to scan a year of cold telemetry for A SOC wants retrospective TI scans against a year of retained archive data.
Incorrect Answers
B:This describes the reason for the preferred control, Use a governed Sentinel data-lake KQL job for historical indicator matching: Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data. It is not the direct defect in the proposed shortcut for A SOC wants retrospective TI scans against a year of retained archive data.
C:That concern applies to another security scenario (An enterprise wants Attack Surface Reduction rules assessed before aggressive enforcement). Here, A SOC wants retrospective TI scans against a year of retained archive data, the specified proposal fails because nRT detection is not a supported substitute for historical lake jobs.
D:Product-name familiarity cannot validate a proposed security action. For A SOC wants retrospective TI scans against a year of retained archive data, the actual issue is that nRT detection is not a supported substitute for historical lake jobs.
Question 943
A SOC wants retrospective TI scans against a year of retained archive data. Which operational finding would validate the selected solution, Use a governed Sentinel data-lake KQL job for historical indicator matching?
- The team schedules a future check of whether the job yields auditable matches and nonmatches for the selected indicator set, without recording any observed result.
- The job yields auditable matches and nonmatches for the selected indicator set
- Pilot event telemetry shows expected audited detections with acceptable false positives
- The SOC approves Use a governed Sentinel data-lake KQL job for historical indicator matching on paper but has not tested its operation.
Explanation
Correct Answer
B:Correct observed evidence. The job yields auditable matches and nonmatches for the selected indicator set. Given the original requirement, that result would substantiate the selected action, Use a governed Sentinel data-lake KQL job for historical indicator matching.
Incorrect Answers
A:A future validation plan is not an observed result. The actual verification should establish that the job yields auditable matches and nonmatches for the selected indicator set, in the scenario involving A SOC wants retrospective TI scans against a year of retained archive data.
C:This observation fits another setting (An enterprise wants Attack Surface Reduction rules assessed before aggressive enforcement). It does not verify Use a governed Sentinel data-lake KQL job for historical indicator matching against the original need.
D:Approval records intent but not actual protection or investigation. For A SOC wants retrospective TI scans against a year of retained archive data, an operational outcome must demonstrate that the job yields auditable matches and nonmatches for the selected indicator set.
Question 944
A SOC wants retrospective TI scans against a year of retained archive data. After the initial control is implemented, the indicator dataset changes and must be checked weekly. What is the best follow-up action?
- Build an approved scheduled job and document data-scan costs
- Pilot event telemetry shows expected audited detections with acceptable false positives
- Use a governed Sentinel data-lake KQL job for historical indicator matching
- Increase an NRT analytics rule's time window to scan a year of cold telemetry
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: The indicator dataset changes and must be checked weekly. Therefore Build an approved scheduled job and document data-scan costs is appropriate for A SOC wants retrospective TI scans against a year of retained archive data, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is The indicator dataset changes and must be checked weekly, so the proper follow-up must address it rather than merely note Pilot event telemetry shows expected audited detections with acceptable false positives.
C:This was the original control already implemented: Use a governed Sentinel data-lake KQL job for historical indicator matching. Its original rationale was: Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data. For the initial setting (A SOC wants retrospective TI scans against a year of retained archive data), that does not itself meet the new condition: The indicator dataset changes and must be checked weekly.
D:This was already unsuitable under the original condition because nRT detection is not a supported substitute for historical lake jobs. It also fails after the change affecting A SOC wants retrospective TI scans against a year of retained archive data.
Question 945
A security investigator has an IOC list and needs to look for matches in old lake records. Which action BEST addresses this Microsoft security operations requirement?
- Build an approved scheduled job and document data-scan costs
- Increase an NRT analytics rule's time window to scan a year of cold telemetry
- Use a governed Sentinel data-lake KQL job for historical indicator matching
- Verify playbook trigger type and Sentinel permissions on the resource group
Explanation
Correct Answer
C:Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data. The selected action is: Use a governed Sentinel data-lake KQL job for historical indicator matching.
Incorrect Answers
A:This action would become suitable if a later condition arose: The indicator dataset changes and must be checked weekly. It is not the immediate answer to A security investigator has an IOC list and needs to look for matches in old lake records.
B:NRT detection is not a supported substitute for historical lake jobs. The shortcut Increase an NRT analytics rule's time window to scan a year of cold telemetry does not resolve the case involving A security investigator has an IOC list and needs to look for matches in old lake records.
D:That action serves a separate case (A SOC engineering group cannot invoke a Logic Apps incident-response workflow despite creating it) in the Manage a security operations environment domain. It does not specifically address the initial case.
Question 946
A security investigator has an IOC list and needs to look for matches in old lake records. A colleague suggests: Increase an NRT analytics rule's time window to scan a year of cold telemetry. What is the MOST important technical defect in this suggestion?
- NRT detection is not a supported substitute for historical lake jobs
- A familiar product name alone establishes that the proposal is safe.
- Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data
- Trigger and access prerequisites determine which playbooks can be selected
Explanation
Correct Answer
A:NRT detection is not a supported substitute for historical lake jobs. This directly explains the defect in Increase an NRT analytics rule's time window to scan a year of cold telemetry for A security investigator has an IOC list and needs to look for matches in old lake records.
Incorrect Answers
B:Product-name familiarity cannot validate a proposed security action. For A security investigator has an IOC list and needs to look for matches in old lake records, the actual issue is that nRT detection is not a supported substitute for historical lake jobs.
C:This describes the reason for the preferred control, Use a governed Sentinel data-lake KQL job for historical indicator matching: Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data. It is not the direct defect in the proposed shortcut for A security investigator has an IOC list and needs to look for matches in old lake records.
D:That concern applies to another security scenario (A SOC engineering group cannot invoke a Logic Apps incident-response workflow despite creating it). Here, A security investigator has an IOC list and needs to look for matches in old lake records, the specified proposal fails because nRT detection is not a supported substitute for historical lake jobs.
Question 947
A security investigator has an IOC list and needs to look for matches in old lake records. After implementing Use a governed Sentinel data-lake KQL job for historical indicator matching, what result would BEST establish that it worked?
- A correctly triggered playbook appears and executes under authorized automation rule conditions
- The team schedules a future check of whether the job yields auditable matches and nonmatches for the selected indicator set, without recording any observed result.
- The SOC approves Use a governed Sentinel data-lake KQL job for historical indicator matching on paper but has not tested its operation.
- The job yields auditable matches and nonmatches for the selected indicator set
Explanation
Correct Answer
D:Correct observed evidence. The job yields auditable matches and nonmatches for the selected indicator set. Given the original requirement, that result would substantiate the selected action, Use a governed Sentinel data-lake KQL job for historical indicator matching.
Incorrect Answers
A:This observation fits another setting (A SOC engineering group cannot invoke a Logic Apps incident-response workflow despite creating it). It does not verify Use a governed Sentinel data-lake KQL job for historical indicator matching against the original need.
B:A future validation plan is not an observed result. The actual verification should establish that the job yields auditable matches and nonmatches for the selected indicator set, in the scenario involving A security investigator has an IOC list and needs to look for matches in old lake records.
C:Approval records intent but not actual protection or investigation. For A security investigator has an IOC list and needs to look for matches in old lake records, an operational outcome must demonstrate that the job yields auditable matches and nonmatches for the selected indicator set.
Question 948
A security investigator has an IOC list and needs to look for matches in old lake records. The original measure is in place. A new requirement arises: The indicator dataset changes and must be checked weekly. Which ADDITIONAL action BEST fits?
- Use a governed Sentinel data-lake KQL job for historical indicator matching
- Build an approved scheduled job and document data-scan costs
- The job yields auditable matches and nonmatches for the selected indicator set
- Increase an NRT analytics rule's time window to scan a year of cold telemetry
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: The indicator dataset changes and must be checked weekly. Therefore Build an approved scheduled job and document data-scan costs is appropriate for A security investigator has an IOC list and needs to look for matches in old lake records, in addition to the previous measure.
Incorrect Answers
A:This was the original control already implemented: Use a governed Sentinel data-lake KQL job for historical indicator matching. Its original rationale was: Data-lake jobs support historical ad-hoc analysis without treating every retained row as interactive hot data. For the initial setting (A security investigator has an IOC list and needs to look for matches in old lake records), that does not itself meet the new condition: The indicator dataset changes and must be checked weekly.
C:An observation is not the additional configuration or response action requested. The change is The indicator dataset changes and must be checked weekly, so the proper follow-up must address it rather than merely note The job yields auditable matches and nonmatches for the selected indicator set.
D:This was already unsuitable under the original condition because nRT detection is not a supported substitute for historical lake jobs. It also fails after the change affecting A security investigator has an IOC list and needs to look for matches in old lake records.
Question 949
A security operations analyst must handle this situation: A network team sends millions of firewall events daily but only per-hour aggregates are queried. What is the BEST initial response?
- Query each raw firewall record from every historical year for a simple hourly chart
- Analyze ingestion patterns and plan suitable analytics or data lake tiers per usage
- Extend the summary schema and validate aggregation logic and scheduling
- Configure suitable Sentinel summary rules with validated KQL and a summary output table
Explanation
Correct Answer
D:Summary rules aggregate source events into queried tables for efficient subsequent analysis. The selected action is: Configure suitable Sentinel summary rules with validated KQL and a summary output table.
Incorrect Answers
A:Repeated raw scans can be inefficient when aggregated trends satisfy the need. The shortcut Query each raw firewall record from every historical year for a simple hourly chart does not resolve the case involving A network team sends millions of firewall events daily but only per-hour aggregates are queried.
B:That action serves a separate case (A Sentinel administrator must distinguish ingest costs from query and retention expenses) in the Manage a security operations environment domain. It does not specifically address the initial case.
C:This action would become suitable if a later condition arose: The business requests per-device daily averages as well. It is not the immediate answer to A network team sends millions of firewall events daily but only per-hour aggregates are queried.
Question 950
A network team sends millions of firewall events daily but only per-hour aggregates are queried. Why should the SOC reject the proposed shortcut: Query each raw firewall record from every historical year for a simple hourly chart?
- A familiar product name alone establishes that the proposal is safe.
- Summary rules aggregate source events into queried tables for efficient subsequent analysis
- Unreviewed deletion destroys threat investigation and retention capability
- Repeated raw scans can be inefficient when aggregated trends satisfy the need
Explanation
Correct Answer
D:Repeated raw scans can be inefficient when aggregated trends satisfy the need. This directly explains the defect in Query each raw firewall record from every historical year for a simple hourly chart for A network team sends millions of firewall events daily but only per-hour aggregates are queried.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A network team sends millions of firewall events daily but only per-hour aggregates are queried, the actual issue is that repeated raw scans can be inefficient when aggregated trends satisfy the need.
B:This describes the reason for the preferred control, Configure suitable Sentinel summary rules with validated KQL and a summary output table: Summary rules aggregate source events into queried tables for efficient subsequent analysis. It is not the direct defect in the proposed shortcut for A network team sends millions of firewall events daily but only per-hour aggregates are queried.
C:That concern applies to another security scenario (A Sentinel administrator must distinguish ingest costs from query and retention expenses). Here, A network team sends millions of firewall events daily but only per-hour aggregates are queried, the specified proposal fails because repeated raw scans can be inefficient when aggregated trends satisfy the need.