Boot disk images in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Boot Disk Image Selection Behavior

You create a new Compute Engine VM instance in Google Cloud Platform and specify a boot disk image family instead of a specific image version. What happens when the instance boots?

A The VM boots using the latest non-deprecated image from the specified image family.

B The VM boots using the oldest image available in the image family.

C The VM fails to boot because a specific image version is required.

D The VM boots using a random image from the image family.

💡 Hint

Think about how GCP manages image families to keep instances updated.

When you specify an image family, GCP automatically selects the latest non-deprecated image from that family to boot the VM. This ensures your VM uses the most recent stable image.

❓ Architecture

intermediate

Custom Boot Disk Image Usage

You want to create multiple VM instances with a custom boot disk image that includes pre-installed software. Which approach is best to ensure all instances use this custom image?

A Use the default public image and run a startup script to install software on each VM.

B Manually install the software on each new VM after creation.

C Create a custom image from a configured VM and specify this image as the boot disk for all new instances.

D Create snapshots of the boot disk after each VM is created.

💡 Hint

Consider how to reuse a configured disk image efficiently across multiple VMs.

Creating a custom image from a configured VM allows you to reuse that image as the boot disk for multiple instances, ensuring consistency and saving setup time.

❓ security

advanced

Securing Boot Disk Images

Which practice best enhances security when using boot disk images in Google Cloud Platform?

A Use only public images without modification to avoid configuration errors.

B Regularly update custom images with security patches before creating new instances.

C Disable encryption on boot disks to improve performance.

D Share boot disk images publicly to allow community review.

💡 Hint

Think about how to keep your VM images safe from vulnerabilities.

Regularly updating custom images with security patches ensures that new instances start with the latest protections, reducing exposure to known vulnerabilities.

❓ Configuration

advanced

Boot Disk Encryption Configuration

You want to create a VM instance with a boot disk encrypted using a customer-managed encryption key (CMEK). Which configuration step is required?

A Specify the CMEK key resource in the disk encryption key field when creating the boot disk.

B Encrypt the boot disk manually after the VM instance is created.

C Use the default Google-managed encryption key and then switch to CMEK later.

D Create the VM instance without encryption and enable CMEK in the instance settings.

💡 Hint

Consider how encryption keys are applied during disk creation.

To use CMEK for a boot disk, you must specify the customer-managed key during the disk creation process. This ensures the disk is encrypted with your key from the start.

✅ Best Practice

expert

Optimizing Boot Disk Image Management at Scale

Your organization manages hundreds of VM instances across multiple projects. You want to maintain consistent boot disk images and simplify updates. Which strategy best achieves this?

A Create custom images separately in each project to avoid cross-project dependencies.

B Use only public images and configure each VM with startup scripts for software installation.

C Manually update each VM instance's boot disk image individually when needed.

D Maintain a centralized custom image repository in a shared project and reference these images in all projects.

💡 Hint

Think about centralizing resources to improve consistency and ease management.

Centralizing custom images in a shared project allows all projects to use the same trusted images, simplifying updates and ensuring consistency across the organization.