You published image version 2.1.0 in an Azure Compute Gallery and your ARM templates reference version "latest". After deploying new session hosts, you discover a regression in 2.1.0. You must prevent further deployments from using 2.1.0 when "latest" is specified but keep it available for limited testing, and plan a rollback for affected hosts. Which two actions should you take? (Choose two.)

Marking image version 2.1.0 as "Exclude from latest" in the Azure Compute Gallery prevents new deployments using "latest" from picking up the problematic version, while keeping it available for specific testing. This addresses the requirement to prevent further deployments from using 2.1.0. To roll back affected hosts, the most effective method is to provision new session hosts from a known stable image version (e.g., 2.0.0). Once these new hosts are ready, drain the affected hosts (those running 2.1.0) to allow users to gracefully disconnect, then remove them from the host pool. Deleting the image version would make it unavailable for any testing. Modifying templates to pin to an older version is a valid long-term solution but doesn't immediately stop "latest" from being 2.1.0 for other deployments, nor does it address existing affected hosts. Reimaging with Azure Update Manager is not designed for rolling back to a previous OS image version.