Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs a mission-critical financial transaction service on Google Cloud backed by an AlloyDB for PostgreSQL database cluster. The organization's disaster recovery and business continuity policy specifies that the database must achieve a Recovery Point Objective (RPO) of near zero to safeguard against accidental data corruption or malicious table drops, with the ability to restore the database to any specific moment in time over the preceding two weeks.
Which backup and recovery strategy should you configure to meet these requirements?
AlloyDB continuous backup and recovery is a native data protection mechanism that continuously records incremental storage changes and transaction logs. This capability allows administrators to restore an existing cluster to any precise moment in its recent history with microsecond granularity, eliminating data loss gaps between scheduled backup intervals.

Continuous backup and recovery is the native managed solution specifically designed for relational database point-in-time recovery. It achieves an RPO of zero and provides microsecond-level recovery points without requiring custom scheduling logic, external orchestration, or disruptive full-database lock operations.
Automated and on-demand backups capture complete, discrete copies of database files at specific scheduled intervals (such as once per day) and store them as independent file-based resources.
The workload only required periodic archival snapshots where a 24-hour RPO was acceptable and there was no requirement for microsecond-level point-in-time recovery.
This approach uses custom scripts orchestrated by Cloud Scheduler and Cloud Run to dump database contents into file formats (such as CSV, SQL dumps, or Parquet) and upload them to Cloud Storage for long-term cold retention.
The objective was multi-year regulatory compliance archiving of static historical data where cold storage economics outweigh rapid disaster recovery requirements.
Read replicas replicate database transactions asynchronously or synchronously to secondary instances in other zones or regions to provide high read throughput and infrastructure failover capability.
The primary requirement was regional disaster recovery to survive a complete Google Cloud regional outage with minimal failover downtime for high-availability read traffic.
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