Question 23 — AB-650 Practice Exam 2
For each Microsoft Entra authentication capability, drag it to the appropriate box in the Correct Match column to match it with its function or deployment characteristic.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Provides push approval with number matching, phone sign-in, time-based one-time passcodes, and support for registering a device-bound passkey | [Gap 1] |
| Uses an RFC 6238-compatible application to generate rotating one-time codes without Microsoft Authenticator push approval or phone sign-in | [Gap 2] |
| Provides a time-limited passcode for onboarding or account recovery and can be configured for single or repeated use during its validity period | [Gap 3] |
| Provides a phishing-resistant credential tied to a Windows device and is primarily deployed through Intune or Group Policy | [Gap 4] |
| Directs users toward their strongest registered authentication method during sign-in | [Gap 5] |
- Temporary Access Pass (TAP)
- SMS authentication
- Microsoft Authenticator
- Windows Hello for Business
- Email one-time passcode
- System-preferred authentication
- Third-party software OATH token
Correct answers
- Gap 1: Microsoft Authenticator
- Gap 2: Third-party software OATH token
- Gap 3: Temporary Access Pass (TAP)
- Gap 4: Windows Hello for Business
- Gap 5: System-preferred authentication
Explanations
Correct Matches
Microsoft Authenticator – Microsoft Authenticator supports MFA push notifications with number matching, passwordless phone sign-in, offline TOTP codes, and registration of device-bound passkeys on supported mobile devices.
Third-party software OATH token – An RFC 6238-compatible authenticator application generates rotating TOTP codes. These applications do not provide Microsoft Authenticator features such as push approval, number matching, or phone sign-in.
Temporary Access Pass (TAP) – TAP provides a temporary credential for onboarding or recovery. It can bootstrap another authentication method and may be configured for one-time or repeated use within its validity window.
Windows Hello for Business – Windows Hello for Business is a device-bound, phishing-resistant authentication method. Its deployment is normally handled through device-management technologies such as Microsoft Intune or Group Policy.
System-preferred authentication – System-preferred authentication automatically steers a user toward the strongest authentication method that the user has already registered.
Unused Items
SMS authentication – SMS delivers a verification code to a phone and belongs to the traditional authentication-method category rather than performing any of the specialized functions described in the table.
Email one-time passcode – Email one-time passcodes can be used for guest authentication but do not provide the deployment, recovery, or strongest-method-selection behavior represented by the table entries.