Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.
Deleting a snapshot does not affect the current state of the virtual machine1. Therefore, if the “Service 1.5” snapshot is deleted, the current state of the virtual machine will remain the same. It will not revert to any of the other snapshots like “Service 2”, “Service 1”, or “Photon-01”. So, none of the options A, B, or C are correct. The current state of the virtual machine after deleting the “Service 1.5” snapshot will still be the state it was in at the time of the deletion. However, please note that you will not be able to return to the “Service 1.5” state once the snapshot is deleted.
D. As said from MacDiesl1010, if you delete the snapshot, it just consolidate it to the vmdk, but you don't have any rollback. If you want to comeback to snapshot Service 1, you have to do "Revert to", so the "You are here" move under Service 1.
Answer is B. However, the question is a little misleading because well yeah, no matter what snapshot you delete, the VM in it's current configuration doesn't change, so it most likely resembles the most recent snapshot, deleted or not. However the question is asking about the snapshots not the VM itself. Deleting a snapshot above the you are here commits to the parent snapshot. Thus the answer is B
B is the answer. When you delete a snapshot the blocks are written to the parent. In this case the parent of Service'1.5 is Service#1, so B is the answer. It cannot be D because you've deleted it!
Note: Deleting a single snapshot preserves the current state of the virtual machine and does not affect any other snapshot
https://kb.vmware.com/s/article/1023657
B is the correct answer. I just reproduced it in vCenter. NOTE: In order to get the structure (2 snaps under Service 1 not cascaded like Photon-01 -> Service 1) you need to revert to Snapshot Service 1 before making Service 2.
Correction...
NOTE: In order to get the structure (2 snaps under Service 1 not cascaded like Photon-01 -> Service 1) you need to revert to Snapshot Service 1 before making Service 1.5.
D is correct, see the "you Are Here" indication.
It means that the current state of the VM is under that snapshot.
Even if deleted, the VM is still in the same state of the snapshot as no revert was executed in the question.
But a revert HAS been executed. To get that structure requires the following in order: Created Service#1, Created Service#2, Reverted to Service#1, Created Service#1.5. That's the revert. So if you delete Service#1.5, the answer can't be 1.5 because you've deleted it. It can only be Service#1. Therefore the answer is B.
Answer is D:
Note: Deleting a single snapshot preserves the current state of the vhttps://www.examtopics.com/exams/vmware/1v0-2120/view/7/#irtual machine and does not affect any other snapshot.
https://kb.vmware.com/s/article/1023657
Yes, but if you've deleted Service#1.5, how can the answer be 1.5 if it no longer exists. You deleted it, so it cannot be the answer!
upvoted 1 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
MacDiesel1010
Highly Voted 7 months, 3 weeks agoBesx
Most Recent 4 days, 10 hours ago6d5bf16
5 months, 1 week agoCheMetto
7 months agoKeif
9 months agoKeif
9 months agomarkey164
10 months, 2 weeks agoJokerRWild
1 year, 1 month agoRepic_NJ
1 year, 3 months agoRepic_NJ
1 year, 3 months agoRepic_NJ
1 year, 3 months agoMaxMink
1 year, 3 months agowpestan
1 year, 4 months agodayanhay
1 year, 4 months agomarkey164
10 months, 2 weeks agopepi_5121
1 year, 4 months agomacxsz
1 year, 6 months agoTakingExams_Forever
1 year, 7 months agothrowaway_account
1 year, 7 months agomarkey164
10 months, 2 weeks ago