Microsoft SC-900 Dumps
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?
Explanation
Correct Answer
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
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.
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.
“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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
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.
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?
Explanation
Correct Answer
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
“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.
“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.
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?
Explanation
Correct Answer
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
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.
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.
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?
Explanation
Correct Answer
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
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.
“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.
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?
Explanation
Correct Answer
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
“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.
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.
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
- Microsoft SC-900 Practice Test 25 - 10 Questions (Last Reviewed 27-Oct-2026)
- Microsoft SC-900 Practice Test 26 - 10 Questions (Last Reviewed 26-Oct-2026)
- Microsoft SC-900 Practice Test 27 - 10 Questions (Last Reviewed 25-Oct-2026)
- Microsoft SC-900 Practice Test 28 - 10 Questions (Last Reviewed 24-Oct-2026)
- Microsoft SC-900 Practice Test 29 - 10 Questions (Last Reviewed 23-Oct-2026)