GCP Professional Cloud Architect Practice Question

An online media company runs the following on Google Cloud:

A Linux Compute Engine VM with a 500-GB persistent disk that contains user-generated content. Operations staff must be able to restore accidentally deleted files within minutes for any change made during the last 24 hours.
A Cloud SQL for PostgreSQL instance that must support restoration to any point in time within the past seven days and achieve a 15-minute recovery time objective (RTO).
A Cloud Storage bucket that holds compliance archives which must remain immutable and recoverable for seven years at the lowest possible cost. Which backup design best satisfies all requirements while keeping operational effort and cost to a minimum?

Rely on regional persistent disks for the VM without additional backups; create a cross-region read replica for Cloud SQL and disable automated backups; move the archive bucket to the Nearline storage class with no further configuration.
Create daily Compute Engine machine images; export the Cloud SQL database to Cloud Storage once per day; enable Dual-Region replication with Turbo Replication for the archive bucket.
Schedule hourly incremental snapshots of the VM's persistent disk stored in a multi-region location; enable automated backups with point-in-time recovery on the Cloud SQL instance; turn on Object Versioning and enforce a seven-year bucket retention policy for the archive bucket.
Protect the VM with a weekly Cloud Backup and DR policy; configure Cloud SQL in HA mode with daily automated backups only; enable Object Versioning for the archive bucket without a retention policy.

Report Issue

Answer Description

The VM's 24-hour file-level recovery goal is best met by an hourly snapshot schedule on its persistent disk; snapshots are incremental, can be mounted quickly as read-only disks, and allow fast file copy-back without shutting down the instance. Cloud SQL point-in-time recovery up to seven days is achieved by enabling automated backups plus write-ahead log archiving; this supports sub-hour RPOs and RTOs around 15 minutes. Long-term immutability for the archive bucket is enforced by turning on Object Versioning and applying a 7-year bucket retention policy, which prevents deletions or overwrites until the policy expires while using low-cost archive classes. The other options either fail the RPO/RTO targets (daily or weekly protection, exports instead of PITR) or omit the legally required retention lock.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.