A company has a Windows Server 2012 R2 Hyper-V hostserver named NYC-HOST1 that hosts a virtual
machine (VM) named NYC-VM1.
A critical security update must be applied immediately to NYC-VM1. There is no time to test the updatebefore
deployment. You must minimize the amount of time needed to restore the VM.
You need to capture the state of NYC-VM1 before youinstall the critical security update.
What should you do?
A.
From Hyper-V Manager, select NYC-VM1, and then create a checkpoint.
B.
Run the Windows PowerShell command Save-VM NYC-VM1.
C.
Run the Windows PowerShell command Get-VMSnapshotNYC-VM1.
D.
Run the Windows PowerShell command Export-VMSnapshot NYC-VM1.
Why not use checkpoint?
I think use checkpoint is the faster way to restore the vm
0
0
I do not think B is correct Save-VM is similar to putting a physical machine into a hibernate state (according to TechNet).
I found a description from a publication on Code-Plex: “Saving a VM stores the contents of memory before powering it off. A background WMI job is created to change the state.”
So how are going to update the VM if it is suspended??
I believe that A is the correct answer. Checkpoint.
0
0
A indeed is the correct answer.
0
0
Defenely A is correct!!!
0
0
If you use Hyper-V Manager you will see the term snapshot and if you use System Centre Virtual Machine Manager or SCVMM you will see checkpoint.
Answer A says: “From Hyper-V Manager”, but not from SCVMM, so it cannot be A
0
0
B is the correct answer from Hyper-V you can create snapshots only.
0
0
In Windows 2012 R2 in Hyper-V manager the term is Checkpoint. In Windows 2012 no R2 the term in Hyper-V manager is snapshot. I was happy that i had the two versions installed to check. There is no VMM mentioned.
0
0
Miki is right, A is the correct answer,
0
0
A – Checkpoint is the correct answer, see below links
The Save-VM cmdlet saves a virtual machine. This is similar to hibernating a physical machine.
http://technet.microsoft.com/en-us/library/hh848590.aspx
http://www.infoworld.com/article/2611339/virtualization/first-look–windows-server-2012-r2-hyper-v-shines-on.html
At least one change to terminology makes function naming more consistent. In the world of Hyper-V, the term “snapshot” has meant a point-in-time image of a system for later use, should it be necessary to roll back to a previous version. SCVMM has used the term “checkpoint” for the same functionality. Now, whereas Hyper-V Manager in Windows Server 2012 still called it a “snapshot,” Hyper-V Manager in the R2 release calls it a “checkpoint.” The only remaining exception is the PowerShell command Export-VMSnapshot. You’ll also find a Checkpoint-VM cmdlet that will take a snapshot of the specified VM. For all intents and purposes
0
0
I just build a VM in Hyper-V Manager, right clicked it and saw “Checkpoint” as an option, I am voting “A” as the correct answer.
0
0
Do you remeber the 2 new questions?
0
0