https://docs.microsoft.com/en-us/powershell/module/az.desktopvirtualization/disconnect- azwvdusersession?view=azps-8.0.0

This is done by using the Add-AzDomainComputer cmdlet in PowerShell. After the computer accounts have been created, the new session hosts can be deployed.
https://docs.microsoft.com/en-us/azure/virtual-desktop/create-session-host-pools#precreate-computer-accounts-in-azure-ad-ds.

Removing VHDLocations is part of the process and happens before creating CCDLocations. The fact that creating the CCDLocations is not listed as an answer does not mean there is no "correct" answer. They're not asking you for *all* of the steps in configuring Cloud Cache.
https://docs.microsoft.com/en-us/fslogix/configure-cloud-cache-tutorial

Enable or disable Start VM on Connect
Once you assign the Desktop Virtualization Power On Contributor role to the service principal on relevant subscriptions, you can configure Start VM on Connect using the Azure portal, Azure PowerShell, or Azure CLI.
To configure Start VM on Connect using the Azure portal:
1. Sign in to the Azure portal.
2. In the search bar, enter Azure Virtual Desktop and select the matching service entry.
*-> 3. Select Host pools, then select the name of the host pool where you want to enable the setting.
4. Select Properties.
5. In the configuration section, set Start VM on connect to Yes to enable it, or No to disable it.
6. Select Save to apply the settings.
Reference:
https://learn.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect