Question 280
In the Atlas Digital Systems pilot environment, a controlled verification is required for: An image release has no rollback strategy, leaving AVD users blocked when the latest application package fails during first sign-in. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A deliberately faulty pilot image is rejected and the fleet can redeploy hosts from the previous approved version. This is an independently observable result of the targeted change: Use versioned image lifecycle management with staged rings, approval criteria, and an accessible known-good fallback version. It closes the specific Atlas Digital Systems failure: An image release has no rollback strategy, leaving AVD users blocked when the latest application package fails during first sign-in.
Incorrect Answers
A VM created from the captured image receives unique identity details and contains no test-user credentials or session history. This is evidence for a DIFFERENT remediation: Create a clean reference VM, remove sensitive artifacts, and generalize or otherwise prepare it according to the supported image capture workflow. That remediation addresses: A custom AVD image contains cached domain credentials and unique machine identifiers because it was copied directly from an active session host. It does not establish resolution of the Atlas Digital Systems problem: An image release has no rollback strategy, leaving AVD users blocked when the latest application package fails during first sign-in. The required outcome here is: A deliberately faulty pilot image is rejected and the fleet can redeploy hosts from the previous approved version.
A host instantiated from the image successfully launches the required business app in a controlled user session. This is evidence for a DIFFERENT remediation: Install and test required applications in a disposable reference host before validating and publishing the approved image. That remediation addresses: An image build team captures a template before completing AVD app compatibility checks, causing every new host to fail an essential app launch. It does not establish resolution of the Atlas Digital Systems problem: An image release has no rollback strategy, leaving AVD users blocked when the latest application package fails during first sign-in. The required outcome here is: A deliberately faulty pilot image is rejected and the fleet can redeploy hosts from the previous approved version.
An audit finds that every active host pool has at least one recoverable supported image version and unused versions expire only after review. This is evidence for a DIFFERENT remediation: Define retention, deprecation, and deletion policies for image versions based on active references and recovery obligations. That remediation addresses: Old custom images are deleted immediately after rollout even though host replacements and disaster recovery still depend on those versions. It does not establish resolution of the Atlas Digital Systems problem: An image release has no rollback strategy, leaving AVD users blocked when the latest application package fails during first sign-in. The required outcome here is: A deliberately faulty pilot image is rejected and the fleet can redeploy hosts from the previous approved version.