Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Cloud Digital Leader Scaling with Google Cloud operations Practice Question
Drag and drop the steps to recover a Compute Engine VM from a snapshot in the correct order.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Stop the VM, create a disk from the snapshot, detach the old boot disk, attach the new boot disk, start the VM
The recovery process involves using the snapshot to create a disk, detaching the old boot disk, attaching the new one, and starting the VM.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Stop the VM, create a disk from the snapshot, detach the old boot disk, attach the new boot disk, start the VM
Why this is correct
This is the correct order because you must stop the VM before modifying boot disks, create the new disk from the snapshot, detach the old boot disk, attach the new one, then start the VM.
- ✗
Create a disk from the snapshot, stop the VM, detach the old boot disk, attach the new boot disk, start the VM
Why it's wrong here
While you can create the disk before stopping the VM, it's safer to stop first to ensure consistency. However, the actual correct order requires stopping before detaching, so placing 'create disk' first is acceptable but not the prescribed order.
- ✗
Stop the VM, detach the old boot disk, create a disk from the snapshot, attach the new boot disk, start the VM
Why it's wrong here
This sequence detaches the existing boot disk before the replacement disk has been created from the snapshot. If the disk-creation step fails or is delayed, the VM is left without any bootable disk and cannot be restarted, forcing you to reattach the old disk as a recovery step. The correct practice is to create the new disk from the snapshot first, ensuring a valid replacement exists, then detach the old boot disk to avoid an unbootable intermediate state.
- ✗
Stop the VM, detach the old boot disk, attach the new boot disk, create a disk from the snapshot, start the VM
Why it's wrong here
In this order, the 'attach new boot disk' step is attempted before the disk resource has been created from the snapshot, so the attach operation will fail because the disk does not exist as a Cloud resource. Compute Engine requires a disk to be fully provisioned and in READY state before it can be attached to an instance; you cannot attach a placeholder or deferred resource. The disk must be created from the snapshot first, then attached, and only after that should the VM be started.
Go deeper
Related to this question
Learn chapter
Compute Options on Google Cloud
Key term
Compute Engine
Compute Engine is Google Cloud's Infrastructure-as-a-Service (IaaS) offering that lets you create and run virtual machines on Google's infrastructure.
Key term
Recovery
Recovery is the process of restoring systems, data, and operations after a security incident, failure, or disaster to return to normal functioning.
About these practice questions
One of 829 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.