How to Prevent New Session Host from Using an Image Version during Deployment

Correct Answer: C

New deployments using the version “latest" will always utilize the newest image version from a SIG.You can exclude a new image from the latest.When being excluded, you need to specify the new image version during the deployment.

Option A is incorrect.

Temporary setting the version as 0.0.1 until the image is tested won't help in meeting the goal.

Option B is incorrect.

End-of-life dates are just informational; users will still be capable of creating VMs from images and versions past the end-of-life date.

Option C is correct.

Setting the option to exclude the version from the latest will stop the new session host from utilizing the image unless the image version is particularly referenced during deployment.

Option D is incorrect.

Creating a managed image first, then moving the managed image to a SIG once validated is the incorrect solution.

To know more about storing and sharing images in an Azure Compute Gallery, please visit the below-given link:

When publishing a new image to a Shared Image Gallery (SIG) in Microsoft Azure Virtual Desktop, you may want to test the image before it is available to any new session host. To do this, you can prevent the new session host from utilizing the image unless the image version is explicitly referenced during deployment.

One way to accomplish this is by using the "exclude from latest" option. This option allows you to exclude a particular version of an image from being considered the "latest" version, which means that it will not be used for new deployments by default. Instead, you would need to explicitly specify the version number during deployment.

To use this option, follow these steps:

1. Open the Azure portal and navigate to your Shared Image Gallery.
2. Select the image version that you want to exclude from the latest.
3. Click on the "Configuration" tab for that version.
4. Locate the "Latest" option and select "Exclude from latest."
5. Save your changes.

Once you have excluded the version from the latest, you can test the image to ensure that it is working as expected. If you need to make any changes, you can create a new version of the image and repeat the process.

When you are ready to make the image available for new deployments, you can either remove the "exclude from latest" option or create a new version with that option disabled.

Note that the other options listed in the answer choices may also be valid solutions in some cases:

• Setting the version as 0.0.1 temporarily can be useful if you want to create a new version of an image but don't want it to be considered the "latest" until it has been tested.
• Setting the end of life to a past date can be used to prevent new deployments from using an older version of an image.
• Creating a managed image first and then moving it to a SIG once validated can be useful if you want to ensure that the image is working as expected before making it available in the SIG.