Microsoft SC-200 Practice Test 16
Question 150
A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot. Which statement BEST explains why the proposed approach (Set every security table to cold data lake tier then expect scheduled real-time alerting on it) fails?
- Cosmetic user changes do not revoke a malicious application grant
- Interactive analytics and low-cost historical data lake retention have different performance and capabilities
- A familiar product name alone establishes that the proposal is safe.
- Cold data lake tier does not support the full real-time analytics-rule experience
Explanation
Correct Answer
D:Cold data lake tier does not support the full real-time analytics-rule experience. This directly explains the defect in Set every security table to cold data lake tier then expect scheduled real-time alerting on it for A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot.
Incorrect Answers
A:That concern applies to another security scenario (An attacker registered an OAuth application granted unusually broad delegated permissions). Here, A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot, the specified proposal fails because cold data lake tier does not support the full real-time analytics-rule experience.
B:This describes the reason for the preferred control, Choose analytics-tier interactive retention and supported data-lake retention separately: Interactive analytics and low-cost historical data lake retention have different performance and capabilities. It is not the direct defect in the proposed shortcut for A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot.
C:Product-name familiarity cannot validate a proposed security action. For A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot, the actual issue is that cold data lake tier does not support the full real-time analytics-rule experience.
Question 151
A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot. Which operational finding would validate the selected solution, Choose analytics-tier interactive retention and supported data-lake retention separately?
- The team schedules a future check of whether recent queries work interactively and approved older records are accessible through supported lake jobs, without recording any observed result.
- The SOC approves Choose analytics-tier interactive retention and supported data-lake retention separately on paper but has not tested its operation.
- Recent queries work interactively and approved older records are accessible through supported lake jobs
- The unauthorized grant is removed and follow-up app activity stops
Explanation
Correct Answer
C:Correct observed evidence. Recent queries work interactively and approved older records are accessible through supported lake jobs. Given the original requirement, that result would substantiate the selected action, Choose analytics-tier interactive retention and supported data-lake retention separately.
Incorrect Answers
A:A future validation plan is not an observed result. The actual verification should establish that recent queries work interactively and approved older records are accessible through supported lake jobs, in the scenario involving A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot.
B:Approval records intent but not actual protection or investigation. For A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot, an operational outcome must demonstrate that recent queries work interactively and approved older records are accessible through supported lake jobs.
D:This observation fits another setting (An attacker registered an OAuth application granted unusually broad delegated permissions). It does not verify Choose analytics-tier interactive retention and supported data-lake retention separately against the original need.
Question 152
A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot. After the initial control is implemented, an old dataset is needed for a new real-time analytic detection. What is the best follow-up action?
- Set every security table to cold data lake tier then expect scheduled real-time alerting on it
- Reassess tier placement and ingestion so required events are available in analytics
- The unauthorized grant is removed and follow-up app activity stops
- Choose analytics-tier interactive retention and supported data-lake retention separately
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: An old dataset is needed for a new real-time analytic detection. Therefore Reassess tier placement and ingestion so required events are available in analytics is appropriate for A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because cold data lake tier does not support the full real-time analytics-rule experience. It also fails after the change affecting A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot.
C:An observation is not the additional configuration or response action requested. The change is An old dataset is needed for a new real-time analytic detection, so the proper follow-up must address it rather than merely note The unauthorized grant is removed and follow-up app activity stops.
D:This was the original control already implemented: Choose analytics-tier interactive retention and supported data-lake retention separately. Its original rationale was: Interactive analytics and low-cost historical data lake retention have different performance and capabilities. For the initial setting (A SOC manager wants inexpensive access to long-running archive hunts without keeping all logs hot), that does not itself meet the new condition: An old dataset is needed for a new real-time analytic detection.
Question 153
A Defender XDR analyst expects all advanced hunting rows to remain for years. Which action BEST addresses this Microsoft security operations requirement?
- Plan permitted lake or long-term retention and use the supported historical query path
- Assume every XDR advanced hunting event is queryable indefinitely without storage configuration
- Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers
- Review incident correlation and split unrelated incident scope where supported
Explanation
Correct Answer
C:Different telemetry sources and tiers have distinct default and configurable retention periods. The selected action is: Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers.
Incorrect Answers
A:This action would become suitable if a later condition arose: Investigators need records older than current interactive retention. It is not the immediate answer to A Defender XDR analyst expects all advanced hunting rows to remain for years.
B:Historical query availability depends on tier, source, and retention configuration. The shortcut Assume every XDR advanced hunting event is queryable indefinitely without storage configuration does not resolve the case involving A Defender XDR analyst expects all advanced hunting rows to remain for years.
D:That action serves a separate case (A SOC manager sees separate unrelated accounts and events in a merged investigation) in the Respond to security incidents domain. It does not specifically address the initial case.
Question 154
A Defender XDR analyst expects all advanced hunting rows to remain for years. A colleague suggests: Assume every XDR advanced hunting event is queryable indefinitely without storage configuration. What is the MOST important technical defect in this suggestion?
- Historical query availability depends on tier, source, and retention configuration
- A familiar product name alone establishes that the proposal is safe.
- Temporal coincidence does not establish common malicious causation
- Different telemetry sources and tiers have distinct default and configurable retention periods
Explanation
Correct Answer
A:Historical query availability depends on tier, source, and retention configuration. This directly explains the defect in Assume every XDR advanced hunting event is queryable indefinitely without storage configuration for A Defender XDR analyst expects all advanced hunting rows to remain for years.
Incorrect Answers
B:Product-name familiarity cannot validate a proposed security action. For A Defender XDR analyst expects all advanced hunting rows to remain for years, the actual issue is that historical query availability depends on tier, source, and retention configuration.
C:That concern applies to another security scenario (A SOC manager sees separate unrelated accounts and events in a merged investigation). Here, A Defender XDR analyst expects all advanced hunting rows to remain for years, the specified proposal fails because historical query availability depends on tier, source, and retention configuration.
D:This describes the reason for the preferred control, Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers: Different telemetry sources and tiers have distinct default and configurable retention periods. It is not the direct defect in the proposed shortcut for A Defender XDR analyst expects all advanced hunting rows to remain for years.
Question 155
A Defender XDR analyst expects all advanced hunting rows to remain for years. After implementing Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers, what result would BEST establish that it worked?
- The team schedules a future check of whether a date-bounded query returns only data retained in the correctly configured tier, without recording any observed result.
- Separate incident records preserve correct evidence and ownership
- The SOC approves Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers on paper but has not tested its operation.
- A date-bounded query returns only data retained in the correctly configured tier
Explanation
Correct Answer
D:Correct observed evidence. A date-bounded query returns only data retained in the correctly configured tier. Given the original requirement, that result would substantiate the selected action, Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers.
Incorrect Answers
A:A future validation plan is not an observed result. The actual verification should establish that a date-bounded query returns only data retained in the correctly configured tier, in the scenario involving A Defender XDR analyst expects all advanced hunting rows to remain for years.
B:This observation fits another setting (A SOC manager sees separate unrelated accounts and events in a merged investigation). It does not verify Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers against the original need.
C:Approval records intent but not actual protection or investigation. For A Defender XDR analyst expects all advanced hunting rows to remain for years, an operational outcome must demonstrate that a date-bounded query returns only data retained in the correctly configured tier.
Question 156
A Defender XDR analyst expects all advanced hunting rows to remain for years. The original measure is in place. A new requirement arises: Investigators need records older than current interactive retention. Which ADDITIONAL action BEST fits?
- Plan permitted lake or long-term retention and use the supported historical query path
- Assume every XDR advanced hunting event is queryable indefinitely without storage configuration
- A date-bounded query returns only data retained in the correctly configured tier
- Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: Investigators need records older than current interactive retention. Therefore Plan permitted lake or long-term retention and use the supported historical query path is appropriate for A Defender XDR analyst expects all advanced hunting rows to remain for years, in addition to the previous measure.
Incorrect Answers
B:This was already unsuitable under the original condition because historical query availability depends on tier, source, and retention configuration. It also fails after the change affecting A Defender XDR analyst expects all advanced hunting rows to remain for years.
C:An observation is not the additional configuration or response action requested. The change is Investigators need records older than current interactive retention, so the proper follow-up must address it rather than merely note A date-bounded query returns only data retained in the correctly configured tier.
D:This was the original control already implemented: Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers. Its original rationale was: Different telemetry sources and tiers have distinct default and configurable retention periods. For the initial setting (A Defender XDR analyst expects all advanced hunting rows to remain for years), that does not itself meet the new condition: Investigators need records older than current interactive retention.
Question 157
A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan. Select TWO entries that identify a sound initial security action and evidence that it worked. (Select TWO.)
- Assume every XDR advanced hunting event is queryable indefinitely without storage configuration
- A date-bounded query returns only data retained in the correctly configured tier
- Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers
- Plan permitted lake or long-term retention and use the supported historical query path
- Correlate cloud workload alerts with resource activity and identity audit evidence
Explanation
Correct Answers
B:Correct validation criterion. A date-bounded query returns only data retained in the correctly configured tier. This observable finding confirms the goal in the scenario: A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
C:Different telemetry sources and tiers have distinct default and configurable retention periods. The selected action is: Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers.
Incorrect Answers
A:Historical query availability depends on tier, source, and retention configuration. The shortcut Assume every XDR advanced hunting event is queryable indefinitely without storage configuration does not resolve the case involving A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
D:This action would become suitable if a later condition arose: Investigators need records older than current interactive retention. It is not the immediate answer to A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
E:That action serves a separate case (A cloud storage account exposes a service principal with suspicious privileged changes) in the Respond to security incidents domain. It does not specifically address the initial case.
Question 158
A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan. Why should the SOC reject the proposed shortcut: Assume every XDR advanced hunting event is queryable indefinitely without storage configuration?
- Unrelated browsing does not establish what happened in the cloud workload
- Different telemetry sources and tiers have distinct default and configurable retention periods
- A familiar product name alone establishes that the proposal is safe.
- Historical query availability depends on tier, source, and retention configuration
Explanation
Correct Answer
D:Historical query availability depends on tier, source, and retention configuration. This directly explains the defect in Assume every XDR advanced hunting event is queryable indefinitely without storage configuration for A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
Incorrect Answers
A:That concern applies to another security scenario (A cloud storage account exposes a service principal with suspicious privileged changes). Here, A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan, the specified proposal fails because historical query availability depends on tier, source, and retention configuration.
B:This describes the reason for the preferred control, Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers: Different telemetry sources and tiers have distinct default and configurable retention periods. It is not the direct defect in the proposed shortcut for A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
C:Product-name familiarity cannot validate a proposed security action. For A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan, the actual issue is that historical query availability depends on tier, source, and retention configuration.
Question 159
A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan. The SOC implements Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers. Which observed result provides credible confirmation?
- Azure management events and workload telemetry agree on the affected principal and operation
- The SOC approves Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers on paper but has not tested its operation.
- A date-bounded query returns only data retained in the correctly configured tier
- The team schedules a future check of whether a date-bounded query returns only data retained in the correctly configured tier, without recording any observed result.
Explanation
Correct Answer
C:Correct observed evidence. A date-bounded query returns only data retained in the correctly configured tier. Given the original requirement, that result would substantiate the selected action, Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers.
Incorrect Answers
A:This observation fits another setting (A cloud storage account exposes a service principal with suspicious privileged changes). It does not verify Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers against the original need.
B:Approval records intent but not actual protection or investigation. For A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan, an operational outcome must demonstrate that a date-bounded query returns only data retained in the correctly configured tier.
D:A future validation plan is not an observed result. The actual verification should establish that a date-bounded query returns only data retained in the correctly configured tier, in the scenario involving A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
Question 160
The original problem was: A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan. The solution is operating, but investigators need records older than current interactive retention. What should change next?
- Plan permitted lake or long-term retention and use the supported historical query path
- Azure management events and workload telemetry agree on the affected principal and operation
- Assume every XDR advanced hunting event is queryable indefinitely without storage configuration
- Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: Investigators need records older than current interactive retention. Therefore Plan permitted lake or long-term retention and use the supported historical query path is appropriate for A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is Investigators need records older than current interactive retention, so the proper follow-up must address it rather than merely note Azure management events and workload telemetry agree on the affected principal and operation.
C:This was already unsuitable under the original condition because historical query availability depends on tier, source, and retention configuration. It also fails after the change affecting A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan.
D:This was the original control already implemented: Distinguish Defender XDR hunting retention from configured Sentinel analytics and lake data tiers. Its original rationale was: Different telemetry sources and tiers have distinct default and configurable retention periods. For the initial setting (A governance reviewer is comparing default XDR hunting availability to a longer Sentinel data-lake retention plan), that does not itself meet the new condition: Investigators need records older than current interactive retention.