Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise runs mission-critical stateful workloads on Compute Engine virtual machines in the us-central1 region using zonal Persistent Disks. The architecture team needs to establish a backup and disaster recovery strategy that satisfies several operational and compliance requirements:
us-east1 regionWhich solution should you recommend to meet these requirements?
Take scheduled instant snapshots of the Persistent Disks in us-central1 and set a Cloud Storage object lifecycle rule to transition instant snapshots to Archive storage after 90 days.
Configure Persistent Disk Asynchronous Replication (PD Async Replication) between us-central1 and us-east1 for both operational recovery and 3-year compliance data retention.
Create regionally scoped snapshot schedules restricted strictly to us-central1 to avoid cross-region network egress costs, and export snapshots older than 30 days to a single-region Coldline Cloud Storage bucket in us-central1.
Configure automated snapshot schedules on the Persistent Disks that create standard snapshots stored in a multi-region location (us) for daily operational recovery, and configure scheduled archive snapshots stored in multi-region us for long-term monthly compliance retention.
Take scheduled instant snapshots of the Persistent Disks in us-central1 and set a Cloud Storage object lifecycle rule to transition instant snapshots to Archive storage after 90 days.
Configure Persistent Disk Asynchronous Replication (PD Async Replication) between us-central1 and us-east1 for both operational recovery and 3-year compliance data retention.
Create regionally scoped snapshot schedules restricted strictly to us-central1 to avoid cross-region network egress costs, and export snapshots older than 30 days to a single-region Coldline Cloud Storage bucket in us-central1.
Configure automated snapshot schedules on the Persistent Disks that create standard snapshots stored in a multi-region location (us) for daily operational recovery, and configure scheduled archive snapshots stored in multi-region us for long-term monthly compliance retention.
Compute Engine Persistent Disk snapshots are incremental point-in-time backups that capture block-level changes from persistent storage. Snapshots can be configured as either standard snapshots for short-term operational recovery or archive snapshots for low-cost, long-term data retention. They can be placed into regional or multi-regional Cloud Storage locations.
us) ensures that snapshots are automatically replicated across multiple regions, allowing immediate disk restoration in us-east1 during a regional outage in us-central1.This architecture leverages fully managed native Compute Engine capabilities (snapshot schedules, multi-region snapshot storage, and archive snapshot tiers) to satisfy RPO, cross-region disaster recovery, and long-term cost optimization with minimal operational overhead.