Google Professional Cloud Database Engineer Question 24
Select 3Google Cloud PlatformYour organization runs a critical e-commerce application on a MySQL database hosted on Google Cloud SQL. The application must maintain high availability with minimal downtime, even during regional outages, and should have a recovery option to restore data in case of accidental deletion. Which combination of strategies should you implement to meet these requirements?
- A
Enable Cross-Region Replicas for the Cloud SQL instance.
- B
Set up a highly available Cloud SQL instance with automatic failover.
- C
Configure daily backups for the Cloud SQL instance.
- D
Rely exclusively on a single-zone instance since it reduces latency.
- E
Use a Memorystore instance as a cache to reduce database load.
Show answer and explanation
Correct answers: A, B, C
Explanation
To achieve high availability and disaster recovery for the MySQL database, you need to combine strategies that protect against regional outages, zonal failures, and accidental data loss. Cross-Region Replicas provide redundancy across regions, a highly available instance with failover handles zonal outages, and backups enable data restoration. A single-zone instance and a caching layer like Memorystore do not meet these requirements.
- A. Correct.
Cross-Region Replicas ensure the database remains available in case of a regional outage, providing high availability across regions.
- B. Correct.
Setting up a highly available Cloud SQL instance with automatic failover protects against zonal failures and ensures minimal downtime.
- C. Correct.
Daily backups allow you to restore the database to a previous state in case of accidental deletion or corruption, providing disaster recovery capabilities.
- D. Incorrect.
Using a single-zone instance reduces latency but introduces a single point of failure, making it unsuitable for high availability or disaster recovery requirements.
- E. Incorrect.
Memorystore is useful for caching to improve performance but does not address high availability or disaster recovery requirements for the database.