Microsoft SC-200 Practice Test 26
Question 250
A cloud platform team needs Azure subscription write operations in Sentinel. A colleague suggests: Query only endpoint process telemetry for Azure subscription administration events. What is the MOST important technical defect in this suggestion?
- Endpoint process creation is not the Azure control-plane audit log
- Alerts are summaries and may omit crucial process, registry or network context
- A familiar product name alone establishes that the proposal is safe.
- Azure Activity telemetry records control-plane events and requires configured collection routing
Explanation
Correct Answer
A:Endpoint process creation is not the Azure control-plane audit log. This directly explains the defect in Query only endpoint process telemetry for Azure subscription administration events for A cloud platform team needs Azure subscription write operations in Sentinel.
Incorrect Answers
B:That concern applies to another security scenario (A threat hunter needs more context than the default device alert view provides). Here, A cloud platform team needs Azure subscription write operations in Sentinel, the specified proposal fails because endpoint process creation is not the Azure control-plane audit log.
C:Product-name familiarity cannot validate a proposed security action. For A cloud platform team needs Azure subscription write operations in Sentinel, the actual issue is that endpoint process creation is not the Azure control-plane audit log.
D:This describes the reason for the preferred control, Connect Azure Activity logs using supported diagnostic settings and policy configuration: Azure Activity telemetry records control-plane events and requires configured collection routing. It is not the direct defect in the proposed shortcut for A cloud platform team needs Azure subscription write operations in Sentinel.
Question 251
A cloud platform team needs Azure subscription write operations in Sentinel. After implementing Connect Azure Activity logs using supported diagnostic settings and policy configuration, what result would BEST establish that it worked?
- A known resource update appears with expected caller and operation in AzureActivity
- The team schedules a future check of whether a known resource update appears with expected caller and operation in AzureActivity, without recording any observed result.
- Supplemental artifacts clarify the sequence and affected account
- The SOC approves Connect Azure Activity logs using supported diagnostic settings and policy configuration on paper but has not tested its operation.
Explanation
Correct Answer
A:Correct observed evidence. A known resource update appears with expected caller and operation in AzureActivity. Given the original requirement, that result would substantiate the selected action, Connect Azure Activity logs using supported diagnostic settings and policy configuration.
Incorrect Answers
B:A future validation plan is not an observed result. The actual verification should establish that a known resource update appears with expected caller and operation in AzureActivity, in the scenario involving A cloud platform team needs Azure subscription write operations in Sentinel.
C:This observation fits another setting (A threat hunter needs more context than the default device alert view provides). It does not verify Connect Azure Activity logs using supported diagnostic settings and policy configuration against the original need.
D:Approval records intent but not actual protection or investigation. For A cloud platform team needs Azure subscription write operations in Sentinel, an operational outcome must demonstrate that a known resource update appears with expected caller and operation in AzureActivity.
Question 252
A cloud platform team needs Azure subscription write operations in Sentinel. The original measure is in place. A new requirement arises: A new subscription is added to the tenant. Which ADDITIONAL action BEST fits?
- A known resource update appears with expected caller and operation in AzureActivity
- Connect Azure Activity logs using supported diagnostic settings and policy configuration
- Query only endpoint process telemetry for Azure subscription administration events
- Extend the activity-log forwarding policy scope to the new subscription
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: A new subscription is added to the tenant. Therefore Extend the activity-log forwarding policy scope to the new subscription is appropriate for A cloud platform team needs Azure subscription write operations in Sentinel, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is A new subscription is added to the tenant, so the proper follow-up must address it rather than merely note A known resource update appears with expected caller and operation in AzureActivity.
B:This was the original control already implemented: Connect Azure Activity logs using supported diagnostic settings and policy configuration. Its original rationale was: Azure Activity telemetry records control-plane events and requires configured collection routing. For the initial setting (A cloud platform team needs Azure subscription write operations in Sentinel), that does not itself meet the new condition: A new subscription is added to the tenant.
C:This was already unsuitable under the original condition because endpoint process creation is not the Azure control-plane audit log. It also fails after the change affecting A cloud platform team needs Azure subscription write operations in Sentinel.
Question 253
A detection engineer wants visibility into Azure resource creation and policy changes. Select TWO entries that identify a sound initial security action and evidence that it worked. (Select TWO.)
- Extend the activity-log forwarding policy scope to the new subscription
- Connect Azure Activity logs using supported diagnostic settings and policy configuration
- A known resource update appears with expected caller and operation in AzureActivity
- Query only endpoint process telemetry for Azure subscription administration events
- Normalize timestamps and correlate operation, app ID, account and target across both sources
Explanation
Correct Answers
B:Azure Activity telemetry records control-plane events and requires configured collection routing. The selected action is: Connect Azure Activity logs using supported diagnostic settings and policy configuration.
C:Correct validation criterion. A known resource update appears with expected caller and operation in AzureActivity. This observable finding confirms the goal in the scenario: A detection engineer wants visibility into Azure resource creation and policy changes.
Incorrect Answers
A:This action would become suitable if a later condition arose: A new subscription is added to the tenant. It is not the immediate answer to A detection engineer wants visibility into Azure resource creation and policy changes.
D:Endpoint process creation is not the Azure control-plane audit log. The shortcut Query only endpoint process telemetry for Azure subscription administration events does not resolve the case involving A detection engineer wants visibility into Azure resource creation and policy changes.
E:That action serves a separate case (A cross-workload incident involves Graph calls and suspicious Exchange changes) in the Respond to security incidents domain. It does not specifically address the initial case.
Question 254
A detection engineer wants visibility into Azure resource creation and policy changes. Why should the SOC reject the proposed shortcut: Query only endpoint process telemetry for Azure subscription administration events?
- A familiar product name alone establishes that the proposal is safe.
- Time proximity alone does not establish a causal connection
- Endpoint process creation is not the Azure control-plane audit log
- Azure Activity telemetry records control-plane events and requires configured collection routing
Explanation
Correct Answer
C:Endpoint process creation is not the Azure control-plane audit log. This directly explains the defect in Query only endpoint process telemetry for Azure subscription administration events for A detection engineer wants visibility into Azure resource creation and policy changes.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A detection engineer wants visibility into Azure resource creation and policy changes, the actual issue is that endpoint process creation is not the Azure control-plane audit log.
B:That concern applies to another security scenario (A cross-workload incident involves Graph calls and suspicious Exchange changes). Here, A detection engineer wants visibility into Azure resource creation and policy changes, the specified proposal fails because endpoint process creation is not the Azure control-plane audit log.
D:This describes the reason for the preferred control, Connect Azure Activity logs using supported diagnostic settings and policy configuration: Azure Activity telemetry records control-plane events and requires configured collection routing. It is not the direct defect in the proposed shortcut for A detection engineer wants visibility into Azure resource creation and policy changes.
Question 255
A detection engineer wants visibility into Azure resource creation and policy changes. The SOC implements Connect Azure Activity logs using supported diagnostic settings and policy configuration. Which observed result provides credible confirmation?
- A verified actor or application link ties the two event streams into a timeline
- A known resource update appears with expected caller and operation in AzureActivity
- The team schedules a future check of whether a known resource update appears with expected caller and operation in AzureActivity, without recording any observed result.
- The SOC approves Connect Azure Activity logs using supported diagnostic settings and policy configuration on paper but has not tested its operation.
Explanation
Correct Answer
B:Correct observed evidence. A known resource update appears with expected caller and operation in AzureActivity. Given the original requirement, that result would substantiate the selected action, Connect Azure Activity logs using supported diagnostic settings and policy configuration.
Incorrect Answers
A:This observation fits another setting (A cross-workload incident involves Graph calls and suspicious Exchange changes). It does not verify Connect Azure Activity logs using supported diagnostic settings and policy configuration against the original need.
C:A future validation plan is not an observed result. The actual verification should establish that a known resource update appears with expected caller and operation in AzureActivity, in the scenario involving A detection engineer wants visibility into Azure resource creation and policy changes.
D:Approval records intent but not actual protection or investigation. For A detection engineer wants visibility into Azure resource creation and policy changes, an operational outcome must demonstrate that a known resource update appears with expected caller and operation in AzureActivity.
Question 256
The original problem was: A detection engineer wants visibility into Azure resource creation and policy changes. The solution is operating, but a new subscription is added to the tenant. What should change next?
- Extend the activity-log forwarding policy scope to the new subscription
- Connect Azure Activity logs using supported diagnostic settings and policy configuration
- Query only endpoint process telemetry for Azure subscription administration events
- A verified actor or application link ties the two event streams into a timeline
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: A new subscription is added to the tenant. Therefore Extend the activity-log forwarding policy scope to the new subscription is appropriate for A detection engineer wants visibility into Azure resource creation and policy changes, in addition to the previous measure.
Incorrect Answers
B:This was the original control already implemented: Connect Azure Activity logs using supported diagnostic settings and policy configuration. Its original rationale was: Azure Activity telemetry records control-plane events and requires configured collection routing. For the initial setting (A detection engineer wants visibility into Azure resource creation and policy changes), that does not itself meet the new condition: A new subscription is added to the tenant.
C:This was already unsuitable under the original condition because endpoint process creation is not the Azure control-plane audit log. It also fails after the change affecting A detection engineer wants visibility into Azure resource creation and policy changes.
D:An observation is not the additional configuration or response action requested. The change is A new subscription is added to the tenant, so the proper follow-up must address it rather than merely note A verified actor or application link ties the two event streams into a timeline.
Question 257
A storage team needs Azure resource data-plane diagnostic events in Sentinel. Which configuration or investigation step is MOST appropriate?
- Use only Azure Activity to capture every blob data-plane request
- Configure appropriate resource diagnostic settings to send supported logs to the workspace
- Enable and validate that category in the resource diagnostic settings
- Investigate Defender for Cloud workload protection alert and corroborate host telemetry
Explanation
Correct Answer
B:Azure resource diagnostic logs differ from subscription activity logs. The selected action is: Configure appropriate resource diagnostic settings to send supported logs to the workspace.
Incorrect Answers
A:Control-plane activity logs alone do not provide all storage data-plane events. The shortcut Use only Azure Activity to capture every blob data-plane request does not resolve the case involving A storage team needs Azure resource data-plane diagnostic events in Sentinel.
C:This action would become suitable if a later condition arose: A new supported diagnostic category becomes required. It is not the immediate answer to A storage team needs Azure resource data-plane diagnostic events in Sentinel.
D:That action serves a separate case (A Defender for Cloud incident flags likely exploitation on a production Linux machine) in the Respond to security incidents domain. It does not specifically address the initial case.
Question 258
A storage team needs Azure resource data-plane diagnostic events in Sentinel. Which statement BEST explains why the proposed approach (Use only Azure Activity to capture every blob data-plane request) fails?
- Control-plane activity logs alone do not provide all storage data-plane events
- A familiar product name alone establishes that the proposal is safe.
- Removing protection hides evidence rather than explaining suspicious workload activity
- Azure resource diagnostic logs differ from subscription activity logs
Explanation
Correct Answer
A:Control-plane activity logs alone do not provide all storage data-plane events. This directly explains the defect in Use only Azure Activity to capture every blob data-plane request for A storage team needs Azure resource data-plane diagnostic events in Sentinel.
Incorrect Answers
B:Product-name familiarity cannot validate a proposed security action. For A storage team needs Azure resource data-plane diagnostic events in Sentinel, the actual issue is that control-plane activity logs alone do not provide all storage data-plane events.
C:That concern applies to another security scenario (A Defender for Cloud incident flags likely exploitation on a production Linux machine). Here, A storage team needs Azure resource data-plane diagnostic events in Sentinel, the specified proposal fails because control-plane activity logs alone do not provide all storage data-plane events.
D:This describes the reason for the preferred control, Configure appropriate resource diagnostic settings to send supported logs to the workspace: Azure resource diagnostic logs differ from subscription activity logs. It is not the direct defect in the proposed shortcut for A storage team needs Azure resource data-plane diagnostic events in Sentinel.
Question 259
A storage team needs Azure resource data-plane diagnostic events in Sentinel. Which operational finding would validate the selected solution, Configure appropriate resource diagnostic settings to send supported logs to the workspace?
- Corroborated process or network evidence establishes the impacted resource and response
- The SOC approves Configure appropriate resource diagnostic settings to send supported logs to the workspace on paper but has not tested its operation.
- A test permitted storage access appears in the target diagnostic table
- The team schedules a future check of whether a test permitted storage access appears in the target diagnostic table, without recording any observed result.
Explanation
Correct Answer
C:Correct observed evidence. A test permitted storage access appears in the target diagnostic table. Given the original requirement, that result would substantiate the selected action, Configure appropriate resource diagnostic settings to send supported logs to the workspace.
Incorrect Answers
A:This observation fits another setting (A Defender for Cloud incident flags likely exploitation on a production Linux machine). It does not verify Configure appropriate resource diagnostic settings to send supported logs to the workspace against the original need.
B:Approval records intent but not actual protection or investigation. For A storage team needs Azure resource data-plane diagnostic events in Sentinel, an operational outcome must demonstrate that a test permitted storage access appears in the target diagnostic table.
D:A future validation plan is not an observed result. The actual verification should establish that a test permitted storage access appears in the target diagnostic table, in the scenario involving A storage team needs Azure resource data-plane diagnostic events in Sentinel.
Question 260
A storage team needs Azure resource data-plane diagnostic events in Sentinel. After the initial control is implemented, a new supported diagnostic category becomes required. What is the best follow-up action?
- Use only Azure Activity to capture every blob data-plane request
- Configure appropriate resource diagnostic settings to send supported logs to the workspace
- A test permitted storage access appears in the target diagnostic table
- Enable and validate that category in the resource diagnostic settings
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: A new supported diagnostic category becomes required. Therefore Enable and validate that category in the resource diagnostic settings is appropriate for A storage team needs Azure resource data-plane diagnostic events in Sentinel, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because control-plane activity logs alone do not provide all storage data-plane events. It also fails after the change affecting A storage team needs Azure resource data-plane diagnostic events in Sentinel.
B:This was the original control already implemented: Configure appropriate resource diagnostic settings to send supported logs to the workspace. Its original rationale was: Azure resource diagnostic logs differ from subscription activity logs. For the initial setting (A storage team needs Azure resource data-plane diagnostic events in Sentinel), that does not itself meet the new condition: A new supported diagnostic category becomes required.
C:An observation is not the additional configuration or response action requested. The change is A new supported diagnostic category becomes required, so the proper follow-up must address it rather than merely note A test permitted storage access appears in the target diagnostic table.