A company has deployed MFA Some employees, however, report they ate not gelling a notification on their mobile device. Other employees report they downloaded a common authenticates application but…

Question

Options

• AThe company is using a claims-based authentication system for MFA
• BThese are symptoms of known compatibility issues with OAuth 1 0
• COpenID Connect requires at least one factor to be a biometric
• DThe company does not allow an SMS authentication method
• EThe WAYF method requires a third factor before the authentication process can complete
• FA vendor-specific authenticator application is needed for push notifications

• A
  1% (1)
• B
  7% (5)
• C
  76% (53)
• D
  3% (2)
• F
  13% (9)

Explanation

The two scenarios each have a distinct root cause. (1) Employees not receiving push notifications: This is best explained by choice F - push notifications require a vendor-specific authenticator app. Generic TOTP apps (e.g., Google Authenticator) do not support push-based approval; they only generate time-based codes. (2) Employees tapping a code in an authenticator app that copies it to clipboard instead of confirming: This behavior is consistent with a TOTP-only workflow where no push mechanism exists - the user must manually copy and paste the code. This aligns with choice D - the company does not allow SMS (or push) authentication, forcing manual code entry. The stated key answers C and E are technically incorrect: OpenID Connect does NOT require biometric factors (C is false), and WAYF (Where Are You From) is a federation discovery mechanism, not an MFA step-count protocol (E is false).

No community discussion yet for this question.