Practice Exams:

Microsoft SC-900 Dumps

EXAM: Microsoft Security, Compliance, and Identity Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

SC-900 Premium Bundle


  • Premium File 259 Questions & Answers
  • Training Course 147 Lectures
  • Study Guide 413 Pages

Microsoft SC-900 Practice Test 27

Question 260

A small business enforces a password and a favorite-color challenge but needs to understand why its account protection is not MFA. Which action and validation evidence belong together?

  1. Action: Deploy supported Windows Hello for Business or platform passkeys where suitable and keep resource authorization decisions separate from the authentication method. Validation: Compare a test user's successful Hello sign-in with a denied attempt to administer a restricted directory role that the account was never assigned.
  2. Action: Use supported passkeys or FIDO2 security keys for users needing phishing-resistant passwordless sign-in instead of relying only on reusable knowledge secrets. Validation: Sign in a test account with a registered security key and verify an untrusted lookalike site cannot produce a valid origin-bound authentication response.
  3. Action: Configure the appropriate Entra authentication methods policy and registration campaign so users can enroll only supported factors allowed by organizational policy. Validation: Check method-policy eligibility for two synthetic groups, register an approved factor and verify an excluded group cannot enroll a restricted method.
  4. Action: Require two or more independent authentication factor categories, such as a password and registered device proof, for sensitive sign-ins. Validation: Test a protected account's sign-in and record that a separate possession or inherence factor is required in addition to its knowledge secret.

Explanation

Correct Answer

D:

The situation is that a small business enforces a password and a favorite-color challenge but needs to understand why its account protection is not MFA. Require two or more independent authentication factor categories, such as a password and registered device proof, for sensitive sign-ins. Validation: Test a protected account's sign-in and record that a separate possession or inherence factor is required in addition to its knowledge secret. The action and test belong together because two passwords or a password plus PIN are both knowledge factors and do not provide the independent assurance of genuine multifactor authentication.

Incorrect Answers

A:

That action-and-evidence pair concerns “use passwordless sign-in without assuming authorization grants”, not this decision. The appropriate action is to require two or more independent authentication factor categories, such as a password and registered device proof, for sensitive sign-ins. To confirm, test a protected account's sign-in and record that a separate possession or inherence factor is required in addition to its knowledge secret.

B:

The proposed pair focuses on “choose phishing-resistant authentication methods where required” instead. The appropriate action is to require two or more independent authentication factor categories, such as a password and registered device proof, for sensitive sign-ins. To confirm, test a protected account's sign-in and record that a separate possession or inherence factor is required in addition to its knowledge secret.

C:

“set authentication method policies for approved factors” evaluates a different intervention. The appropriate action is to require two or more independent authentication factor categories, such as a password and registered device proof, for sensitive sign-ins. To confirm, test a protected account's sign-in and record that a separate possession or inherence factor is required in addition to its knowledge secret.

Question 261

For this cloud security and identity case, A payroll worker receives a flood of unexpected push prompts after a phishing campaign and management needs to improve Authenticator usage. What is the most appropriate next decision?

  1. Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept.
  2. Configure the appropriate Entra authentication methods policy and registration campaign so users can enroll only supported factors allowed by organizational policy.
  3. Deploy supported Windows Hello for Business or platform passkeys where suitable and keep resource authorization decisions separate from the authentication method.
  4. Use supported passkeys or FIDO2 security keys for users needing phishing-resistant passwordless sign-in instead of relying only on reusable knowledge secrets.

Explanation

Correct Answer

A:

Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks. To verify, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Incorrect Answers

B:

“set authentication method policies for approved factors” is related to another task, not the failure shown here. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

C:

This alternative focuses on “use passwordless sign-in without assuming authorization grants” instead of the required outcome. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

D:

That choice concerns “choose phishing-resistant authentication methods where required”, not the immediate requirement. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Question 262

A payroll worker receives a flood of unexpected push prompts after a phishing campaign and management needs to improve Authenticator usage. Why does the recommended approach address this particular concern?

  1. Passwordless sign-in changes how the user proves identity but does not confer additional access rights or eliminate policy evaluation for resources.
  2. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.
  3. Authentication methods availability is governed by tenant policy and user targeting, not merely by a user installing an authenticator app.
  4. FIDO2 public-key authentication binds cryptographic proof to the legitimate relying party origin, reducing phishing and password replay exposure.

Explanation

Correct Answer

B:

Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks. This supports the decision to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept.

Incorrect Answers

A:

The principle behind “use passwordless sign-in without assuming authorization grants” is not the one being tested. Here, number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

C:

“set authentication method policies for approved factors” explains a different mechanism. Here, number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

D:

That statement concerns “choose phishing-resistant authentication methods where required” rather than the cause in this case. Here, number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Question 263

A payroll worker receives a flood of unexpected push prompts after a phishing campaign and management needs to improve Authenticator usage. Which evidence best validates the proposed outcome?

  1. Test a protected account's sign-in and record that a separate possession or inherence factor is required in addition to its knowledge secret.
  2. Issue a test pass with configured expiry, register a permitted strong method, and verify reuse and expiration follow the chosen configuration.
  3. Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.
  4. Attempt to set a known weak test password or an organization-themed variation and verify the policy rejects it during the supported change path.

Explanation

Correct Answer

C:

Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected. It is the relevant test because number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Incorrect Answers

A:

“explain multifactor authentication as independent factor categories” would verify a different part of the system. To check this result, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

B:

That test concerns “use temporary access pass for supported onboarding and recovery”, not the requested outcome. To check this result, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

D:

This evidence addresses “apply Microsoft entra password protection and banned-password rules” instead of confirming the repair. To check this result, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Question 264

Consider this situation: A payroll worker receives a flood of unexpected push prompts after a phishing campaign and management needs to improve Authenticator usage. A team member suggests: "Tell staff to approve repeated unexpected Authenticator notifications quickly so their phone stops vibrating." What is the main risk?

  1. Compromise of one knowledge-based credential source may satisfy both prompts and leave the account exposed despite a claim of MFA.
  2. Password spraying can succeed against common predictable choices despite user awareness campaigns and regular forced changes.
  3. A strongly authenticated employee could gain unintended resource permissions if the system wrongly conflates strong identity proof with authorization.
  4. A victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

Explanation

Correct Answer

D:

A victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests. The shortcut is unsafe because number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Incorrect Answers

A:

That consequence concerns “Compromise of one knowledge-based credential source may satisfy both prompts and leave the account exposed despite…”, which is a different failure. Here, a victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

B:

“Password spraying can succeed against common predictable choices despite user awareness campaigns and regular forced changes” does not describe the result of this shortcut. Here, a victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

C:

The alternative risk relates to “A strongly authenticated employee could gain unintended resource permissions if the system wrongly conflates strong identity…”, not the stated mistake. Here, a victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

Question 265

A security and compliance reviewer considers: A payroll worker receives a flood of unexpected push prompts after a phishing campaign and management needs to improve Authenticator usage. Which response and evidence should be linked?

  1. Action: Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Validation: Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.
  2. Action: Use Entra Password Protection and suitable custom banned-password lists to prevent commonly guessed or organization-themed passwords where supported. Validation: Attempt to set a known weak test password or an organization-themed variation and verify the policy rejects it during the supported change path.
  3. Action: Use supported passkeys or FIDO2 security keys for users needing phishing-resistant passwordless sign-in instead of relying only on reusable knowledge secrets. Validation: Sign in a test account with a registered security key and verify an untrusted lookalike site cannot produce a valid origin-bound authentication response.
  4. Action: Issue a time-limited Temporary Access Pass through authorized policy for a supported user recovery or initial passwordless registration workflow. Validation: Issue a test pass with configured expiry, register a permitted strong method, and verify reuse and expiration follow the chosen configuration.

Explanation

Correct Answer

A:

Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Validation: Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected. The action and test belong together because number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Incorrect Answers

B:

“apply Microsoft entra password protection and banned-password rules” evaluates a different intervention. The appropriate action is to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. To confirm, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

C:

The linked action and check for “choose phishing-resistant authentication methods where required” would not resolve this case. The appropriate action is to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. To confirm, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

D:

That action-and-evidence pair concerns “use temporary access pass for supported onboarding and recovery”, not this decision. The appropriate action is to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. To confirm, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Question 266

An employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. Which action best addresses this requirement?

  1. Configure Microsoft Entra self-service password reset with supported authentication methods and registration requirements appropriate to user risk.
  2. Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept.
  3. Use Entra Password Protection and suitable custom banned-password lists to prevent commonly guessed or organization-themed passwords where supported.
  4. Require two or more independent authentication factor categories, such as a password and registered device proof, for sensitive sign-ins.

Explanation

Correct Answer

B:

The situation is that an employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks. To verify, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Incorrect Answers

A:

“enable self-service password reset with adequate identity verification” is related to another task, not the failure shown here. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

C:

That choice concerns “apply Microsoft entra password protection and banned-password rules”, not the immediate requirement. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

D:

The proposed action addresses “explain multifactor authentication as independent factor categories” rather than the problem described. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Question 267

A cloud security learner considers: An employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. Which underlying principle applies?

  1. Banned-password screening addresses weak and predictable strings at creation or change time, complementing MFA rather than replacing it.
  2. FIDO2 public-key authentication binds cryptographic proof to the legitimate relying party origin, reducing phishing and password replay exposure.
  3. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.
  4. Two passwords or a password plus PIN are both knowledge factors and do not provide the independent assurance of genuine multifactor authentication.

Explanation

Correct Answer

C:

The situation is that an employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. Number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks. This supports the decision to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept.

Incorrect Answers

A:

“apply Microsoft entra password protection and banned-password rules” describes another technical distinction. Here, number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

B:

“choose phishing-resistant authentication methods where required” explains a different mechanism. Here, number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

D:

The principle behind “explain multifactor authentication as independent factor categories” is not the one being tested. Here, number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Question 268

An employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. What should the team examine before accepting the result?

  1. Attempt to set a known weak test password or an organization-themed variation and verify the policy rejects it during the supported change path.
  2. Compare a test user's successful Hello sign-in with a denied attempt to administer a restricted directory role that the account was never assigned.
  3. Reset a sandbox user's password through its registered recovery factors and confirm an unregistered stranger cannot complete the same flow.
  4. Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Explanation

Correct Answer

D:

The situation is that an employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected. It is the relevant test because number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Incorrect Answers

A:

That test concerns “apply Microsoft entra password protection and banned-password rules”, not the requested outcome. To check this result, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

B:

The proposed check is relevant to “use passwordless sign-in without assuming authorization grants”, but not sufficient here. To check this result, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

C:

This evidence addresses “enable self-service password reset with adequate identity verification” instead of confirming the repair. To check this result, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Question 269

An employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. The proposed shortcut is: "Tell staff to approve repeated unexpected Authenticator notifications quickly so their phone stops vibrating." Which failure is most likely?

  1. A victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.
  2. An attacker may seize user accounts by abusing weak password recovery, even though ordinary interactive sign-in requires MFA.
  3. Rollouts may fail or violate policy when method enrollment and group targeting do not match the approved authentication requirements.
  4. An attacker may steal and immediately replay credentials collected by a realistic phishing proxy despite the presence of ordinary one-time codes.

Explanation

Correct Answer

A:

The situation is that an employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. A victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests. The shortcut is unsafe because number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Incorrect Answers

B:

The alternative risk relates to “An attacker may seize user accounts by abusing weak password recovery, even though ordinary interactive sign-in…”, not the stated mistake. Here, a victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

C:

“Rollouts may fail or violate policy when method enrollment and group targeting do not match the…” can arise elsewhere, but it is not the most direct risk here. Here, a victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

D:

That consequence concerns “An attacker may steal and immediately replay credentials collected by a realistic phishing proxy despite the…”, which is a different failure. Here, a victim may approve an attacker's sign-in through MFA fatigue if alerts lack context and training to deny unauthorized requests.

Question 270

For this case—An employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent.—which implementation and acceptance check are correctly paired?

  1. Action: Deploy supported Windows Hello for Business or platform passkeys where suitable and keep resource authorization decisions separate from the authentication method. Validation: Compare a test user's successful Hello sign-in with a denied attempt to administer a restricted directory role that the account was never assigned.
  2. Action: Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Validation: Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.
  3. Action: Use Entra Password Protection and suitable custom banned-password lists to prevent commonly guessed or organization-themed passwords where supported. Validation: Attempt to set a known weak test password or an organization-themed variation and verify the policy rejects it during the supported change path.
  4. Action: Configure the appropriate Entra authentication methods policy and registration campaign so users can enroll only supported factors allowed by organizational policy. Validation: Check method-policy eligibility for two synthetic groups, register an approved factor and verify an excluded group cannot enroll a restricted method.

Explanation

Correct Answer

B:

The situation is that an employee routinely approves sign-in prompts without a browser session while the organization claims every push indicates genuine consent. Enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. Validation: Trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected. The action and test belong together because number matching requires the user to confirm the value shown in the genuine sign-in flow, countering simple approval fatigue attacks.

Incorrect Answers

A:

“use passwordless sign-in without assuming authorization grants” evaluates a different intervention. The appropriate action is to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. To confirm, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

C:

That action-and-evidence pair concerns “apply Microsoft entra password protection and banned-password rules”, not this decision. The appropriate action is to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. To confirm, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

D:

The proposed pair focuses on “set authentication method policies for approved factors” instead. The appropriate action is to enable supported Microsoft Authenticator push prompts with number matching and user context to make fraudulent approval attempts harder to accept. To confirm, trigger a controlled sign-in, check the matching number on the authentic request, and verify an unsolicited prompt is explicitly rejected.

Microsoft Security, Compliance, and Identity Fundamentals (SC-900) Practice Tests