Production deployments use the gallery’s latest image, so an untested build has appeared on newly added hosts. Which change best prevents recurrence?

✓ Correct answer

• Pin the approved explicit image version in production deployment parameters and promote versions after testing.

Control image promotion and version selection. Keep known-good versions until dependent deployments and rollback requirements are resolved. Option explanations: A. Pin the approved explicit image version in production deployment parameters and promote versions after testing.: Explicit pinning makes new deployments use the intended reviewed build. B. Delete all older versions before the next build.: That removes rollback choices and does not prevent adoption of an untested latest version. C. Change pool load balancing so latest selects fewer users.: Load balancing does not decide which gallery version provisioning uses. D. Publish every build to production with the same untracked app configuration.: Untracked configuration undermines repeatability and validation. Sources: Azure Compute Gallery — https://learn.microsoft.com/en-us/azure/virtual-machines/azure-compute-gallery; Windows update management methodologies — https://learn.microsoft.com/en-us/azure/virtual-desktop/windows-update-management-methodologies-session-hosts

Read the source reference