Scenario: Users are attempting to logon through Citrix Gateway. They successfully pass the Endpoint Analysis (EPA) scan, but are NOT able to see the client choices at logon. What can a Citrix…

Question

Options

• AQuarantine groups
• BClient choices globally
• CSplit tunneling
• DnFactor authentication

• A
  83% (20)
• B
  4% (1)
• C
  4% (1)
• D
  8% (2)

Explanation

Quarantine groups, when configured on Citrix Gateway, intercept users after a completed EPA scan and assign them to a restricted policy group - this group-based session policy can suppress the client choices screen, even for users who passed the scan. Disabling quarantine groups allows those users to bypass that restricted policy path and reach the standard logon flow where client choices (like Receiver/Workspace app vs. browser) are presented normally.

Why the distractors are wrong:

• B (Client choices globally): Disabling client choices globally would remove the client choices screen for everyone - the opposite of what's needed.
• C (Split tunneling): Split tunneling controls which traffic routes through the VPN tunnel; it has no bearing on what logon UI is presented.
• D (nFactor authentication): nFactor governs multi-step authentication flows; while it can affect logon behavior broadly, the specific cause here is EPA-triggered quarantine group assignment, not the auth factor chain itself.

Memory tip: Think "quarantine = lockdown." Even a passing EPA result can land a user in a quarantine group with a locked-down session policy - disabling quarantine groups lifts that lockdown and lets the client choices screen through.

No community discussion yet for this question.