Exam Professional Cloud Architect topic 1 question 108 discussion

Ans) C and D Cloud SQL. If you use Cloud SQL, the fully managed Google Cloud MySQL database, you should enable automated backups and binary logging for your Cloud SQL instances. This allows you to perform a point-in-time recovery, which restores your database from a backup and recovers it to a fresh Cloud SQL instance

C. Binary logging D. Automated backups

Binary logging and automated backups

Prerequisites for creating a read replica Before you can create a read replica of a primary Cloud SQL instance, the instance must meet the following requirements: Automated backups must be enabled. Binary logging must be enabled which requires point-in-time recovery to be enabled. Learn more about the impact of these logs. At least one backup must have been created after binary logging was enabled. https://cloud.google.com/sql/docs/mysql/replication#requirements

CD Before being able to create a read replica, you have to make sure "binary logging and automated backup" are enabled. So picking only D or C without the other one makes no sense. https://cloud.google.com/sql/docs/mysql/replication/create-replica

The correct answers are C. & D. Binary logging is a feature of MySQL that records all changes made to the database. This log can be used to restore the database to a previous state in case of a failure. Automated backups are regularly scheduled backups of the database. They are the most reliable way to ensure that data is not lost in case of a catastrophic failure.

C and D. Read replicas wont work in this case.

C. Binary logging D. Automated backups

Binary logging records changes to the data, which can help you recover data and minimize data loss during an unexpected failure. Automated backups create regular backups of your database, allowing you to restore the database to a specific point in time in case of a catastrophic failure.

backup data automatically

CD => the answer B is for performance issue. The question focus on data loss prevention.

B and D: No need to explain D, but B... here is why When you set up a read replica, automaticaly binary logging is activated. Then, in case of desaster, you can promote manually a read replica and it will have all data before the desaster occurs.

B and D are correct answers as per below reference, 1. Before you can create a read replica of a primary Cloud SQL instance, the instance must meet the following requirements: Automated backups must be enabled. 2. Binary logging must be enabled which requires point-in-time recovery to be enabled. Learn more about the impact of these logs. 3. At least one backup must have been created after binary logging was enabled. It means creating read replica already covers binary logging. Please read the following references for more information https://cloud.google.com/solutions/cloud-sql-mysql-disaster-recovery-complete-failover-fallback https://medium.com/google-cloud/cloud-sql-recovering-from-regional-failure-in-10-minutes-or-less-mysql-fc055540a8f0 Replication in Cloud SQL | Cloud SQL for MySQL | Google Cloud

C and D are correct answers, Backups help you restore lost data to your Cloud SQL instance. Additionally, if an instance is having a problem, you can restore it to a previous state by using the backup to overwrite it. Enable automated backups for any instance that contains necessary data. Backups protect your data from loss or damage. Enabling automated backups, along with binary logging, is also required for some operations, such as clone and replica creation. https://cloud.google.com/sql/docs/mysql/backup-recovery/backups#what_backups_provide

C. Binary logging D. Automated backups Binary logging is a feature of MySQL that records all changes made to the database in a binary log file. By enabling binary logging on your Cloud SQL instance, you can use the log file to recover your database in case of catastrophic failure. Automated backups are a feature of Cloud SQL that allows you to automatically create and retain backups of your database. By enabling automated backups, you can restore your database in case of catastrophic failure or other data loss events. Option A, sharding, is not a recommended approach. Sharding is a technique for distributing data across multiple servers to improve performance and scalability. While sharding can help to improve the performance of a database, it is not specifically designed to protect against data loss in case of catastrophic failure.

cd is ok

I see Read Replicas as more of a performance thing, than DR thing