Citrix Virtual Apps and Desktops 7 Advanced Administration Free Sample Questions

With multi-site aggregation the user authenticates and enumerates on the StoreFront deployment local to them (Site A), which aggregates the resources from Site B. Optimal HDX (gateway) routing then maps the Site B Delivery Controllers/zone to the Site B Citrix ADC Gateway, so the ICA launch is routed through the gateway co-located with the resources instead of the gateway the user logged on through. Answer: A; B.

StoreFront keeps each store's subscription (and favorites) data in a local Microsoft ESENT (Extensible Storage Engine) datastore at C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Citrix\SubscriptionsStore\1__Citrix_ ; the database file is PersistentDictionary.edb. The store web.config only contains the client endpoint that points to the Subscriptions Store service; it does not hold subscription data.

During a Primary zone outage in a multi-zone Citrix deployment, site performance degradation occurs because the Secondary zone Delivery Controllers must handle additional load without the Primary zone controllers. This creates resource contention and increased response times until the Primary zone is restored. The zone preference settings and load balancing algorithms are disrupted, causing suboptimal performance across the remaining infrastructure.

Studio cannot connect to the site during a Primary zone outage because Studio typically connects to the Primary zone Delivery Controllers by default. When these controllers are unavailable, administrative access through Studio is lost unless explicitly configured to connect to Secondary zone controllers. This represents a critical limitation in site management during Primary zone failures.

VDA machines in the Primary zone cannot be accessed during the zone outage because their registered Delivery Controllers are unavailable. Even though the machines may still be running, users cannot establish new connections because the broker service responsible for authentication and session management is down. Existing sessions continue running but new connections fail until zone recovery or VDA re-registration to Secondary zone controllers.

In Citrix App Layering, when multiple application layers are created, the layer priority is determined by the creation timestamp, with the most recently created layer taking the highest priority. App Layer C is the correct answer because it was created with the latest timestamp among all the application layers. This priority system ensures that newer application installations and updates override older versions, preventing conflicts and ensuring users access the most current application versions. App Layers A, B, and D were created earlier and therefore have lower priority in the layering hierarchy.

WEM only manages AD objects that have been added to the configuration set (users/groups, computers, computer groups, OUs). Multiple users or groups can be added at once by separating names with semicolons, and machines are added with the Add Object (computer/computer group) or Add OU buttons. Groups can be added, and Item Priority exists for users/groups and for computers/OUs alike.

Citrix recommends a maximum of six servers in a StoreFront server group; beyond six, the overhead of synchronizing configuration and subscription data outweighs the benefit of extra servers and performance degrades. Instead of growing the group past six members, scale up the existing servers (StoreFront recommends 4 vCPUs, minimum 2) so that fewer, larger servers carry the load.

Elastic layers are app layers assigned to users/groups and delivered at logon on top of a layered image. They require non-persistent machines (persistent desktops are supported only if elastic layering and user layers are not enabled), and a few applications, such as Microsoft Office, cannot be delivered elastically (check the App Layering recipes). Elastic layer priority follows the original app layer creation order, not attach order, and any app layer can be assigned elastically without being recreated.

Elastic layers deliver app layers on demand to the specific users or groups they are assigned to, so they suit applications needed by only a subset of users (e.g., a Marketing-only app, or custom HR apps used by a few managers) without adding them to every layered image. Letting users install their own applications is the job of user layers, and apps needed by everyone belong in the layered image.

When 'Log Off Web Portal When a session is launched' is enabled, the WEM Transformer logs the user off the StoreFront web front end as soon as the desktop session launches. With StoreFront workspace control at its default, all applications/sessions started from the store are disconnected when the user logs off from the store, so the just-launched session would be dropped. Workspace control must therefore first be set so that sessions are NOT logged off/disconnected when users log off from StoreFront.

In the WEM administration console, Advanced Settings > Configuration > Main Configuration > Agent Actions contains per-action-type processing switches (Process Applications, Process Printers, Process Network Drives, Process Virtual Drives, ...). The printer works because Process Printers is enabled; the new network drive action is never applied until Process Network Drives is enabled.