Plan and design Citrix Virtual Apps and Desktops on Azure
What the exam tests
Planning questions ask you to turn business requirements into a Citrix resource location design, host connection layout, machine catalog strategy, and image lifecycle. You must choose regions for latency and data residency, decide how many Cloud Connectors are needed, and select MCS or another provisioning method. The design must also cover identity, networking, storage, scaling, and disaster recovery.
Core rules and concepts
- A Citrix resource location maps to an Azure region and contains Cloud Connectors, host connections, catalogs, and delivery groups.
- Deploy at least two Cloud Connectors per resource location for availability. They are domain joined and require outbound TCP 443 to Citrix Cloud.
- A host connection is scoped to one Azure subscription and region. Use a service principal with the minimum role needed, commonly Contributor at the target resource group or subscription.
- MCS is the native Azure provisioning method: it captures a master image, creates copies, and manages identity and power operations. Plan image updates as a repeatable cycle.
- Catalogs should align with workload type, image, machine size, and update cadence. Delivery groups map users to catalogs and control access.
- Design for N+1 or N+2 capacity, maintenance windows, and a separate image resource group.
Worked example
A company needs 800 users in East US and West US with active-active access. Each region gets its own resource location, two Cloud Connectors, and a host connection to the regional VNet. The master image is stored in a regional image resource group and replicated through the image pipeline. Each region has a machine catalog sized for 60 percent of its local users plus one host for maintenance, because users can fail over between regions. The delivery group includes both catalogs, but priority is set so local users prefer the local catalog. This design avoids cross-region VDA sessions and keeps Cloud Connector traffic regional.
Traps that cost marks
Placing Cloud Connectors in a DMZ or exposing them to the internet is a common design error. Assuming one Cloud Connector is sufficient for production availability loses marks. Mixing multiple images and VM sizes in one catalog complicates updates and should be justified. Forgetting that the host connection is regional, not global, causes deployment failures. Treating Citrix Cloud as a replacement for AD DS is also wrong for standard domain-joined VDA designs.
Key points
- One resource location per Azure region; at least two Cloud Connectors per location.
- Host connections are subscription-and-region scoped and use a service principal.
- MCS is the default Azure provisioning method for catalog images.
- Separate catalogs by image, size, and workload to simplify lifecycle management.
- Design capacity with maintenance and regional failover headroom.