1Y0-312 Citrix Virtual Apps and Desktops 7 Advanced Administration Practice Questions

The Platform layer holds the software for a specific target environment (hypervisor tools for an additional hypervisor, provisioning software, connection broker/VDA, SCCM) and is what lets a layered image be published to that platform. In a multi-hypervisor deployment you create a Platform layer for each target environment (hypervisor plus provisioning type). Windows updates belong in the OS layer, and there is no five-Platform-layer repository limit.

The Platform layer holds the software for a specific target environment (hypervisor tools for an additional hypervisor, provisioning software, connection broker/VDA, SCCM) and is what lets a layered image be published to that platform. In a multi-hypervisor deployment you create a Platform layer for each target environment (hypervisor plus provisioning type). Windows updates belong in the OS layer, and there is no five-Platform-layer repository limit.

The WEM documentation states that WEM supports SQL Server Always On availability groups (Basic and Advanced) for database high availability and that Citrix has tested and certified WEM on that technology; the documentation walks through creating the WEM database and adding it to an availability group with a listener. It does not designate mirroring, replication or clustering as the recommended option.

Apps A and B are needed by all users and can be built into a single layered image. App C is restricted to executives, so instead of maintaining a second image it is assigned as an Elastic Layer to the executives group only (elastic layering works on non-persistent MCS machines). One layered image with an elastic layer meets the requirement with the least effort. User layers persist user settings/installed apps and do not restrict app access.

When upgrading the Workspace Environment Management (WEM) Administration Console, the infrastructure service and database must be upgraded prior to upgrading the console to ensure compatibility and prevent version mismatch errors. The console communicates with these backend components, so they must be at the correct version first. PowerShell commands, agents, and DLL files are handled differently in the upgrade process and do not require pre-console upgrade.

A VDA registers with a Delivery Controller over TCP 80. It learns which Controllers to contact from the Controllers policy (ListOfDDCs under HKLM\Software\Policies\Citrix\VirtualDesktopAgent), the ListOfDDCs registry value set at VDA installation, OU-based discovery, or MCS personality.ini. The master image was built without Controller addresses and no policy supplies them, so the VDAs have no Controller to register with, even though TCP 80, time sync and the Broker Service are all fine.

With multi-site aggregation the user logs on to, and enumerates resources from, the StoreFront deployment in their own site - Site A - which aggregates the resource feed from the Site B Delivery Controllers. Launch routing is a separate decision. By default StoreFront launches through the gateway the user connected through, but optimal HDX (gateway) routing, set per store on the Optimal HDX Routing tab or with Register-STFStoreOptimalLaunchGateway, maps a resource feed or zone to its optimal gateway. The StoreFront 1912 LTSR docs say it 'forces ... connections through the gateway closest to the ... farms' that host the apps, so the ICA launch for the Site B resources goes through the Site B Citrix ADC. Pairs that enumerate through the Site B StoreFront are wrong, because the user never logs on there. Site A for both steps is what happens without optimal gateway routing.

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.

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.

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.

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.

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.

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.