Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company needs to deploy several Compute Engine virtual machines (VMs) for an internal web application. Each VM requires a specific operating system, pre-installed proprietary business applications, and customized security configurations.
You want to deploy these instances quickly with a consistent baseline configuration while ensuring the baseline image is private and restricted only to your Google Cloud project.
Which image deployment strategy should you recommend?
Custom OS images are boot disk images that you create, own, and control within your Google Cloud project. They capture the operating system, installed software, dependencies, and configuration settings from an existing boot disk or external disk import, allowing you to use that standardized state to launch new virtual machines.
Using a custom image provides the perfect balance of security, private access, consistency, and fast provisioning speed. It eliminates repeated post-boot initialization and protects proprietary configurations inside your project boundary.
Public OS images are base operating system images provided and maintained by Google, open-source communities, and third-party vendors. A startup script is a script specified in VM metadata that runs automatically every time the virtual machine boots or restarts to perform initialization tasks.
You needed to deploy standard, unmodified open-source operating systems across projects where software requirements change continuously or where maintaining custom base images introduces unnecessary operational maintenance.
An image family points to the latest non-deprecated version of an OS image within a project. Public image projects (such as debian-cloud, ubuntu-os-cloud, or windows-cloud) are globally accessible projects managed by Google and third-party operating system vendors that host base public images for all Google Cloud users.
Your goal was to ensure virtual machines always provision from the latest patched version of a standard vendor OS (e.g., Debian or SUSE Linux) without proprietary customizations or strict private project isolation.
A blank persistent disk is an unformatted block storage volume provisioned without any file system, operating system, or bootloader.
You were attaching additional block storage volumes to an already running VM to provide secondary file storage or raw database partitions.
Change the inputs and watch how the outcome changes.

Pick a deployment strategy and workload requirement to see how each VM boots and whether the baseline stays private.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated