Citrix Virtual Apps and Desktops Service Integration with Microsoft Azure study plan

Map each Citrix Virtual Apps and Desktops on Azure component (delivery controller, Cloud Connector, VDA, StoreFront/Workspace, host connection) to the Azure resource that hosts it, and write a one-page reference you can redraw from memory

Create a free or pay-as-you-go Azure subscription and build a resource group plus a hub virtual network with a gateway subnet, a management subnet, and a workload subnet using the portal, then repeat the same build with Azure CLI to confirm both paths

Explain the difference between Azure RBAC roles and Citrix cloud roles by listing which identity performs machine catalog creation, which performs image preparation, and which reads the host connection

Provision a domain-joined utility VM and document the exact steps to join it, including DNS server settings and the subnet it sits in

Design the machine catalog strategy for your scenario: decide MCS versus PVS, pooled versus dedicated, and single-session versus multi-session, and justify each choice against a stated user group

Size the Azure VM SKUs for your VDAs and estimate cost for a defined number of users at a defined concurrency, showing the arithmetic in a spreadsheet

Prepare a master image on an Azure VM, run the VDA installer, and generalize or snapshot it in the way your chosen provisioning method requires

Configure a host connection from Citrix Cloud to your Azure subscription and confirm the subscription and network appear as available resources

Write the capacity and image lifecycle section of a design document, covering image update cadence and how many spare machines stay powered on

Create a machine catalog using Azure provisioning and publish a delivery group with at least two test users, then verify a successful ICA session end to end

Configure Azure load balancing for RDP/SSH-style management access separately from Citrix access, and explain why Citrix session traffic does not use an Azure load balancer

Assign static private IP addresses or confirm dynamic allocation behavior for VDAs, and record which subnet each catalog uses

Configure network security groups so that only required ports are open between the VDA subnet, the Cloud Connector subnet, and the internet, and document each rule with its purpose

Test name resolution from a VDA to the Cloud Connector and to Azure services, and record the DNS configuration that made it work

Implement hybrid identity by connecting your on-premises or simulated directory to Microsoft Entra ID, and confirm sign-in works for a synced test account

Configure conditional access or MFA policy for Citrix access and verify the policy actually blocks a sign-in that should be blocked

Set up Azure VPN gateway or ExpressRoute-equivalent private connectivity between your simulated on-premises network and Azure, and prove routing with a ping or traceroute from each side

Document the traffic flows for ICA, Cloud Connector outbound, and management access, naming the port, direction, and endpoint for each

Explain how Citrix Federated Authentication Service fits with Entra ID and when you would use it instead of plain Entra ID sign-in

Enable Azure Monitor and configure at least one alert on VDA CPU or available memory, and confirm the alert fires by stressing a test VM

Configure autoscale for a delivery group with a schedule and peak settings, then observe machines power on and off across a simulated peak window

Apply Citrix Autoscale or Azure-native scaling logic and compare the two approaches in writing, noting which one you would choose and why

Harden the deployment by applying disk encryption and reviewing which accounts hold owner or contributor rights on the resource group

Capture a baseline of session performance using a monitoring tool and record the numbers you would compare against after tuning

Design where Citrix ADC sits in front of your Azure deployment, choosing between an ADC in Azure, an ADC on premises, and the Citrix Cloud service, and justify the choice for your scenario

Deploy a Citrix ADC VPX in Azure and configure a load-balanced virtual server for StoreFront or Gateway traffic, then verify the virtual server reports UP

Configure health monitors for the backend services and demonstrate what happens to the virtual server state when a backend is stopped

Write the certificate and TLS plan for the ADC, including where certificates terminate and how they are renewed

Update your design document with the ADC tier and the failover behavior you would expect if one ADC instance becomes unavailable

Reproduce and resolve three realistic failures: a VDA that fails to register, a session that fails to launch, and a host connection that cannot enumerate the subscription, and write the diagnostic path for each

Use Citrix diagnostic tools and Azure activity logs side by side to trace one failure from symptom to root cause

Analyze a simulated cost overrun by identifying idle or oversized machines and proposing concrete remediation

Review Azure subscription limits and quotas relevant to your design (cores per region, public IPs, network interfaces) and confirm your design stays within them

Build a troubleshooting checklist ordered by where you look first, second, and third

Rebuild the core deployment from scratch in a fresh resource group without consulting your earlier notes, timing how long it takes

Run a full practice exam under timed conditions and record your score per domain

Re-study the two weakest domains identified by the practice exam and write a short summary of each weak area

Verify every item on your troubleshooting checklist against the rebuilt environment and correct anything that no longer applies

Write a final one-page summary of the deployment decisions you would defend in an interview or design review