1Y0-231 · Question #24
Scenario: A Citrix Administrator is configuring a new authentication, authorization, and auditing (AAA) virtual server, and the status is DOWN. The administrator makes the below configurations: add…
The correct answer is D. An LDAP policy. Binding an LDAP authentication policy is what brings the SAML_SP authentication vserver from DOWN to UP, because a Citrix authentication vserver has no method to validate user credentials until at least one authentication policy (such as LDAP) is bound to it - without it, the…
Question
Scenario: A Citrix Administrator is configuring a new authentication, authorization, and auditing (AAA) virtual server, and the status is DOWN. The administrator makes the below configurations:
add lb vserver lb_vsrv_www HTTP 10.107.149.229 80 -persistenceType NONE -cltTimeout 180 - authn401 ON-authnVsName SAML_SP bind lb vserver lb_vsrv_www_ssl Red_srv bind lb vserver Ib_vsrv_www_ssl Blue_srv add authentication vserver SAML_SP SSL 10.107.149.230 443 -AuthenticationDomain citrix.lab What should the administrator bind to the virtual server SAML_SP to complete the installation and change the status to UP?
Options
- AAn SSL certificate
- BA service
- CAn AAA policy
- DAn LDAP policy
How the community answered
(25 responses)- A12% (3)
- B4% (1)
- C8% (2)
- D76% (19)
Explanation
Binding an LDAP authentication policy is what brings the SAML_SP authentication vserver from DOWN to UP, because a Citrix authentication vserver has no method to validate user credentials until at least one authentication policy (such as LDAP) is bound to it - without it, the vserver is operationally incomplete regardless of other configuration.
Why the distractors are wrong:
- A (SSL certificate): An SSL cert is required for the SSL vserver to serve traffic, but the vserver is already configured as SSL type - the missing piece is an authentication method, not the certificate alone.
- B (A service): Services are bound to LB vservers to represent backend servers. Authentication vservers don't bind to services - they bind to authentication policies.
- C (AAA policy): "AAA policy" is the category/umbrella term, not a specific bindable object type in NetScaler/ADC. You bind a specific policy type (LDAP, RADIUS, SAML, etc.), not a generic "AAA policy."
Memory tip: Think of it this way - LB vservers need Services, Auth vservers need Policies. An authentication vserver is essentially asking "how should I authenticate users?" - until you answer that with a policy (LDAP, RADIUS, etc.), it stays DOWN because it has nothing to do.
Topics
Community Discussion
No community discussion yet for this question.