Microsoft SC-200 Practice Test 45
Question 440
A high-confidence malware attachment was delivered before signature updates. After the initial control is implemented, the email is found in a shared mailbox with a special exemption. What is the best follow-up action?
- Investigate policy scope and perform authorized manual remediation if needed
- Assume a traditional spam-filter pass proves a delivered attachment is harmless
- Recomputed sample counts agree with available summary output records
- Review Defender for Office 365 automated remediation and zero-hour auto purge applicability
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: The email is found in a shared mailbox with a special exemption. Therefore Investigate policy scope and perform authorized manual remediation if needed is appropriate for A high-confidence malware attachment was delivered before signature updates, in addition to the previous measure.
Incorrect Answers
B:This was already unsuitable under the original condition because initial mail delivery does not exclude subsequent malicious classification. It also fails after the change affecting A high-confidence malware attachment was delivered before signature updates.
C:An observation is not the additional configuration or response action requested. The change is The email is found in a shared mailbox with a special exemption, so the proper follow-up must address it rather than merely note Recomputed sample counts agree with available summary output records.
D:This was the original control already implemented: Review Defender for Office 365 automated remediation and zero-hour auto purge applicability. Its original rationale was: Supported remediation can remove qualifying malicious mail after initial delivery. For the initial setting (A high-confidence malware attachment was delivered before signature updates), that does not itself meet the new condition: The email is found in a shared mailbox with a special exemption.
Question 441
A user reports that a previously delivered malicious message remained in the mailbox. Which action BEST addresses this Microsoft security operations requirement?
- Assume a traditional spam-filter pass proves a delivered attachment is harmless
- Review Defender for Office 365 automated remediation and zero-hour auto purge applicability
- Use Defender XDR DeviceLogonEvents and relevant logon types for the device scope
- Investigate policy scope and perform authorized manual remediation if needed
Explanation
Correct Answer
B:Supported remediation can remove qualifying malicious mail after initial delivery. The selected action is: Review Defender for Office 365 automated remediation and zero-hour auto purge applicability.
Incorrect Answers
A:Initial mail delivery does not exclude subsequent malicious classification. The shortcut Assume a traditional spam-filter pass proves a delivered attachment is harmless does not resolve the case involving A user reports that a previously delivered malicious message remained in the mailbox.
C:That action serves a separate case (A SOC detects an account performing unexpected interactive and network sign-ins) in the Perform threat hunting domain. It does not specifically address the initial case.
D:This action would become suitable if a later condition arose: The email is found in a shared mailbox with a special exemption. It is not the immediate answer to A user reports that a previously delivered malicious message remained in the mailbox.
Question 442
A user reports that a previously delivered malicious message remained in the mailbox. A colleague suggests: Assume a traditional spam-filter pass proves a delivered attachment is harmless. What is the MOST important technical defect in this suggestion?
- File system events do not directly describe successful or failed authentication
- Supported remediation can remove qualifying malicious mail after initial delivery
- A familiar product name alone establishes that the proposal is safe.
- Initial mail delivery does not exclude subsequent malicious classification
Explanation
Correct Answer
D:Initial mail delivery does not exclude subsequent malicious classification. This directly explains the defect in Assume a traditional spam-filter pass proves a delivered attachment is harmless for A user reports that a previously delivered malicious message remained in the mailbox.
Incorrect Answers
A:That concern applies to another security scenario (A SOC detects an account performing unexpected interactive and network sign-ins). Here, A user reports that a previously delivered malicious message remained in the mailbox, the specified proposal fails because initial mail delivery does not exclude subsequent malicious classification.
B:This describes the reason for the preferred control, Review Defender for Office 365 automated remediation and zero-hour auto purge applicability: Supported remediation can remove qualifying malicious mail after initial delivery. It is not the direct defect in the proposed shortcut for A user reports that a previously delivered malicious message remained in the mailbox.
C:Product-name familiarity cannot validate a proposed security action. For A user reports that a previously delivered malicious message remained in the mailbox, the actual issue is that initial mail delivery does not exclude subsequent malicious classification.
Question 443
A user reports that a previously delivered malicious message remained in the mailbox. After implementing Review Defender for Office 365 automated remediation and zero-hour auto purge applicability, what result would BEST establish that it worked?
- A qualifying sample message receives the expected retrospective remediation outcome
- The team schedules a future check of whether a qualifying sample message receives the expected retrospective remediation outcome, without recording any observed result.
- The SOC approves Review Defender for Office 365 automated remediation and zero-hour auto purge applicability on paper but has not tested its operation.
- Time-bounded results list affected devices, accounts and logon types
Explanation
Correct Answer
A:Correct observed evidence. A qualifying sample message receives the expected retrospective remediation outcome. Given the original requirement, that result would substantiate the selected action, Review Defender for Office 365 automated remediation and zero-hour auto purge applicability.
Incorrect Answers
B:A future validation plan is not an observed result. The actual verification should establish that a qualifying sample message receives the expected retrospective remediation outcome, in the scenario involving A user reports that a previously delivered malicious message remained in the mailbox.
C:Approval records intent but not actual protection or investigation. For A user reports that a previously delivered malicious message remained in the mailbox, an operational outcome must demonstrate that a qualifying sample message receives the expected retrospective remediation outcome.
D:This observation fits another setting (A SOC detects an account performing unexpected interactive and network sign-ins). It does not verify Review Defender for Office 365 automated remediation and zero-hour auto purge applicability against the original need.
Question 444
A user reports that a previously delivered malicious message remained in the mailbox. The original measure is in place. A new requirement arises: The email is found in a shared mailbox with a special exemption. Which ADDITIONAL action BEST fits?
- A qualifying sample message receives the expected retrospective remediation outcome
- Investigate policy scope and perform authorized manual remediation if needed
- Review Defender for Office 365 automated remediation and zero-hour auto purge applicability
- Assume a traditional spam-filter pass proves a delivered attachment is harmless
Explanation
Correct Answer
B:Correct follow-up. The requirement changed to: The email is found in a shared mailbox with a special exemption. Therefore Investigate policy scope and perform authorized manual remediation if needed is appropriate for A user reports that a previously delivered malicious message remained in the mailbox, in addition to the previous measure.
Incorrect Answers
A:An observation is not the additional configuration or response action requested. The change is The email is found in a shared mailbox with a special exemption, so the proper follow-up must address it rather than merely note A qualifying sample message receives the expected retrospective remediation outcome.
C:This was the original control already implemented: Review Defender for Office 365 automated remediation and zero-hour auto purge applicability. Its original rationale was: Supported remediation can remove qualifying malicious mail after initial delivery. For the initial setting (A user reports that a previously delivered malicious message remained in the mailbox), that does not itself meet the new condition: The email is found in a shared mailbox with a special exemption.
D:This was already unsuitable under the original condition because initial mail delivery does not exclude subsequent malicious classification. It also fails after the change affecting A user reports that a previously delivered malicious message remained in the mailbox.
Question 445
An attacker registered an OAuth application granted unusually broad delegated permissions. Select TWO entries that identify a sound initial security action and evidence that it worked. (Select TWO.)
- Investigate the app grant and revoke unauthorized consent or app sessions using supported controls
- The unauthorized grant is removed and follow-up app activity stops
- Rotate or revoke the affected service principal credentials and audit further grants
- Use KQL extend for derived columns and project only fields needed downstream
- Reset only the mailbox display name and assume app authorization disappears
Explanation
Correct Answers
A:OAuth consent abuse can persist through application permissions independent of a user's password. The selected action is: Investigate the app grant and revoke unauthorized consent or app sessions using supported controls.
B:Correct validation criterion. The unauthorized grant is removed and follow-up app activity stops. This observable finding confirms the goal in the scenario: An attacker registered an OAuth application granted unusually broad delegated permissions.
Incorrect Answers
C:This action would become suitable if a later condition arose: Investigation reveals a compromised service principal credential too. It is not the immediate answer to An attacker registered an OAuth application granted unusually broad delegated permissions.
D:That action serves a separate case (A SOC wants to project a calculated risk flag for multiple events) in the Perform threat hunting domain. It does not specifically address the initial case.
E:Cosmetic user changes do not revoke a malicious application grant. The shortcut Reset only the mailbox display name and assume app authorization disappears does not resolve the case involving An attacker registered an OAuth application granted unusually broad delegated permissions.
Question 446
An attacker registered an OAuth application granted unusually broad delegated permissions. Why should the SOC reject the proposed shortcut: Reset only the mailbox display name and assume app authorization disappears?
- OAuth consent abuse can persist through application permissions independent of a user's password
- UI labels do not derive values inside the KQL result set
- Cosmetic user changes do not revoke a malicious application grant
- A familiar product name alone establishes that the proposal is safe.
Explanation
Correct Answer
C:Cosmetic user changes do not revoke a malicious application grant. This directly explains the defect in Reset only the mailbox display name and assume app authorization disappears for An attacker registered an OAuth application granted unusually broad delegated permissions.
Incorrect Answers
A:This describes the reason for the preferred control, Investigate the app grant and revoke unauthorized consent or app sessions using supported controls: OAuth consent abuse can persist through application permissions independent of a user's password. It is not the direct defect in the proposed shortcut for An attacker registered an OAuth application granted unusually broad delegated permissions.
B:That concern applies to another security scenario (A SOC wants to project a calculated risk flag for multiple events). Here, An attacker registered an OAuth application granted unusually broad delegated permissions, the specified proposal fails because cosmetic user changes do not revoke a malicious application grant.
D:Product-name familiarity cannot validate a proposed security action. For An attacker registered an OAuth application granted unusually broad delegated permissions, the actual issue is that cosmetic user changes do not revoke a malicious application grant.
Question 447
An attacker registered an OAuth application granted unusually broad delegated permissions. The SOC implements Investigate the app grant and revoke unauthorized consent or app sessions using supported controls. Which observed result provides credible confirmation?
- Derived fields have consistent types and expected values on sample rows
- The SOC approves Investigate the app grant and revoke unauthorized consent or app sessions using supported controls on paper but has not tested its operation.
- The unauthorized grant is removed and follow-up app activity stops
- The team schedules a future check of whether the unauthorized grant is removed and follow-up app activity stops, without recording any observed result.
Explanation
Correct Answer
C:Correct observed evidence. The unauthorized grant is removed and follow-up app activity stops. Given the original requirement, that result would substantiate the selected action, Investigate the app grant and revoke unauthorized consent or app sessions using supported controls.
Incorrect Answers
A:This observation fits another setting (A SOC wants to project a calculated risk flag for multiple events). It does not verify Investigate the app grant and revoke unauthorized consent or app sessions using supported controls against the original need.
B:Approval records intent but not actual protection or investigation. For An attacker registered an OAuth application granted unusually broad delegated permissions, an operational outcome must demonstrate that the unauthorized grant is removed and follow-up app activity stops.
D:A future validation plan is not an observed result. The actual verification should establish that the unauthorized grant is removed and follow-up app activity stops, in the scenario involving An attacker registered an OAuth application granted unusually broad delegated permissions.
Question 448
The original problem was: An attacker registered an OAuth application granted unusually broad delegated permissions. The solution is operating, but investigation reveals a compromised service principal credential too. What should change next?
- Reset only the mailbox display name and assume app authorization disappears
- Investigate the app grant and revoke unauthorized consent or app sessions using supported controls
- Derived fields have consistent types and expected values on sample rows
- Rotate or revoke the affected service principal credentials and audit further grants
Explanation
Correct Answer
D:Correct follow-up. The requirement changed to: Investigation reveals a compromised service principal credential too. Therefore Rotate or revoke the affected service principal credentials and audit further grants is appropriate for An attacker registered an OAuth application granted unusually broad delegated permissions, in addition to the previous measure.
Incorrect Answers
A:This was already unsuitable under the original condition because cosmetic user changes do not revoke a malicious application grant. It also fails after the change affecting An attacker registered an OAuth application granted unusually broad delegated permissions.
B:This was the original control already implemented: Investigate the app grant and revoke unauthorized consent or app sessions using supported controls. Its original rationale was: OAuth consent abuse can persist through application permissions independent of a user's password. For the initial setting (An attacker registered an OAuth application granted unusually broad delegated permissions), that does not itself meet the new condition: Investigation reveals a compromised service principal credential too.
C:An observation is not the additional configuration or response action requested. The change is Investigation reveals a compromised service principal credential too, so the proper follow-up must address it rather than merely note Derived fields have consistent types and expected values on sample rows.
Question 449
An analyst observes a suspicious third-party app accessing cloud files after new consent. Which configuration or investigation step is MOST appropriate?
- Investigate the app grant and revoke unauthorized consent or app sessions using supported controls
- Rotate or revoke the affected service principal credentials and audit further grants
- Reset only the mailbox display name and assume app authorization disappears
- Use a governed Sentinel data-lake KQL job for historical indicator matching
Explanation
Correct Answer
A:OAuth consent abuse can persist through application permissions independent of a user's password. The selected action is: Investigate the app grant and revoke unauthorized consent or app sessions using supported controls.
Incorrect Answers
B:This action would become suitable if a later condition arose: Investigation reveals a compromised service principal credential too. It is not the immediate answer to An analyst observes a suspicious third-party app accessing cloud files after new consent.
C:Cosmetic user changes do not revoke a malicious application grant. The shortcut Reset only the mailbox display name and assume app authorization disappears does not resolve the case involving An analyst observes a suspicious third-party app accessing cloud files after new consent.
D:That action serves a separate case (A security investigator has an IOC list and needs to look for matches in old lake records) in the Perform threat hunting domain. It does not specifically address the initial case.
Question 450
An analyst observes a suspicious third-party app accessing cloud files after new consent. Which statement BEST explains why the proposed approach (Reset only the mailbox display name and assume app authorization disappears) fails?
- NRT detection is not a supported substitute for historical lake jobs
- Cosmetic user changes do not revoke a malicious application grant
- A familiar product name alone establishes that the proposal is safe.
- OAuth consent abuse can persist through application permissions independent of a user's password
Explanation
Correct Answer
B:Cosmetic user changes do not revoke a malicious application grant. This directly explains the defect in Reset only the mailbox display name and assume app authorization disappears for An analyst observes a suspicious third-party app accessing cloud files after new consent.
Incorrect Answers
A:That concern applies to another security scenario (A security investigator has an IOC list and needs to look for matches in old lake records). Here, An analyst observes a suspicious third-party app accessing cloud files after new consent, the specified proposal fails because cosmetic user changes do not revoke a malicious application grant.
C:Product-name familiarity cannot validate a proposed security action. For An analyst observes a suspicious third-party app accessing cloud files after new consent, the actual issue is that cosmetic user changes do not revoke a malicious application grant.
D:This describes the reason for the preferred control, Investigate the app grant and revoke unauthorized consent or app sessions using supported controls: OAuth consent abuse can persist through application permissions independent of a user's password. It is not the direct defect in the proposed shortcut for An analyst observes a suspicious third-party app accessing cloud files after new consent.