Question 240A finance department wants to move from passwords to Windows Hello for Business on managed Windows devices. Which governance action most directly addresses the recurring risk? Include device compliance and credential recovery in rollout planning. Review MFA registration and policy exceptions for high-risk accounts. Monitor identity sync health and document fallback during an outage. Document registration, recovery, and lost-device procedures for passwordless methods. ExplanationCorrect Answer A:Include device compliance and credential recovery in rollout planning. Maintaining this control reduces recurrence because: Device-bound cryptographic credentials can authenticate a user without transmitting a reusable account password. The immediate response remains: Deploy the supported Windows Hello for Business key or certificate trust configuration and enrollment. Other Answers B:MFA combines different authentication factors, reducing dependence on a stolen password alone. The stronger recurring control is to include device compliance and credential recovery in rollout planning. C:Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. Reducing this risk requires a practice to include device compliance and credential recovery in rollout planning. D:Passwordless authentication substitutes strong cryptographic proof or device-bound credentials for a reusable account password. The stronger recurring control is to include device compliance and credential recovery in rollout planning.
Question 241A company asks users to approve an MFA request on an unknown phone because their employee password was already valid. Which action most directly resolves the security or identity requirement? Use supported number matching and contextual notifications, along with appropriate MFA protections. Enable the supported Microsoft Entra MFA methods and an appropriate enforcement policy. Use Entra access policy enforcement on the enterprise application where supported. Reject the unrecognized authentication prompt and investigate the associated sign-in attempt. ExplanationCorrect Answer D:An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. To confirm, inspect sign-in details and confirm no successful authentication occurred from the suspicious source. Other Answers A:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. The corrective action for this requirement is to reject the unrecognized authentication prompt and investigate the associated sign-in attempt. B:MFA combines different authentication factors, reducing dependence on a stolen password alone. A more relevant action is to reject the unrecognized authentication prompt and investigate the associated sign-in attempt. C:Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. The corrective action for this requirement is to reject the unrecognized authentication prompt and investigate the associated sign-in attempt.
Question 242A company asks users to approve an MFA request on an unknown phone because their employee password was already valid. Which technical distinction is decisive in this case? An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. MFA combines different authentication factors, reducing dependence on a stolen password alone. Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. ExplanationCorrect Answer A:An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. This is the principle behind: Reject the unrecognized authentication prompt and investigate the associated sign-in attempt. The evidence to inspect is: Inspect sign-in details and confirm no successful authentication occurred from the suspicious source. Other Answers B:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. By contrast, an unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. C:MFA combines different authentication factors, reducing dependence on a stolen password alone. In the stated system, an unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. D:Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. By contrast, an unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve.
Question 243A company asks users to approve an MFA request on an unknown phone because their employee password was already valid. Which observation best validates the chosen approach? Attempt the app sign-in before and after enabling a targeted policy and confirm a second factor is required. Sign in from a test user and confirm the required second factor is challenged. Trigger a controlled test prompt and verify the user sees sufficient matching context. Inspect sign-in details and confirm no successful authentication occurred from the suspicious source. ExplanationCorrect Answer D:Inspect sign-in details and confirm no successful authentication occurred from the suspicious source. This test checks the expected result of: Reject the unrecognized authentication prompt and investigate the associated sign-in attempt. It matters because: An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. Other Answers A:Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. The relevant acceptance check is to inspect sign-in details and confirm no successful authentication occurred from the suspicious source. B:MFA combines different authentication factors, reducing dependence on a stolen password alone. A more meaningful verification is to inspect sign-in details and confirm no successful authentication occurred from the suspicious source. C:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. The relevant acceptance check is to inspect sign-in details and confirm no successful authentication occurred from the suspicious source.
Question 244A company asks users to approve an MFA request on an unknown phone because their employee password was already valid. Which governance action most directly addresses the recurring risk? Train employees to report unexpected challenges and monitor MFA fatigue patterns. Review MFA push abuse signals and educate users not to approve unknown prompts. Review MFA registration and policy exceptions for high-risk accounts. Review app assignment and Conditional Access policy scope together. ExplanationCorrect Answer A:Train employees to report unexpected challenges and monitor MFA fatigue patterns. Maintaining this control reduces recurrence because: An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. The immediate response remains: Reject the unrecognized authentication prompt and investigate the associated sign-in attempt. Other Answers B:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. Reducing this risk requires a practice to train employees to report unexpected challenges and monitor MFA fatigue patterns. C:MFA combines different authentication factors, reducing dependence on a stolen password alone. The stronger recurring control is to train employees to report unexpected challenges and monitor MFA fatigue patterns. D:Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. Reducing this risk requires a practice to train employees to report unexpected challenges and monitor MFA fatigue patterns.
Question 245A school enables SSPR for students but discovers users cannot complete resets because registration was never required. Which action most directly resolves the security or identity requirement? Run a supported authentication-method registration campaign and confirm enrollment coverage. Deploy the supported Windows Hello for Business key or certificate trust configuration and enrollment. Secure authentication-method registration with appropriate identity verification and risk controls. Review and restrict authentication methods and registration as required by the new security policy. ExplanationCorrect Answer A:SSPR depends on the user having enrolled eligible verification methods before an outage. To confirm, check registration status for a representative student cohort and complete a reset test. Other Answers B:Device-bound cryptographic credentials can authenticate a user without transmitting a reusable account password. This failure calls for a decision to run a supported authentication-method registration campaign and confirm enrollment coverage. C:Method registration is a sensitive identity change, not just a low-risk user preference. A more relevant action is to run a supported authentication-method registration campaign and confirm enrollment coverage. D:Registered factors and permitted authentication method policies are separately governed. This failure calls for a decision to run a supported authentication-method registration campaign and confirm enrollment coverage.
Question 246A school enables SSPR for students but discovers users cannot complete resets because registration was never required. Which technical distinction is decisive in this case? Registered factors and permitted authentication method policies are separately governed. Method registration is a sensitive identity change, not just a low-risk user preference. Device-bound cryptographic credentials can authenticate a user without transmitting a reusable account password. SSPR depends on the user having enrolled eligible verification methods before an outage. ExplanationCorrect Answer D:SSPR depends on the user having enrolled eligible verification methods before an outage. This is the principle behind: Run a supported authentication-method registration campaign and confirm enrollment coverage. The evidence to inspect is: Check registration status for a representative student cohort and complete a reset test. Other Answers A:Registered factors and permitted authentication method policies are separately governed. In the stated system, SSPR depends on the user having enrolled eligible verification methods before an outage. B:Method registration is a sensitive identity change, not just a low-risk user preference. By contrast, SSPR depends on the user having enrolled eligible verification methods before an outage. C:Device-bound cryptographic credentials can authenticate a user without transmitting a reusable account password. In the stated system, SSPR depends on the user having enrolled eligible verification methods before an outage.
Question 247A school enables SSPR for students but discovers users cannot complete resets because registration was never required. Which observation best validates the chosen approach? Use a test account with a deprecated method and confirm it cannot satisfy the new requirement. Provision a test device and verify user authentication and key lifecycle through a reset. Check registration status for a representative student cohort and complete a reset test. Attempt to register a new factor through an unauthorized flow and verify additional verification is required. ExplanationCorrect Answer C:Check registration status for a representative student cohort and complete a reset test. This test checks the expected result of: Run a supported authentication-method registration campaign and confirm enrollment coverage. It matters because: SSPR depends on the user having enrolled eligible verification methods before an outage. Other Answers A:Registered factors and permitted authentication method policies are separately governed. A more meaningful verification is to check registration status for a representative student cohort and complete a reset test. B:Device-bound cryptographic credentials can authenticate a user without transmitting a reusable account password. A more meaningful verification is to check registration status for a representative student cohort and complete a reset test. D:Method registration is a sensitive identity change, not just a low-risk user preference. The failure is checked more directly by a test to check registration status for a representative student cohort and complete a reset test.
Question 248A school enables SSPR for students but discovers users cannot complete resets because registration was never required. Which governance action most directly addresses the recurring risk? Review registered methods at policy changes and during external-user offboarding. Include device compliance and credential recovery in rollout planning. Monitor authentication method change audit events and notify account owners. Track method registration completeness during onboarding. ExplanationCorrect Answer D:Track method registration completeness during onboarding. Maintaining this control reduces recurrence because: SSPR depends on the user having enrolled eligible verification methods before an outage. The immediate response remains: Run a supported authentication-method registration campaign and confirm enrollment coverage. Other Answers A:Registered factors and permitted authentication method policies are separately governed. The stronger recurring control is to track method registration completeness during onboarding. B:Device-bound cryptographic credentials can authenticate a user without transmitting a reusable account password. The stronger recurring control is to track method registration completeness during onboarding. C:Method registration is a sensitive identity change, not just a low-risk user preference. A more direct preventive measure is to track method registration completeness during onboarding.
Question 249A SaaS application requires only a password today, and the tenant wants to enforce MFA for its use without changing the application's code. Which action most directly resolves the security or identity requirement? Use Entra access policy enforcement on the enterprise application where supported. Configure an authentication strength requiring a supported phishing-resistant method for the protected app. Enable the supported Microsoft Entra MFA methods and an appropriate enforcement policy. Plan the supported password hash synchronization or alternative hybrid sign-in method. ExplanationCorrect Answer A:Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. To confirm, attempt the app sign-in before and after enabling a targeted policy and confirm a second factor is required. Other Answers B:Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. The corrective action for this requirement is to use Entra access policy enforcement on the enterprise application where supported. C:MFA combines different authentication factors, reducing dependence on a stolen password alone. The corrective action for this requirement is to use Entra access policy enforcement on the enterprise application where supported. D:Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. This failure calls for a decision to use Entra access policy enforcement on the enterprise application where supported.
Question 250A SaaS application requires only a password today, and the tenant wants to enforce MFA for its use without changing the application's code. Which technical distinction is decisive in this case? Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. MFA combines different authentication factors, reducing dependence on a stolen password alone. Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. ExplanationCorrect Answer C:Identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. This is the principle behind: Use Entra access policy enforcement on the enterprise application where supported. The evidence to inspect is: Attempt the app sign-in before and after enabling a targeted policy and confirm a second factor is required. Other Answers A:Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. By contrast, identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. B:MFA combines different authentication factors, reducing dependence on a stolen password alone. By contrast, identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application. D:Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. In the stated system, identity-provider policy can require MFA at the sign-in boundary without rewriting every relying application.