A user's account information required for multi-factor authentication is not set up properly and is preventing the user from logging in. What should you do?

Question

Options

• AUse the MFA Unlock command in the Admin Portal to suspend multifactor authentication for 10 minutes.
• BDelete the user's account and create a new one.
• CAsk the user to delete all browser cookies, then try again.
• DChange the user's director/ source from Active Directory to LDAP for authentication.

• A
  78% (25)
• B
  13% (4)
• C
  3% (1)
• D
  6% (2)

Explanation

Option A is correct because the MFA Unlock (sometimes called "MFA Reset" or "Temporary Bypass") command in an Admin Portal is the standard administrative tool designed specifically for this scenario - it temporarily suspends MFA for a short window so the user can log in and reconfigure their authentication credentials without losing their account data. Option B is destructive overkill; deleting and recreating an account loses all user data, permissions, and history when a targeted admin tool exists. Option C (clearing browser cookies) addresses browser-side session issues, not a server-side MFA configuration problem. Option D makes no sense here - switching directory sources (AD vs. LDAP) changes the authentication backend, which would likely break the account further rather than resolve an MFA setup issue.

Memory tip: Think of MFA Unlock as a "temporary key" - when a lock (MFA) is jammed, you don't demolish the door (delete account) or repaint it (clear cookies); you use the master key (Admin Portal bypass) to get in temporarily and fix the lock properly.

No community discussion yet for this question.