Scenario: A Citrix Engineer is managing a Provisioning Services environment. The day after a new vDisk version is rolled out to production, multiple users report issues with one of the core applications hosted on the vDisk image. The administrator wants to roll back the new change and allow the target devices to stream from a functioning vDisk as soon as possible.
How can the engineer accomplish this in the least amount of time?
To accomplish the rollback as quickly as possible, the engineer should copy an older version of the vDisk from the backup storage location and then reassign all the target devices to the imported vDisk and restart them. This approach ensures that the users can immediately start using a known, functioning vDisk without going through additional steps like reverting to Maintenance or Test mode, which could cause downtime and complicate the process. Restoring a working vDisk from backup is the most efficient way to resolve the issue promptly.
If issues exist in the new version, revert from test to maintenance, if no active sessions exist. You can alternately revert from production to either test or maintenance. Shut down any booted device before reverting to another version. https://docs.citrix.com/en-us/provisioning/current-release/manage/managing-vdisks/vdisks-update.html
I am not even sutre if that is possible to revert from prod to test or to maint version
Answer C makes no sense as it causes downtime. once a production VMs (let's say thousands of them) are booted the you cannot revert a vdisk version to maintenance or test because they are booted from that vDisk version. to revert you would need to shut all VDAs down that causes down time. the only reasonable option is to restore older vDisk version from backup and reboot devices in batches once they are drained.
"The administrator wants to roll back the new change and allow the target devices to stream from a functioning vDisk as soon as possible." If the vDisk is corrupted and you want to roll back why would you want to revert the disk to TST or MAINT version and again push it to the users? Especially that you don't push MAINT vDisks to users? I think it should be B. Get a working vDisk from backup -> restore -> let users work -> focus on fixing new corrupted build.
Yes, C is correct