Question 220A government agency requires a hardware-based sign-in method for a restricted application, but the current policy accepts any registered second factor. Which governance action most directly addresses the recurring risk? Require phishing-resistant factors for privileged roles and test break-glass procedures. Review registered methods at policy changes and during external-user offboarding. Maintain stronger authentication requirements for sensitive workloads. Monitor identity sync health and document fallback during an outage. ExplanationCorrect Answer C:Maintain stronger authentication requirements for sensitive workloads. Maintaining this control reduces recurrence because: Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. The immediate response remains: Configure an authentication strength requiring a supported phishing-resistant method for the protected app. Other Answers A:Phishing-resistant methods bind authentication to a legitimate origin more robustly than relayed SMS codes. A more direct preventive measure is to maintain stronger authentication requirements for sensitive workloads. B:Registered factors and permitted authentication method policies are separately governed. The lasting safeguard is to maintain stronger authentication requirements for sensitive workloads. D:Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. The lasting safeguard is to maintain stronger authentication requirements for sensitive workloads.
Question 221A business adopts Microsoft Authenticator push notifications without checking protection against accidental or fraudulent approval prompts. Which action most directly resolves the security or identity requirement? Use supported number matching and contextual notifications, along with appropriate MFA protections. Reject the unrecognized authentication prompt and investigate the associated sign-in attempt. Replace interactive user-based script authentication with an appropriate nonhuman identity. Enable the supported Microsoft Entra MFA methods and an appropriate enforcement policy. ExplanationCorrect Answer A:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. To confirm, trigger a controlled test prompt and verify the user sees sufficient matching context. Other Answers B:An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. This failure calls for a decision to use supported number matching and contextual notifications, along with appropriate MFA protections. C:Service principals and managed identities are designed for workload authentication without human MFA prompts. A more relevant action is to use supported number matching and contextual notifications, along with appropriate MFA protections. D:MFA combines different authentication factors, reducing dependence on a stolen password alone. The corrective action for this requirement is to use supported number matching and contextual notifications, along with appropriate MFA protections.
Question 222A business adopts Microsoft Authenticator push notifications without checking protection against accidental or fraudulent approval prompts. Which technical distinction is decisive in this case? A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. Service principals and managed identities are designed for workload authentication without human MFA prompts. MFA combines different authentication factors, reducing dependence on a stolen password alone. An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. ExplanationCorrect Answer A:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. This is the principle behind: Use supported number matching and contextual notifications, along with appropriate MFA protections. The evidence to inspect is: Trigger a controlled test prompt and verify the user sees sufficient matching context. Other Answers B:Service principals and managed identities are designed for workload authentication without human MFA prompts. In the stated system, a push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. C:MFA combines different authentication factors, reducing dependence on a stolen password alone. In the stated system, a push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. D:An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. By contrast, a push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks.
Question 223A business adopts Microsoft Authenticator push notifications without checking protection against accidental or fraudulent approval prompts. Which observation best validates the chosen approach? Inspect sign-in details and confirm no successful authentication occurred from the suspicious source. Trigger a controlled test prompt and verify the user sees sufficient matching context. Sign in from a test user and confirm the required second factor is challenged. Run the job with its workload credential and confirm it no longer needs a human challenge. ExplanationCorrect Answer B:Trigger a controlled test prompt and verify the user sees sufficient matching context. This test checks the expected result of: Use supported number matching and contextual notifications, along with appropriate MFA protections. It matters because: A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. Other Answers A:An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. Proving this correction calls for a check to trigger a controlled test prompt and verify the user sees sufficient matching context. C:MFA combines different authentication factors, reducing dependence on a stolen password alone. The failure is checked more directly by a test to trigger a controlled test prompt and verify the user sees sufficient matching context. D:Service principals and managed identities are designed for workload authentication without human MFA prompts. The relevant acceptance check is to trigger a controlled test prompt and verify the user sees sufficient matching context.
Question 224A business adopts Microsoft Authenticator push notifications without checking protection against accidental or fraudulent approval prompts. Which governance action most directly addresses the recurring risk? Train employees to report unexpected challenges and monitor MFA fatigue patterns. Review MFA registration and policy exceptions for high-risk accounts. Review MFA push abuse signals and educate users not to approve unknown prompts. Block shared human accounts in unattended automation. ExplanationCorrect Answer C:Review MFA push abuse signals and educate users not to approve unknown prompts. Maintaining this control reduces recurrence because: A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. The immediate response remains: Use supported number matching and contextual notifications, along with appropriate MFA protections. Other Answers A:An unsolicited MFA prompt can indicate credential compromise, not a legitimate requirement to approve. The lasting safeguard is to review MFA push abuse signals and educate users not to approve unknown prompts. B:MFA combines different authentication factors, reducing dependence on a stolen password alone. A more direct preventive measure is to review MFA push abuse signals and educate users not to approve unknown prompts. D:Service principals and managed identities are designed for workload authentication without human MFA prompts. Reducing this risk requires a practice to review MFA push abuse signals and educate users not to approve unknown prompts.
Question 225A contractor can still log in with a previously registered phone number after the organization changes its approved methods policy. Which action most directly resolves the security or identity requirement? Run a supported authentication-method registration campaign and confirm enrollment coverage. Configure an authentication strength requiring a supported phishing-resistant method for the protected app. Review and restrict authentication methods and registration as required by the new security policy. Secure authentication-method registration with appropriate identity verification and risk controls. ExplanationCorrect Answer C:Registered factors and permitted authentication method policies are separately governed. To confirm, use a test account with a deprecated method and confirm it cannot satisfy the new requirement. Other Answers A:SSPR depends on the user having enrolled eligible verification methods before an outage. A more relevant action is to review and restrict authentication methods and registration as required by the new security policy. B:Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. The required change instead is to review and restrict authentication methods and registration as required by the new security policy. D:Method registration is a sensitive identity change, not just a low-risk user preference. This failure calls for a decision to review and restrict authentication methods and registration as required by the new security policy.
Question 226A contractor can still log in with a previously registered phone number after the organization changes its approved methods policy. Which technical distinction is decisive in this case? Method registration is a sensitive identity change, not just a low-risk user preference. Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. Registered factors and permitted authentication method policies are separately governed. SSPR depends on the user having enrolled eligible verification methods before an outage. ExplanationCorrect Answer C:Registered factors and permitted authentication method policies are separately governed. This is the principle behind: Review and restrict authentication methods and registration as required by the new security policy. The evidence to inspect is: Use a test account with a deprecated method and confirm it cannot satisfy the new requirement. Other Answers A:Method registration is a sensitive identity change, not just a low-risk user preference. By contrast, registered factors and permitted authentication method policies are separately governed. B:Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. By contrast, registered factors and permitted authentication method policies are separately governed. D:SSPR depends on the user having enrolled eligible verification methods before an outage. In the stated system, registered factors and permitted authentication method policies are separately governed.
Question 227A contractor can still log in with a previously registered phone number after the organization changes its approved methods policy. Which observation best validates the chosen approach? Test access with SMS-only and with a FIDO2 key to confirm differing outcomes. Use a test account with a deprecated method and confirm it cannot satisfy the new requirement. Attempt to register a new factor through an unauthorized flow and verify additional verification is required. Check registration status for a representative student cohort and complete a reset test. ExplanationCorrect Answer B:Use a test account with a deprecated method and confirm it cannot satisfy the new requirement. This test checks the expected result of: Review and restrict authentication methods and registration as required by the new security policy. It matters because: Registered factors and permitted authentication method policies are separately governed. Other Answers A:Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. The failure is checked more directly by a test to use a test account with a deprecated method and confirm it cannot satisfy the new requirement. C:Method registration is a sensitive identity change, not just a low-risk user preference. The relevant acceptance check is to use a test account with a deprecated method and confirm it cannot satisfy the new requirement. D:SSPR depends on the user having enrolled eligible verification methods before an outage. Proving this correction calls for a check to use a test account with a deprecated method and confirm it cannot satisfy the new requirement.
Question 228A contractor can still log in with a previously registered phone number after the organization changes its approved methods policy. Which governance action most directly addresses the recurring risk? Track method registration completeness during onboarding. Review registered methods at policy changes and during external-user offboarding. Monitor authentication method change audit events and notify account owners. Maintain stronger authentication requirements for sensitive workloads. ExplanationCorrect Answer B:Review registered methods at policy changes and during external-user offboarding. Maintaining this control reduces recurrence because: Registered factors and permitted authentication method policies are separately governed. The immediate response remains: Review and restrict authentication methods and registration as required by the new security policy. Other Answers A:SSPR depends on the user having enrolled eligible verification methods before an outage. A more direct preventive measure is to review registered methods at policy changes and during external-user offboarding. C:Method registration is a sensitive identity change, not just a low-risk user preference. The stronger recurring control is to review registered methods at policy changes and during external-user offboarding. D:Authentication strengths specify acceptable method combinations rather than treating every MFA method as equal. Reducing this risk requires a practice to review registered methods at policy changes and during external-user offboarding.
Question 229A customer service app says it must force reauthentication on every click despite a central single sign-on design. Which action most directly resolves the security or identity requirement? Plan the supported password hash synchronization or alternative hybrid sign-in method. Use supported number matching and contextual notifications, along with appropriate MFA protections. Evaluate supported passwordless methods such as Windows Hello for Business or passkeys. Use a supported Entra single sign-on session with risk-appropriate sign-in frequency policies. ExplanationCorrect Answer D:SSO reduces repeated authentication while session controls determine when fresh proof is required. To confirm, sign in to two authorized applications and observe session reuse without bypassing policy challenges. Other Answers A:Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. The corrective action for this requirement is to use a supported Entra single sign-on session with risk-appropriate sign-in frequency policies. B:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. The corrective action for this requirement is to use a supported Entra single sign-on session with risk-appropriate sign-in frequency policies. C:Passwordless authentication substitutes strong cryptographic proof or device-bound credentials for a reusable account password. A more relevant action is to use a supported Entra single sign-on session with risk-appropriate sign-in frequency policies.
Question 230A customer service app says it must force reauthentication on every click despite a central single sign-on design. Which technical distinction is decisive in this case? Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. SSO reduces repeated authentication while session controls determine when fresh proof is required. A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. Passwordless authentication substitutes strong cryptographic proof or device-bound credentials for a reusable account password. ExplanationCorrect Answer B:SSO reduces repeated authentication while session controls determine when fresh proof is required. This is the principle behind: Use a supported Entra single sign-on session with risk-appropriate sign-in frequency policies. The evidence to inspect is: Sign in to two authorized applications and observe session reuse without bypassing policy challenges. Other Answers A:Entra hybrid authentication can validate synchronized credentials while avoiding a different password database per app. By contrast, SSO reduces repeated authentication while session controls determine when fresh proof is required. C:A push prompt's authentication quality depends on resistance to unsolicited approval and fatigue attacks. By contrast, SSO reduces repeated authentication while session controls determine when fresh proof is required. D:Passwordless authentication substitutes strong cryptographic proof or device-bound credentials for a reusable account password. By contrast, SSO reduces repeated authentication while session controls determine when fresh proof is required.