You are deploying a Cloud SQL for MySQL database to serve a non-critical application. The database size is 10 GB and will be updated every night with data stored in a Cloud Storage bucket. The databas

Designing Cloud SQL solutions for availability and cost

Question

You are deploying a Cloud SQL for MySQL database to serve a non-critical application. The database size is 10 GB and will be updated every night with data stored in a Cloud Storage bucket. The database serves read-only traffic from the application during the day. The data locality requirement of this application mandates that data must reside in a single region. You want to minimize the cost of running this database while maintaining an RTO of 1 day. What should you do-

Options

ACreate a Cloud SQL for MySQL instance with high availability (HA) enabled. Configure automated
BCreate a Cloud SQL for MySQL instance with high availability (HA) disabled. Create a read replica
CCreate a Cloud SQL for MySQL instance with high availability (HA) disabled. Create a read replica
DCreate a Cloud SQL for MySQL instance with high availability (HA) disabled. Configure automated

Explanation

The correct answer is D: Cloud SQL with HA disabled and automated backups configured. The application is non-critical, read-only during the day, single-region, and has a lenient RTO of 1 day. High availability (HA) adds a standby instance cost and is unnecessary here since 1-day RTO allows for a backup restore. A read replica (options B and C) is also unnecessary because the single primary can handle read-only traffic without the added cost of a replica. Automated backups satisfy the 1-day RTO by allowing point-in-time restoration within that window. This configuration is the minimum viable, lowest-cost setup that still meets all stated requirements.

Topics

#Cloud SQL#Disaster Recovery#Cost Optimization#Automated Backups

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice