To enable an easy rollback of a VM change within about two hours, which method provides the simplest rollback approach?

To enable an easy rollback of a VM change within about two hours, which method provides the simplest rollback approach?

• A. Create a snapshot on the hypervisor.
• B. Make an on-demand incremental backup to a VTL.
• C. Make an on-demand, full backup to a secondary location.
• D. Create a snapshot on a remote storage array.

Answer: (A)

For a rollback to be quick, you want a point-in-time state you can revert to with minimal steps. Creating a snapshot on the hypervisor gives you an instant, point-in-time image of the VM that you can revert to, usually with very little downtime. Because the VM’s state is stored locally and the revert is a built-in operation, you can undo the change and resume normal operation within minutes, which fits a two-hour window nicely. In contrast, backups to tape or another location require transferring data and performing a restore, which adds steps and time; a full backup restore from a secondary location can take even longer, especially for large VMs. A snapshot on remote storage can be useful for disaster recovery, but restoring from remote storage adds latency and management overhead, making it slower and less straightforward than a local hypervisor snapshot. Keep in mind that snapshots are best for short-term undo rather than long-term protection, and should be cleaned up after the rollback to avoid performance or storage issues.

For a rollback to be quick, you want a point-in-time state you can revert to with minimal steps. Creating a snapshot on the hypervisor gives you an instant, point-in-time image of the VM that you can revert to, usually with very little downtime. Because the VM’s state is stored locally and the revert is a built-in operation, you can undo the change and resume normal operation within minutes, which fits a two-hour window nicely. In contrast, backups to tape or another location require transferring data and performing a restore, which adds steps and time; a full backup restore from a secondary location can take even longer, especially for large VMs. A snapshot on remote storage can be useful for disaster recovery, but restoring from remote storage adds latency and management overhead, making it slower and less straightforward than a local hypervisor snapshot. Keep in mind that snapshots are best for short-term undo rather than long-term protection, and should be cleaned up after the rollback to avoid performance or storage issues.