Selecting a Cost-Effective Solution for Relational Data on Google Cloud Platform

Point-in-Time Recovery for Small Operational Data in One Geographic Location

Question

You want to select and configure a cost-effective solution for relational data on Google Cloud Platform.

You are working with a small set of operational data in one geographic location.

You need to support point-in-time recovery.

What should you do?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

https://cloud.google.com/sql/docs/mysql/backup-recovery/restore

In this scenario, you are looking for a cost-effective solution for managing relational data that requires point-in-time recovery. There are two Google Cloud Platform (GCP) services that can help with this requirement: Cloud SQL and Cloud Spanner.

Cloud SQL is a fully-managed relational database service that supports MySQL, PostgreSQL, and SQL Server. It offers high availability, automatic backups, and point-in-time recovery. You can configure Cloud SQL to use binary logging, which allows you to restore your database to a specific point in time. Additionally, Cloud SQL supports failover replicas that can automatically take over if the primary instance fails.

Therefore, Option A and Option B both recommend using Cloud SQL (MySQL) for point-in-time recovery, but they differ in their additional configuration options. Option A suggests enabling binary logging, whereas Option B suggests creating failover replicas. Both of these options can help improve availability and recovery time in the event of a failure. Therefore, either option can be a good choice depending on the specific needs of the application.

Cloud Spanner, on the other hand, is a globally-distributed, horizontally-scalable relational database service that supports SQL queries and ACID transactions. It is designed for high availability, fault tolerance, and strong consistency across multiple regions. While it also supports point-in-time recovery, it may be overkill for a small set of operational data in a single geographic location. Therefore, options C and D may not be the most cost-effective solutions in this scenario.

In summary, based on the requirement for a cost-effective solution for a small set of operational data in one geographic location with the need for point-in-time recovery, selecting Cloud SQL (MySQL) with either binary logging or failover replicas enabled would be the best option.