What does the CyberArk Identity App Gateway work with? (Choose three.)

Question

Options

• ASAML-Compliant Apps
• BWS-Fed Enabled Apps
• COIDC Web Apps
• DThick Client (non-web-based Apps)
• ETerminal Services
• FTelnet

• A
  91% (21)
• D
  4% (1)
• F
  4% (1)

Explanation

Note: The provided answer lists only "A," but since the question requires three selections, the most likely intended correct answers are A, B, and C - all three are web-based identity protocol standards that CyberArk Identity App Gateway explicitly supports.

Why A, B, and C are correct: CyberArk Identity App Gateway acts as a reverse proxy to broker secure access to internal web applications using modern identity federation protocols: SAML (A), WS-Federation (B), and OIDC (C). All three are standard web-based SSO/authentication protocols, which aligns directly with the gateway's design purpose.

Why the others are wrong:

• D (Thick Client / non-web-based apps): App Gateway is specifically a web application proxy - it has no mechanism to intercept or broker thick client traffic.
• E (Terminal Services): Terminal Services use RDP, a completely separate protocol stack; App Gateway doesn't handle RDP brokering.
• F (Telnet): Telnet is a legacy, plaintext terminal protocol - entirely outside the scope of a modern identity gateway.

Memory tip: Think "App Gateway = Web Protocols Only." The three correct answers (SAML, WS-Fed, OIDC) are all browser-based SSO standards. If the answer involves something you'd install on a desktop or connect to via a terminal, App Gateway doesn't cover it.

No community discussion yet for this question.