A build pipeline installs a cumulative OS update and an application update successfully. The image is used by shared desktops with FSLogix. What validation is needed before broad rollout?

✓ Correct answer

• Deploy pilot hosts from the new image and test real sign-in, profile attachment and representative application workflows.

Image validation must test the resulting desktop and user state, including OS/app compatibility and profile behavior. Option explanations: A. Raise the session limit before the first pilot sign-in.: A capacity setting is not compatibility validation and can add load. B. Deploy pilot hosts from the new image and test real sign-in, profile attachment and representative application workflows.: The deployed shared desktop can expose interactions that a successful installer on the build VM does not test. C. Use the package-install exit codes as the only release gate.: They prove installer execution, not desktop usability. D. Copy current user profiles into the generalized image for convenience.: Live user profiles should stay outside the reusable image. Sources: Windows update management methodologies — https://learn.microsoft.com/en-us/azure/virtual-desktop/windows-update-management-methodologies-session-hosts; Prepare a golden image — https://learn.microsoft.com/en-us/azure/virtual-desktop/set-up-golden-image

Read the source reference