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.
An organization runs critical stateful workloads on Google Compute Engine virtual machines (VMs) using attached persistent disks. To satisfy corporate governance and meet a Recovery Point Objective (RPO) of 24 hours, the operations team needs to automate backups under the following requirements:
Which solution should the cloud engineer implement?
Storage Transfer Service is a managed service designed for large-scale data transfers between cloud storage providers (such as AWS S3 or Azure Blob Storage) and Cloud Storage buckets, or between different Cloud Storage buckets and POSIX file systems.
The scenario required automated synchronization of unstructured file objects from an external cloud provider or on-premises POSIX file server into a Google Cloud Storage bucket with object lifecycle deletion rules.
While Cloud Storage Object Lifecycle Management can manage bucket object retention, persistent disk snapshots are managed directly within Compute Engine infrastructure rather than directly managed as regular bucket objects by users.
In Google Cloud Platform, snapshot schedules are native resource policies that automate the creation and lifecycle management of persistent disk snapshots. They allow administrators to define periodic backup cadences and auto-deletion rules without managing external schedulers or running custom script infrastructure.
Using native snapshot schedule resource policies is the Google Cloud recommended best practice for automated disk data protection. It completely eliminates operational burden, reduces configuration errors, and natively guarantees disk-level backup consistency on the required schedule.
This approach uses Cloud Scheduler as a cron trigger to invoke a Cloud Functions instance. The function executes custom code (such as Python using the Google Cloud Client Libraries or REST APIs) that queries active disks, creates new snapshots via API calls, lists existing snapshots, and issues deletion commands for snapshots with creation timestamps older than 14 days.
The workload required highly dynamic, programmatic backup workflows with custom pre-snapshot application freezing, external database quiescing scripts, or multi-cloud notification webhooks that native snapshot schedules do not support.
Prior to the introduction of native snapshot schedules in Compute Engine, scheduling Cloud Functions via Cloud Scheduler was a common workaround. Today, Google Cloud provides native resource policies specifically to avoid the complexity of custom-coded backup functions.
An Instance Template is an immutable resource definition used to create VM instances and Managed Instance Groups (MIGs). It specifies machine type, boot disk image, labels, network interfaces, and startup scripts for standardized VM provisioning.
The primary requirement was to define a blueprint for launching fleets of identical stateless compute instances with specific machine shapes and container configurations across multiple zones.
To protect disks associated with VMs in an instance group, snapshot schedules must still be defined as resource policies and attached directly to the individual persistent disks.
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