Q: 5
You have an Azure AD tenant. You plan to implement an authentication solution to meet the following requirements:
• Require number matching.
• Display the geographical location when signing in.
Which authentication method should you include in the solution?
Options
Discussion
Option C is the way to go. Had something like this in a mock, and Microsoft Authenticator is the only one that does both number matching and shows the sign-in location info. SMS, TAP, and FIDO2 don't hit both requirements. Pretty sure on this but open to corrections!
Option C TAP (B) is tempting but it doesn't provide number matching or show geo info, unlike Authenticator.
C imo, Microsoft Authenticator is the only one here with both number matching and the geo location prompt during sign-in. SMS and TAP (B) don't show those context features, and FIDO2 keys (D) don't do number matching either. Pretty sure that's what MS wants for secure MFA now, but happy to hear if someone has seen something different in production.
C
Microsoft Authenticator handles both number matching and geolocation prompts. Nice clear wording in the question, makes it easy to spot that only C covers both requirements.
Microsoft Authenticator handles both number matching and geolocation prompts. Nice clear wording in the question, makes it easy to spot that only C covers both requirements.
Seen this in official docs and test banks, it's C. Microsoft Authenticator is the only one that lets you do number matching and see the sign-in location. I think that's what the exam wants here but happy to hear another view.
C , A and B are easy traps here since they don't support number matching with location like Microsoft Authenticator does.
C imo. Official study guide and the MS Learn labs both call out Microsoft Authenticator for number matching plus sign-in location stuff.
C tbh, B is a trap since TAP doesn’t support number matching or show geo location.
Its C for sure. Microsoft Authenticator supports both number matching and shows the sign-in location, which is exactly what they're asking for. Pretty sure SMS, TAP, and FIDO2 can't do both. If I'm missing something let me know, but C fits best.
I don’t think B is right here. Temporary Access Pass doesn’t support number matching or show location details. Pretty sure it’s C, Microsoft Authenticator, since that’s the one with both features. Anybody see a reason to pick B?
Be respectful. No spam.
