You are publishing a new image to a Shared Image Gallery. You desire to test/verify the image before it is available to any new session host. How would you stop the new session host from utilizing the image unless the image version is particularly referenced during deployment?

Answer options:

A.Temporary set the version as 0.0.1 until the image is tested.
B.Set the end of life to a past date.
C.Set the option to exclude the version from the latest.
D.Create a managed image first, then move the managed image to a SIG once validated.

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.
Reference: 
To know more about storing and sharing images in an Azure Compute Gallery, please visit the below-given link: 

https://docs.microsoft.com/en-us/azure/virtual-machines/shared-image-galleries#image-versions