Where can MFA filters be used? (Choose three.)

Question

Options

• AUser and Admin Portal login
• BApp level 2FA/MFA
• CRADIUS
• DSelf-service password reset
• EEditing personal profile attributes
• FOAUTH2 connections

• A
  92% (47)
• D
  2% (1)
• E
  4% (2)
• F
  2% (1)

Explanation

Note: The question says "Choose three," but the provided answer key only shows "A." This appears to be an incomplete answer key. Based on standard IAM/identity platform exam content (such as Okta), the three correct answers are most likely A, B, and C.

User and Admin Portal login (A), App-level 2FA/MFA (B), and RADIUS (C) are the three contexts where MFA filters/policies can be applied because they all represent active authentication entry points where step-up verification can be enforced - a user logging into the portal, signing into a connected app, or authenticating over RADIUS are all authentication events that MFA policy engines can intercept and gate.

Self-service password reset (D) typically uses identity verification (security questions, email/SMS codes) rather than MFA policy filters specifically - it's a recovery flow, not an authentication flow. Editing personal profile attributes (E) is a post-login action; while some platforms support step-up auth for sensitive edits, this is not a standard MFA filter target. OAUTH2 connections (F) are authorization grant flows governed by OAuth policies, not MFA filters directly - MFA would be enforced at the IdP login step upstream, not on the OAuth connection itself.

Memory tip: Think "Where does a user authenticate?" - Portal login, App sign-on, and RADIUS are all authentication handshakes. Password reset and profile editing happen after identity is already established, and OAuth is an authorization protocol, not an authentication filter point.

No community discussion yet for this question.