Google Professional Cloud Database Engineer Question 158
Single answerGoogle Cloud PlatformYour company runs a critical e-commerce application on Google Cloud using Cloud SQL for the database backend. The application must ensure minimal downtime (less than 1 hour) in the event of a disaster, and it cannot afford to lose more than 5 minutes of transactions. How should you configure the database solution to meet the required recovery time objective (RTO) and recovery point objective (RPO)?
- A
Configure Cross-Region Replicas for Cloud SQL and enable automated backups.
- B
Set up a Read Replica in the same region and enable automated backups.
- C
Use Cloud SQL point-in-time recovery and rely on manual failover.
- D
Deploy a multi-regional Cloud Spanner database.
Show answer and explanation
Correct answer: A
Explanation
To meet the RTO of less than 1 hour and RPO of 5 minutes, you need a solution that provides disaster recovery across regions with minimal data loss. Cross-Region Replicas ensure data is replicated to another region, and failover can be automated to minimize downtime. Automated backups further ensure data integrity. The other options either do not meet the RTO/RPO requirements or introduce unnecessary complexity.
- A. Correct.
This option is correct. Cross-Region Replicas provide high availability and disaster recovery capabilities, ensuring that data is replicated to another region. Automated backups help meet RPO requirements, while the cross-region setup ensures that failover to the replica can meet the RTO requirement.
- B. Incorrect.
This option is incorrect. A Read Replica in the same region cannot provide disaster recovery if the entire region becomes unavailable. It also does not guarantee an RPO of 5 minutes, as backups alone may not capture the most recent transactions.
- C. Incorrect.
This option is incorrect. Point-in-time recovery can help with data restoration, but it does not meet the RTO requirement of less than 1 hour, as manual failover and recovery can take significant time.
- D. Incorrect.
This option is incorrect. While Cloud Spanner provides multi-regional setups and high availability, it may be overkill for the given scenario. Additionally, migrating an existing Cloud SQL database to Spanner would introduce complexity and downtime.