ACCESS-DEF · Question #40
What can cause users to be prompted for unrecognized MFA factors, such as a wrong phone number or unregistered MFA factor?
The correct answer is C. They mistyped their username. Mistyping a username causes the system to look up a different user's account, which may have a different phone number registered for MFA or no MFA factor at all - so the prompts appear "unrecognized" to the person actually typing. Option A is wrong because installing the app on…
Question
Options
- ASomeone installed the CyberArk Identity mobile app on a different phone with their credentials.
- BThe administrator switched authentication profiles.
- CThey mistyped their username.
- DSomeone registered their phone number to the wrong username.
How the community answered
(15 responses)- B7% (1)
- C87% (13)
- D7% (1)
Explanation
Mistyping a username causes the system to look up a different user's account, which may have a different phone number registered for MFA or no MFA factor at all - so the prompts appear "unrecognized" to the person actually typing. Option A is wrong because installing the app on a new phone doesn't change which factor is registered to the account; it's an app access issue, not an account mismatch. Option B is wrong because switching authentication profiles changes policy for a group of users, not which specific phone number or factor is tied to an individual account. Option D describes a real scenario that could cause confusion, but the registered phone would still appear in the system - it's the ownership that's wrong, not the prompt itself, making it a less direct cause of the described symptom.
Memory tip: Think "wrong name = wrong account = wrong MFA." A simple typo hands you someone else's login context, and their MFA settings are invisible to you.
Topics
Community Discussion
No community discussion yet for this question.