Microsoft SC-200 Practice Test 46
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.
Question 451
An analyst observes a suspicious third-party app accessing cloud files after new consent. Which operational finding would validate the selected solution, Investigate the app grant and revoke unauthorized consent or app sessions using supported controls?
- The team schedules a future check of whether the unauthorized grant is removed and follow-up app activity stops, without recording any observed result.
- The job yields auditable matches and nonmatches for the selected indicator set
- The unauthorized grant is removed and follow-up app activity stops
- 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.
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: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 analyst observes a suspicious third-party app accessing cloud files after new consent.
B:This observation fits another setting (A security investigator has an IOC list and needs to look for matches in old lake records). It does not verify Investigate the app grant and revoke unauthorized consent or app sessions using supported controls against the original need.
D:Approval records intent but not actual protection or investigation. For An analyst observes a suspicious third-party app accessing cloud files after new consent, an operational outcome must demonstrate that the unauthorized grant is removed and follow-up app activity stops.
Question 452
An analyst observes a suspicious third-party app accessing cloud files after new consent. After the initial control is implemented, investigation reveals a compromised service principal credential too. What is the best follow-up action?
- Investigate the app grant and revoke unauthorized consent or app sessions using supported controls
- Reset only the mailbox display name and assume app authorization disappears
- The unauthorized grant is removed and follow-up app activity stops
- 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 analyst observes a suspicious third-party app accessing cloud files after new consent, in addition to the previous measure.
Incorrect Answers
A: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 analyst observes a suspicious third-party app accessing cloud files after new consent), that does not itself meet the new condition: Investigation reveals a compromised service principal credential too.
B: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 analyst observes a suspicious third-party app accessing cloud files after new consent.
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 The unauthorized grant is removed and follow-up app activity stops.
Question 453
A user generates risky sign-ins from unfamiliar locations and devices. Which action BEST addresses this Microsoft security operations requirement?
- Investigate Microsoft Entra risky user and sign-in details before targeted remediation
- Revoke sessions and enforce appropriate identity protection response
- Close the case solely because the password was recently changed
- Query Defender XDR DeviceNetworkEvents for remote-address and initiating-process context
Explanation
Correct Answer
A:Entra identity-risk evidence connects suspicious sign-ins with account and session indicators. The selected action is: Investigate Microsoft Entra risky user and sign-in details before targeted remediation.
Incorrect Answers
B:This action would become suitable if a later condition arose: A valid user session is confirmed stolen. It is not the immediate answer to A user generates risky sign-ins from unfamiliar locations and devices.
C:Password age alone does not exclude stolen active tokens or ongoing abuse. The shortcut Close the case solely because the password was recently changed does not resolve the case involving A user generates risky sign-ins from unfamiliar locations and devices.
D:That action serves a separate case (A SOC asks which endpoint process opened connections to a listed external IP) in the Perform threat hunting domain. It does not specifically address the initial case.
Question 454
A user generates risky sign-ins from unfamiliar locations and devices. A colleague suggests: Close the case solely because the password was recently changed. What is the MOST important technical defect in this suggestion?
- File-operation events do not directly establish remote connection attempts
- Entra identity-risk evidence connects suspicious sign-ins with account and session indicators
- A familiar product name alone establishes that the proposal is safe.
- Password age alone does not exclude stolen active tokens or ongoing abuse
Explanation
Correct Answer
D:Password age alone does not exclude stolen active tokens or ongoing abuse. This directly explains the defect in Close the case solely because the password was recently changed for A user generates risky sign-ins from unfamiliar locations and devices.
Incorrect Answers
A:That concern applies to another security scenario (A SOC asks which endpoint process opened connections to a listed external IP). Here, A user generates risky sign-ins from unfamiliar locations and devices, the specified proposal fails because password age alone does not exclude stolen active tokens or ongoing abuse.
B:This describes the reason for the preferred control, Investigate Microsoft Entra risky user and sign-in details before targeted remediation: Entra identity-risk evidence connects suspicious sign-ins with account and session indicators. It is not the direct defect in the proposed shortcut for A user generates risky sign-ins from unfamiliar locations and devices.
C:Product-name familiarity cannot validate a proposed security action. For A user generates risky sign-ins from unfamiliar locations and devices, the actual issue is that password age alone does not exclude stolen active tokens or ongoing abuse.
Question 455
A user generates risky sign-ins from unfamiliar locations and devices. After implementing Investigate Microsoft Entra risky user and sign-in details before targeted remediation, what result would BEST establish that it worked?
- Matching events show remote IP, device and initiating executable
- Correlated risk and sign-in events establish scope and remediation outcome
- The team schedules a future check of whether correlated risk and sign-in events establish scope and remediation outcome, without recording any observed result.
- The SOC approves Investigate Microsoft Entra risky user and sign-in details before targeted remediation on paper but has not tested its operation.
Explanation
Correct Answer
B:Correct observed evidence. Correlated risk and sign-in events establish scope and remediation outcome. Given the original requirement, that result would substantiate the selected action, Investigate Microsoft Entra risky user and sign-in details before targeted remediation.
Incorrect Answers
A:This observation fits another setting (A SOC asks which endpoint process opened connections to a listed external IP). It does not verify Investigate Microsoft Entra risky user and sign-in details before targeted remediation against the original need.
C:A future validation plan is not an observed result. The actual verification should establish that correlated risk and sign-in events establish scope and remediation outcome, in the scenario involving A user generates risky sign-ins from unfamiliar locations and devices.
D:Approval records intent but not actual protection or investigation. For A user generates risky sign-ins from unfamiliar locations and devices, an operational outcome must demonstrate that correlated risk and sign-in events establish scope and remediation outcome.
Question 456
A user generates risky sign-ins from unfamiliar locations and devices. The original measure is in place. A new requirement arises: A valid user session is confirmed stolen. Which ADDITIONAL action BEST fits?
- Revoke sessions and enforce appropriate identity protection response
- Matching events show remote IP, device and initiating executable
- Close the case solely because the password was recently changed
- Investigate Microsoft Entra risky user and sign-in details before targeted remediation
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: A valid user session is confirmed stolen. Therefore Revoke sessions and enforce appropriate identity protection response is appropriate for A user generates risky sign-ins from unfamiliar locations and devices, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is A valid user session is confirmed stolen, so the proper follow-up must address it rather than merely note Matching events show remote IP, device and initiating executable.
C:This was already unsuitable under the original condition because password age alone does not exclude stolen active tokens or ongoing abuse. It also fails after the change affecting A user generates risky sign-ins from unfamiliar locations and devices.
D:This was the original control already implemented: Investigate Microsoft Entra risky user and sign-in details before targeted remediation. Its original rationale was: Entra identity-risk evidence connects suspicious sign-ins with account and session indicators. For the initial setting (A user generates risky sign-ins from unfamiliar locations and devices), that does not itself meet the new condition: A valid user session is confirmed stolen.
Question 457
A security operations analyst must handle this situation: An identity SOC sees identity protection flags for a suspected stolen session. What is the BEST initial response?
- Close the case solely because the password was recently changed
- Revoke sessions and enforce appropriate identity protection response
- Investigate Microsoft Entra risky user and sign-in details before targeted remediation
- Use KQL arg_max on the timestamp while grouping by the device identifier
Explanation
Correct Answer
C:Entra identity-risk evidence connects suspicious sign-ins with account and session indicators. The selected action is: Investigate Microsoft Entra risky user and sign-in details before targeted remediation.
Incorrect Answers
A:Password age alone does not exclude stolen active tokens or ongoing abuse. The shortcut Close the case solely because the password was recently changed does not resolve the case involving An identity SOC sees identity protection flags for a suspected stolen session.
B:This action would become suitable if a later condition arose: A valid user session is confirmed stolen. It is not the immediate answer to An identity SOC sees identity protection flags for a suspected stolen session.
D:That action serves a separate case (A SOC needs the latest device observation per hostname in KQL) in the Perform threat hunting domain. It does not specifically address the initial case.
Question 458
An identity SOC sees identity protection flags for a suspected stolen session. Why should the SOC reject the proposed shortcut: Close the case solely because the password was recently changed?
- Password age alone does not exclude stolen active tokens or ongoing abuse
- A familiar product name alone establishes that the proposal is safe.
- An arbitrary row is not equivalent to last known state per entity
- Entra identity-risk evidence connects suspicious sign-ins with account and session indicators
Explanation
Correct Answer
A:Password age alone does not exclude stolen active tokens or ongoing abuse. This directly explains the defect in Close the case solely because the password was recently changed for An identity SOC sees identity protection flags for a suspected stolen session.
Incorrect Answers
B:Product-name familiarity cannot validate a proposed security action. For An identity SOC sees identity protection flags for a suspected stolen session, the actual issue is that password age alone does not exclude stolen active tokens or ongoing abuse.
C:That concern applies to another security scenario (A SOC needs the latest device observation per hostname in KQL). Here, An identity SOC sees identity protection flags for a suspected stolen session, the specified proposal fails because password age alone does not exclude stolen active tokens or ongoing abuse.
D:This describes the reason for the preferred control, Investigate Microsoft Entra risky user and sign-in details before targeted remediation: Entra identity-risk evidence connects suspicious sign-ins with account and session indicators. It is not the direct defect in the proposed shortcut for An identity SOC sees identity protection flags for a suspected stolen session.
Question 459
An identity SOC sees identity protection flags for a suspected stolen session. The SOC implements Investigate Microsoft Entra risky user and sign-in details before targeted remediation. Which observed result provides credible confirmation?
- Correlated risk and sign-in events establish scope and remediation outcome
- Each device appears once with its verified newest timestamp
- The team schedules a future check of whether correlated risk and sign-in events establish scope and remediation outcome, without recording any observed result.
- The SOC approves Investigate Microsoft Entra risky user and sign-in details before targeted remediation on paper but has not tested its operation.
Explanation
Correct Answer
A:Correct observed evidence. Correlated risk and sign-in events establish scope and remediation outcome. Given the original requirement, that result would substantiate the selected action, Investigate Microsoft Entra risky user and sign-in details before targeted remediation.
Incorrect Answers
B:This observation fits another setting (A SOC needs the latest device observation per hostname in KQL). It does not verify Investigate Microsoft Entra risky user and sign-in details before targeted remediation against the original need.
C:A future validation plan is not an observed result. The actual verification should establish that correlated risk and sign-in events establish scope and remediation outcome, in the scenario involving An identity SOC sees identity protection flags for a suspected stolen session.
D:Approval records intent but not actual protection or investigation. For An identity SOC sees identity protection flags for a suspected stolen session, an operational outcome must demonstrate that correlated risk and sign-in events establish scope and remediation outcome.
Question 460
The original problem was: An identity SOC sees identity protection flags for a suspected stolen session. The solution is operating, but a valid user session is confirmed stolen. What should change next?
- Revoke sessions and enforce appropriate identity protection response
- Correlated risk and sign-in events establish scope and remediation outcome
- Investigate Microsoft Entra risky user and sign-in details before targeted remediation
- Close the case solely because the password was recently changed
Explanation
Correct Answer
A:Correct follow-up. The requirement changed to: A valid user session is confirmed stolen. Therefore Revoke sessions and enforce appropriate identity protection response is appropriate for An identity SOC sees identity protection flags for a suspected stolen session, in addition to the previous measure.
Incorrect Answers
B:An observation is not the additional configuration or response action requested. The change is A valid user session is confirmed stolen, so the proper follow-up must address it rather than merely note Correlated risk and sign-in events establish scope and remediation outcome.
C:This was the original control already implemented: Investigate Microsoft Entra risky user and sign-in details before targeted remediation. Its original rationale was: Entra identity-risk evidence connects suspicious sign-ins with account and session indicators. For the initial setting (An identity SOC sees identity protection flags for a suspected stolen session), that does not itself meet the new condition: A valid user session is confirmed stolen.
D:This was already unsuitable under the original condition because password age alone does not exclude stolen active tokens or ongoing abuse. It also fails after the change affecting An identity SOC sees identity protection flags for a suspected stolen session.