Free Practice Questions for Citrix 1Y0-205 Exam

According to the Citrix documentation1, when user subscriptions are disabled for a store (Mandatory Store), the following behaviors occur:

Users cannot subscribe to applications from the store. All the applications in the store are automatically subscribed to each user and appear in Citrix Workspace app.

Users cannot remove applications from Citrix Workspace app on the Favorites screen.

Users can organize their applications into folders using the Citrix Workspace app desktop.

Applications are placed in the Start menu or the Applications folder on the user’s device, depending on the Citrix Workspace app version and operating system.

Therefore, the correct answer is B and D.

1: Configure user access

When StoreFront must integrate with a third-party portal, the portal typically acts as the external system that captures user credentials, handles primary authentication, and then passes those credentials (usually via HTTP headers or basic authentication mechanisms) to StoreFront.

Citrix documentation notes that HTTP Basic authentication is the method suited for integrations where StoreFront must accept credentials from an external portal or non-Citrix authentication framework. This method allows StoreFront to validate credentials passed programmatically from the third-party system.

Why not the other options?

Unauthenticated: This provides anonymous access and does not support integration with authenticated external portals.

Domain pass-through: Requires a Windows-integrated authentication flow, not compatible with third-party portals.

Pass-through from NetScaler Gateway: This applies only when authentication is performed via Citrix Gateway, not an external custom portal.

Therefore, HTTP Basic is the appropriate authentication method for third-party portal integration.

Documentation References:

StoreFront Authentication Methods Overview

StoreFront Third-Party Integration Scenarios (Authentication Requirements)

According to Citrix documentation, to make a configuration change for a StoreFront server group, the change should be made on one StoreFront server in the group, and then the Propagate Changes feature should be used to synchronize the change across the group1

According to the Citrix documentation1, the weight option assigns a numerical weight to a service. The higher the weight, the more requests the service can handle. By default, the weight is 1, which means equal distribution of requests. To make the new servers receive twice the connections of the old servers, the administrator needs to assign a weight of 2 to the services attached to the new servers.

According to the Citrix Virtual Apps and Desktops 7 Deployment and Administration course, the Citrix ADC maintains a revision history of the configuration files, which can be used to restore a previous configuration in case of accidental changes or deletions. Restarting the Citrix ADC, running HA file synchronization, or running Save v/s Running configuration will not undo the changes made by the administrator. Therefore, the correct answer is A. Restore from revision history1

1: Manage | Citrix Virtual Apps and Desktops 7 2308

When using an HDX Session printers policy, print jobs sent to a printer managed by the print server are routed directly to the network print server and then to the specified printer3.

The redirectURL parameter of the set cs vserver command specifies the URL where the user requests are redirected if the status of the content switching virtual server is DOWN1. This parameter is used for configuring backup servers or displaying maintenance messages1.

 The Secure Ticket Authority (STA) server locations must be configured on the Citrix Gateway and StoreFront to facilitate secure external access. The Citrix Gateway uses STA to validate session requests and the StoreFront communicates with the STA to manage user sessions securely.

The Citrix Virtual Apps and Desktops documentation specifies that the Local Host Cache feature allows connection brokering operations in a site to continue when the connection between a Delivery Controller and the site database fails1. This implies that the Delivery Controller, which is part of the FlexCast Management Architecture (FMA) services, uses the Local System account to access the Citrix Virtual Apps and Desktops SQL databases in scenarios where the primary database connection is unavailable.

Citrix AutoScale provides automated power management and resource optimization for Virtual Apps and Desktops workloads. Citrix documentation describes two primary AutoScale mechanisms that determine when machines should power on or off:

✔ Schedule-Based AutoScale

Admins can define time-based schedules so machines automatically:

Power on during business hours

Power off during off-peak times

Adjust capacity based on predictable usage patterns

This method is ideal for environments with predictable workloads.

✔ Load-Based AutoScale

AutoScale monitors real-time session demand and machine usage metrics such as:

Session count

Load index

Resource utilization

Machines power on automatically when demand increases and power down during light usage.

Why the other options are incorrect:

Desktop-Based: Not an AutoScale category; desktops are simply resources managed by AutoScale.

Host-Based: Not a Citrix AutoScale mode.

Server-Based: Irrelevant to AutoScale logic; refers to server workloads, not AutoScale mechanisms.

Documentation References

Citrix Virtual Apps and Desktops AutoScale Guide → AutoScale Methods

Citrix Cloud / Studio AutoScale Settings → Schedule-Based and Load-Based Controls