DRAG DROP You need to evaluate the RDS deployment in the Seattle office. The solution must meet the technical requirements. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

The question requires the correct sequence of actions to evaluate an on-premises Remote Desktop Services (RDS) deployment for migration to Azure Virtual Desktop (AVD).

1. The first step in any assessment or migration is to create an Azure Migrate project. This project serves as the central hub for discovering, assessing, and migrating workloads.
2. For VDI (Virtual Desktop Infrastructure) and RDS assessments, Azure Migrate integrates with ISV (Independent Software Vendor) partner tools. The required technical evaluation is based on utilization, which is provided by the Lakeside SysTrack tool. This tool must be registered with the project.
3. To collect the necessary utilization and performance data from the on-premises servers, the Lakeside agent (client) must be installed on the target virtual machines, which in this scenario are identified by a specific prefix.

Microsoft Learn (Azure Migrate): "Create and manage projects." The documentation states the first step is to create an Azure Migrate project. It specifies: "In the Azure portal, search for Azure Migrate. In Services, select Azure Migrate. In Get started, select Discover, assess and migrate. In Servers, databases and web apps, select Create project."

Microsoft Learn (Azure Migrate): "Add migration tools." After the project is created, you add assessment and migration tools. The documentation states: "In Azure Migrate > Add tools, select the tools you want to add. Then select Add tool." For VDI assessments, this would be the Lakeside tool.

Microsoft Community Hub (Blog): "Migrate Virtual Desktops to Azure." This official blog post outlines the process: "Run a discovery of your on-premises datacenter using Lakeside, an integrated ISV tool in Azure Migrate. Lakeside will collect performance information using clients installed on on-premises virtual desktops." This confirms that installing the agent (client) is the correct follow-on step after registering the tool.