Citrix
1Y0-440 · Question #48
SCENARIO: A Citrix Architect holds a design discussion with a team of Workspacelab members, and they capture the following requirements for the NetScaler Seven project: A pair of NetScaler MPX…
The correct answer is D. ldapLoginName is set as SAMAccountName. See the full explanation below for the reasoning.
Question
SCENARIO: A Citrix Architect holds a design discussion with a team of Workspacelab members, and they capture the following requirements for the NetScaler Seven project:
- A pair of NetScaler MPX appliances will be deployed in the DMZ network and another pair in the internal network.
- High availability will be accessible between the pair of NetScaler MPX appliances in the DMZ network.
- High availability will NOT be accessible between the pair of NetScaler MPX appliances in the internal network.
- The NetScaler Gateway virtual server is integrated with the StoreFront server.
- The authentication to the NetScaler Gateway virtual server is through LDAP.
- The Workspacelab users should be authenticated using Cert Policy and LDAP.
- The primary authentication method will be LDAP and secondary authentication will be Certificate.
- Single sign-on must be performed between StoreFront and NetScaler Gateway. After deployment, the architect observes that LDAP authentication is failing. Click the Exhibit button to review the output of ssld debug and the configuration of the authentication policy. What is causing the authentication issue?
Options
- AUserDisplayName is set as subject DN
- BUserPrincipalName is not set.
- CUser does NOT exist in database
- DldapLoginName is set as SAMAccountName
How the community answered
(46 responses)- A4% (2)
- B11% (5)
- C2% (1)
- D83% (38)
Community Discussion
No community discussion yet for this question.