1Y0-231 · Question #33
To which three bind points can a Citrix Administrator bind a session policy, to enable Clientless access? (Choose three.)
The correct answer is A. Group D. User E. Virtual server. Session policies on Citrix NetScaler/ADC for Clientless access can be bound at the Group (A), User (D), and Virtual Server (E) levels - these are the three standard bind points within the NetScaler AAA/Access Gateway policy framework that apply to session-level configuration…
Question
To which three bind points can a Citrix Administrator bind a session policy, to enable Clientless access? (Choose three.)
Options
- AGroup
- BService
- CService Group
- DUser
- EVirtual server
How the community answered
(37 responses)- A86% (32)
- B5% (2)
- C8% (3)
Explanation
Session policies on Citrix NetScaler/ADC for Clientless access can be bound at the Group (A), User (D), and Virtual Server (E) levels - these are the three standard bind points within the NetScaler AAA/Access Gateway policy framework that apply to session-level configuration. Binding at the virtual server level sets the default behavior for all users connecting through that vServer, while user and group bindings allow more granular overrides for specific individuals or AD groups.
Why B (Service) and C (Service Group) are wrong: Services and service groups are load-balancing constructs used to represent backend servers - they are bind points for traffic policies (like load balancing or content switching), not for session or access policies. Session policies govern client session behavior and have no relevance to the service/service group binding context.
Memory tip: Think "GUV" - Group, User, Virtual server - the three identity/access anchors. Services and service groups belong to the backend/infrastructure side of NetScaler, so they'll never appear in an access policy binding question.
Topics
Community Discussion
No community discussion yet for this question.