Your network contains a Hyper-V host named Server1 that runs Windows Server 2012 R2. Server1 hosts a
virtual machine named VM1 that runs Windows Server 2012 R2.
You take a snapshot of VM1, and then you install an application on VM1.
You verify that the application runs properly.
You need to ensure that the current state of VM1 is contained in a single virtual hard disk file. The solution must
minimize the amount of downtime on VM1.
What should you do?

A.
From Hyper-V Manager, delete the snapshot.

B.
From a command prompt, run dism.exe and specify the /commit-image parameter.

C.
From a command prompt, run dism.exe and specify the /delete-image parameter.

D.
From Hyper-V Manager, inspect the virtual hard disk.

Explanation:
Virtual machine snapshots are file-based snapshots of the state, disk data, and configuration of a
virtualmachine at a specific point in time. You can take multiple snapshots of a virtual machine, even while it is
running. You can then revert the virtual machine to any of the previous states by App1ying a snapshot to the
virtualmachine.
Taking a snapshot of a VM is to in essence freeze the current state and make it a parent disk based on
currentstate, and at the same time create a child disk to capture all subsequent changes.
– See more at:
Snapshots require adequate storage space. Snapshots are stored as .avhd files in the same location at
thevirtual hard disk. Taking multiple snapshots can quickly consume a large amount of storage space.
When you use Hyper-V Manager to delete a snapshot, the snapshot is removed from the snapshot treebut the
.avhd file is not deleted until you turn off the virtual machine.