A Citrix Administrator needs to configure an authentication approach that will allow internal users to use their corporate credentials to automatically log on to external software as a service…

Question

Options

• ACreate an LDAP server for each external SaaS domain and bind them to the authentication,
• BDeploy SAML on Citrix ADC with the identity provider (IdP) role.
• CCreate a domain trust relationship between the external LDAP server(s) and corporate LDAP
• DUse nFactor visualizer on Citrix ADC to ensure RADIUS, LDAP, and push one-time password

• A
  7% (2)
• B
  79% (22)
• C
  4% (1)
• D
  11% (3)

Explanation

Option B is correct because SAML (Security Assertion Markup Language) is the industry-standard protocol designed precisely for this use case: allowing users to authenticate once with their corporate credentials (the Identity Provider) and gain seamless access to external SaaS applications (the Service Providers). Citrix ADC acting as the IdP federates identity to SaaS apps without exposing corporate passwords externally.

Why the distractors are wrong:

• A - Creating per-domain LDAP servers is not how SaaS authentication works; LDAP is an internal directory protocol not designed to federate identity to external web services.
• C - Domain trust relationships apply to Active Directory environments for inter-domain resource access, not to external SaaS applications outside corporate control.
• D - nFactor with RADIUS/LDAP/OTP addresses multi-factor authentication for inbound access (e.g., logging into Citrix itself), not outbound SSO to SaaS apps.

Memory tip: Think SAML = SaaS Authentication Made Lightweight. Whenever a question involves corporate credentials + external SaaS + single sign-on, SAML with an IdP role is the answer. The IdP (your company) vouches for the user to the SaaS Service Provider - no password sharing required.

No community discussion yet for this question.