1Y0-231 · Question #38
Scenario: A Citrix Administrator needs to configure an authentication workflow on Citrix ADC with the below requirements. - All internal users must use their corporate credentials to authenticate…
The correct answer is C. Configure nFactor authentication with two LDAP advanced policies and one SAML advanced. nFactor authentication on Citrix ADC enables conditional, policy-driven authentication flows that can route users to different auth methods based on identity signals. Option C is correct because nFactor can evaluate a user's identity and direct internal users through LDAP…
Question
Scenario: A Citrix Administrator needs to configure an authentication workflow on Citrix ADC with the below requirements.
- All internal users must use their corporate credentials to authenticate.
- Users from partner organizations must be authenticated using their own directory services
without replication or a synchronization process. How can the administrator meet the above requirements while authenticating the users?
Options
- ADeploy SAML on Citrix ADC in the service provider (SP) role for users from partner organizations.
- BCreate two LDAP and two SAML authentication policies on the authentication, authorization, and
- CConfigure nFactor authentication with two LDAP advanced policies and one SAML advanced
- DConfigure two dedicated AAA virtual servers for internal and partner users.
How the community answered
(29 responses)- A10% (3)
- B17% (5)
- C66% (19)
- D7% (2)
Explanation
nFactor authentication on Citrix ADC enables conditional, policy-driven authentication flows that can route users to different auth methods based on identity signals. Option C is correct because nFactor can evaluate a user's identity and direct internal users through LDAP (validating against the corporate Active Directory) while routing partner users through SAML federation - which lets partners authenticate against their own Identity Provider without any directory replication or sync, satisfying both requirements in a single unified workflow.
Why the distractors fail:
- A only addresses partner authentication via SAML SP role, leaving no solution for internal users' corporate LDAP requirement.
- B lacks the conditional routing engine; piling policies onto a standard AAA vserver doesn't intelligently choose which policy applies to which user - it also doubles the SAML policies unnecessarily.
- D using two separate AAA virtual servers is an architectural workaround, not an authentication solution - it forces users to know which URL to hit and doesn't meet the requirement with a single, unified workflow.
Memory tip: Think of nFactor as a decision tree - "N factors, N paths." When you see requirements like "Group A uses X, Group B uses Y," nFactor is almost always the answer because it's the only mechanism on Citrix ADC that conditionally branches authentication logic based on who the user is.
Topics
Community Discussion
No community discussion yet for this question.