Microsoft SC-200 Practice Test 28
Question 270
An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel. Which statement BEST explains why the proposed approach (Paste plain indicator strings into a workbook title and assume they become TI data) fails?
- A workbook title does not ingest or normalize indicator records
- A familiar product name alone establishes that the proposal is safe.
- Network events and process-creation events contain different primary telemetry
- Threat indicators can support correlation and TI analytics when ingested and normalized
Explanation
Correct Answer
A:A workbook title does not ingest or normalize indicator records. This directly explains the defect in Paste plain indicator strings into a workbook title and assume they become TI data for An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel.
Incorrect Answers
B:Product-name familiarity cannot validate a proposed security action. For An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel, the actual issue is that a workbook title does not ingest or normalize indicator records.
C:That concern applies to another security scenario (A suspicious PowerShell chain spawned from a user-facing document). Here, An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel, the specified proposal fails because a workbook title does not ingest or normalize indicator records.
D:This describes the reason for the preferred control, Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings: Threat indicators can support correlation and TI analytics when ingested and normalized. It is not the direct defect in the proposed shortcut for An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel.
Question 271
An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel. Which operational finding would validate the selected solution, Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings?
- Sample approved indicators appear with type, confidence and provenance fields
- The SOC approves Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings on paper but has not tested its operation.
- The matching process creation record exposes parent process and command line
- The team schedules a future check of whether sample approved indicators appear with type, confidence and provenance fields, without recording any observed result.
Explanation
Correct Answer
A:Correct observed evidence. Sample approved indicators appear with type, confidence and provenance fields. Given the original requirement, that result would substantiate the selected action, Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings.
Incorrect Answers
B:Approval records intent but not actual protection or investigation. For An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel, an operational outcome must demonstrate that sample approved indicators appear with type, confidence and provenance fields.
C:This observation fits another setting (A suspicious PowerShell chain spawned from a user-facing document). It does not verify Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings against the original need.
D:A future validation plan is not an observed result. The actual verification should establish that sample approved indicators appear with type, confidence and provenance fields, in the scenario involving An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel.
Question 272
An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel. After the initial control is implemented, the feed supplies revoked or stale indicators. What is the best follow-up action?
- Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings
- Paste plain indicator strings into a workbook title and assume they become TI data
- Review expiration and confidence filters before continuing automated use
- The matching process creation record exposes parent process and command line
Explanation
Correct Answer
C:Correct follow-up. The requirement changed to: The feed supplies revoked or stale indicators. Therefore Review expiration and confidence filters before continuing automated use is appropriate for An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel, in addition to the previous measure.
Incorrect Answers
A:This was the original control already implemented: Configure a supported Sentinel threat-intelligence ingestion connector and verify indicator mappings. Its original rationale was: Threat indicators can support correlation and TI analytics when ingested and normalized. For the initial setting (An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel), that does not itself meet the new condition: The feed supplies revoked or stale indicators.
B:This was already unsuitable under the original condition because a workbook title does not ingest or normalize indicator records. It also fails after the change affecting An incident hunter needs IP indicators from an approved threat-intelligence feed in Sentinel.
D:An observation is not the additional configuration or response action requested. The change is The feed supplies revoked or stale indicators, so the proper follow-up must address it rather than merely note The matching process creation record exposes parent process and command line.
Question 273
An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector. Which action BEST addresses this Microsoft security operations requirement?
- Send arbitrary JSON to a nonexistent table name and assume it appears immediately
- Create a custom workspace table and use a supported ingestion path with schema mapping
- Investigate Microsoft Graph activity logs and correlate app identity, request and response details
- Update the transformation/schema safely and test old and new record shapes
Explanation
Correct Answer
B:Custom tables require compatible ingestion, columns, and access permissions. The selected action is: Create a custom workspace table and use a supported ingestion path with schema mapping.
Incorrect Answers
A:Without table creation and valid ingestion rules the data will not land reliably. The shortcut Send arbitrary JSON to a nonexistent table name and assume it appears immediately does not resolve the case involving An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector.
C:That action serves a separate case (A SOC detects application permission abuse using Microsoft Graph activity logs) in the Respond to security incidents domain. It does not specifically address the initial case.
D:This action would become suitable if a later condition arose: The SaaS adds a nested action metadata field. It is not the immediate answer to An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector.
Question 274
An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector. A colleague suggests: Send arbitrary JSON to a nonexistent table name and assume it appears immediately. What is the MOST important technical defect in this suggestion?
- Custom tables require compatible ingestion, columns, and access permissions
- App-only permissions can operate independently of interactive user MFA
- Without table creation and valid ingestion rules the data will not land reliably
- A familiar product name alone establishes that the proposal is safe.
Explanation
Correct Answer
C:Without table creation and valid ingestion rules the data will not land reliably. This directly explains the defect in Send arbitrary JSON to a nonexistent table name and assume it appears immediately for An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector.
Incorrect Answers
A:This describes the reason for the preferred control, Create a custom workspace table and use a supported ingestion path with schema mapping: Custom tables require compatible ingestion, columns, and access permissions. It is not the direct defect in the proposed shortcut for An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector.
B:That concern applies to another security scenario (A SOC detects application permission abuse using Microsoft Graph activity logs). Here, An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector, the specified proposal fails because without table creation and valid ingestion rules the data will not land reliably.
D:Product-name familiarity cannot validate a proposed security action. For An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector, the actual issue is that without table creation and valid ingestion rules the data will not land reliably.
Question 275
An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector. After implementing Create a custom workspace table and use a supported ingestion path with schema mapping, what result would BEST establish that it worked?
- A controlled JSON record populates the intended typed custom columns
- The team schedules a future check of whether a controlled JSON record populates the intended typed custom columns, without recording any observed result.
- API call records identify the app, request target and suspicious activity times
- The SOC approves Create a custom workspace table and use a supported ingestion path with schema mapping on paper but has not tested its operation.
Explanation
Correct Answer
A:Correct observed evidence. A controlled JSON record populates the intended typed custom columns. Given the original requirement, that result would substantiate the selected action, Create a custom workspace table and use a supported ingestion path with schema mapping.
Incorrect Answers
B:A future validation plan is not an observed result. The actual verification should establish that a controlled JSON record populates the intended typed custom columns, in the scenario involving An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector.
C:This observation fits another setting (A SOC detects application permission abuse using Microsoft Graph activity logs). It does not verify Create a custom workspace table and use a supported ingestion path with schema mapping against the original need.
D:Approval records intent but not actual protection or investigation. For An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector, an operational outcome must demonstrate that a controlled JSON record populates the intended typed custom columns.
Question 276
An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector. The original measure is in place. A new requirement arises: The SaaS adds a nested action metadata field. Which ADDITIONAL action BEST fits?
- Create a custom workspace table and use a supported ingestion path with schema mapping
- Send arbitrary JSON to a nonexistent table name and assume it appears immediately
- Update the transformation/schema safely and test old and new record shapes
- A controlled JSON record populates the intended typed custom columns
Explanation
Correct Answer
C:Correct follow-up. The requirement changed to: The SaaS adds a nested action metadata field. Therefore Update the transformation/schema safely and test old and new record shapes is appropriate for An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector, in addition to the previous measure.
Incorrect Answers
A:This was the original control already implemented: Create a custom workspace table and use a supported ingestion path with schema mapping. Its original rationale was: Custom tables require compatible ingestion, columns, and access permissions. For the initial setting (An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector), that does not itself meet the new condition: The SaaS adds a nested action metadata field.
B:This was already unsuitable under the original condition because without table creation and valid ingestion rules the data will not land reliably. It also fails after the change affecting An enterprise SaaS exports line-delimited JSON logs not covered by an existing connector.
D:An observation is not the additional configuration or response action requested. The change is The SaaS adds a nested action metadata field, so the proper follow-up must address it rather than merely note A controlled JSON record populates the intended typed custom columns.
Question 277
A security operations analyst must handle this situation: A vendor wants its proprietary audit events ingested into Sentinel with a defined schema. What is the BEST initial response?
- Update the transformation/schema safely and test old and new record shapes
- Apply supported Entra account restriction and session revocation consistent with incident authority
- Create a custom workspace table and use a supported ingestion path with schema mapping
- Send arbitrary JSON to a nonexistent table name and assume it appears immediately
Explanation
Correct Answer
C:Custom tables require compatible ingestion, columns, and access permissions. The selected action is: Create a custom workspace table and use a supported ingestion path with schema mapping.
Incorrect Answers
A:This action would become suitable if a later condition arose: The SaaS adds a nested action metadata field. It is not the immediate answer to A vendor wants its proprietary audit events ingested into Sentinel with a defined schema.
B:That action serves a separate case (A compromised administrator is still actively authenticating to cloud applications) in the Respond to security incidents domain. It does not specifically address the initial case.
D:Without table creation and valid ingestion rules the data will not land reliably. The shortcut Send arbitrary JSON to a nonexistent table name and assume it appears immediately does not resolve the case involving A vendor wants its proprietary audit events ingested into Sentinel with a defined schema.
Question 278
A vendor wants its proprietary audit events ingested into Sentinel with a defined schema. Why should the SOC reject the proposed shortcut: Send arbitrary JSON to a nonexistent table name and assume it appears immediately?
- A familiar product name alone establishes that the proposal is safe.
- Custom tables require compatible ingestion, columns, and access permissions
- Without table creation and valid ingestion rules the data will not land reliably
- Profile appearance has no security effect on active authentication
Explanation
Correct Answer
C:Without table creation and valid ingestion rules the data will not land reliably. This directly explains the defect in Send arbitrary JSON to a nonexistent table name and assume it appears immediately for A vendor wants its proprietary audit events ingested into Sentinel with a defined schema.
Incorrect Answers
A:Product-name familiarity cannot validate a proposed security action. For A vendor wants its proprietary audit events ingested into Sentinel with a defined schema, the actual issue is that without table creation and valid ingestion rules the data will not land reliably.
B:This describes the reason for the preferred control, Create a custom workspace table and use a supported ingestion path with schema mapping: Custom tables require compatible ingestion, columns, and access permissions. It is not the direct defect in the proposed shortcut for A vendor wants its proprietary audit events ingested into Sentinel with a defined schema.
D:That concern applies to another security scenario (A compromised administrator is still actively authenticating to cloud applications). Here, A vendor wants its proprietary audit events ingested into Sentinel with a defined schema, the specified proposal fails because without table creation and valid ingestion rules the data will not land reliably.
Question 279
A vendor wants its proprietary audit events ingested into Sentinel with a defined schema. The SOC implements Create a custom workspace table and use a supported ingestion path with schema mapping. Which observed result provides credible confirmation?
- A controlled JSON record populates the intended typed custom columns
- The team schedules a future check of whether a controlled JSON record populates the intended typed custom columns, without recording any observed result.
- The SOC approves Create a custom workspace table and use a supported ingestion path with schema mapping on paper but has not tested its operation.
- New attempts are blocked and sessions are invalidated as intended
Explanation
Correct Answer
A:Correct observed evidence. A controlled JSON record populates the intended typed custom columns. Given the original requirement, that result would substantiate the selected action, Create a custom workspace table and use a supported ingestion path with schema mapping.
Incorrect Answers
B:A future validation plan is not an observed result. The actual verification should establish that a controlled JSON record populates the intended typed custom columns, in the scenario involving A vendor wants its proprietary audit events ingested into Sentinel with a defined schema.
C:Approval records intent but not actual protection or investigation. For A vendor wants its proprietary audit events ingested into Sentinel with a defined schema, an operational outcome must demonstrate that a controlled JSON record populates the intended typed custom columns.
D:This observation fits another setting (A compromised administrator is still actively authenticating to cloud applications). It does not verify Create a custom workspace table and use a supported ingestion path with schema mapping against the original need.
Question 280
The original problem was: A vendor wants its proprietary audit events ingested into Sentinel with a defined schema. The solution is operating, but the SaaS adds a nested action metadata field. What should change next?
- Send arbitrary JSON to a nonexistent table name and assume it appears immediately
- Update the transformation/schema safely and test old and new record shapes
- Create a custom workspace table and use a supported ingestion path with schema mapping
- New attempts are blocked and sessions are invalidated as intended
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: The SaaS adds a nested action metadata field. Therefore Update the transformation/schema safely and test old and new record shapes is appropriate for A vendor wants its proprietary audit events ingested into Sentinel with a defined schema, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because without table creation and valid ingestion rules the data will not land reliably. It also fails after the change affecting A vendor wants its proprietary audit events ingested into Sentinel with a defined schema.
C:This was the original control already implemented: Create a custom workspace table and use a supported ingestion path with schema mapping. Its original rationale was: Custom tables require compatible ingestion, columns, and access permissions. For the initial setting (A vendor wants its proprietary audit events ingested into Sentinel with a defined schema), that does not itself meet the new condition: The SaaS adds a nested action metadata field.
D:An observation is not the additional configuration or response action requested. The change is The SaaS adds a nested action metadata field, so the proper follow-up must address it rather than merely note New attempts are blocked and sessions are invalidated as intended.