Citrix 1Y0-440 Exam With Confidence Using Practice Dumps

Scenario: A Citrix Architect is asked by management at the Workspacelab organization to review their existing configuration and make the necessary upgrades. The architect recommends small changes to the pre-existing Citrix ADC configuration. Currently, the Citrix ADC MPX devices are configured in a high availability pair, and the outbound traffic is load balanced between two Internet service providers (ISPs). However, the failover is NOT happening correctly. The following requirements were discussed during the design requirement phase:

• The return traffic for a specific flow should be routed through the same path while using Link Load Balancing.

• The link should fail over even if the ISP router is up and intermediary devices to an ISP router are down.

• Traffic going through one ISP router should fail over to the secondary ISP, and the traffic should NOT flow through both routers simultaneously. What should the architect configure to meet this requirement?

Scenario: A Citrix Architect and a team of Workspacelab members have met for a design discussion about the NetScaler Design Project. They captured the following requirements:

• Two pairs of NetScaler MPX appliances will be deployed in the DMZ network and the internal network.
• High availability will be accessible between the pair of NetScaler MPX appliances in the DMZ network.
• Multi-factor authentication must be configured for the NetScaler Gateway virtual server.
• The NetScaler Gateway virtual server is integrated with XenApp/XenDesktop environment.
• Load balancing must be deployed for the users from the workspacelab.com and vendorlab.com domains.
• The logon page must show the workspacelab logo.
• Certificate verification must be performed to identify and extract the username.
• The client certificate must have UserPrincipalName as a subject.
• All the managed workstations for the workspace users must have a client identifications certificate installed on it.
• The workspacelab users connecting from a managed workstation with a client certificate on it should be authenticated using LDAP.
• The workspacelab users connecting from a workstation without a client certificate should be authenticated using LDAP and RADIUS.
• The vendorlab users should be authenticated using Active Directory Federation Service.
• The user credentials must NOT be shared between workspacelab and vendorlab.
• Single Sign-on must be performed between StoreFront and NetScaler Gateway.
• A domain drop down list must be provided if the user connects to the NetScaler Gateway virtual server externally.
• The domain of the user connecting externally must be identified using the domain selected from the domain drop down list.

On performing the deployment, the architect observes that users are always prompted with two-factor authentication when trying to assess externally from an unmanaged workstation.

Click the exhibit button to view the configuration.

What should the architect do to correct this configuration?

Scenario: A Citrix Architect holds a design discussion with a team of Workspacelab members, and they capture the following requirements for the NetScaler design 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.
• Multi-factor authentication must be configured for the NetScaler Gateway virtual server.
• The NetScaler Gateway virtual server is integrated with the StoreFront server.
• Load balancing must be deployed for users from the workspacelab.com domain.
• The workspacelab users should be authenticated using Cert Policy and LDAP.
• All the client certificates must be SHA 256-signed, 2048 bits, and have UserPrincipalName as the subject.
• 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 aaad debug and the configuration of the authentication policy.

Exhibit 1

Exhibit 2

What is causing this issue?