https://cloud.google.com/sql/docs/mysql/backup-recovery/backups not B: Automatic backups are made EVERY SINGLE DAY. You can set only the number of backups up to 365. Also you cannot choose your Archival storage as destination not C: You cannot setup "on-demand" backup. User would have to make backups manually every month. Also you cannot choose your Archival storage as destination not D: You cannot conver backup to export file. Also Coldline class is less cost-effective than Archival class. The only option left is "A" You can set up your job with any date/time schedule. You can export file to any storage with any storage class.

First need to understand backup vs export, two different concepts. - https://cloud.google.com/sql/docs/mysql/backup-recovery/backups A – yes, you can export data from Cloud SQL to Cloud Storage- https://cloud.google.com/sql/docs/mysql/import-export/exporting#cloud-sql Not B, C, D – be it automatic or on-demand backup, according to the doc “No, you can't export a backup. You can only export instance data.”

https://www.exam-answer.com/retain-month-end-copy-cloud-sql-mysql-database-three-years B is the correct answer.. I am not sure why people are posting wrong answers here.

A is the correct answer, as in a you can export as per your requirement and then moved it to archive class , but in b,c,d you can't do that

Option B is the best choice because it allows you to leverage the automatic first-of-the-month backup feature that is provided by Cloud SQL. Cloud SQL provides automated backups that can be configured to run at specific times, including the first of the month. By retaining the first-of-the-month backup for three years, you can be sure that you have a complete copy of the database for that month.

Answer A

Answer A is the correct one according to "https://cloud.google.com/blog/topics/developers-practitioners/scheduling-cloud-sql-exports-using-cloud-functions-and-cloud-scheduler" and "https://cloud.google.com/sql/docs/mysql/backup-recovery/backups#backups_versus_exports".

So Answer is A. You can't export back up. Very clear. https://cloud.google.com/sql/docs/mysql/backup-recovery/backups#can_i_export_a_backup

A is correct answer, Export the SQL month end data as a CSV file to cloud storage bucket, and move the data to Archival Storages for 3 years for audit purpose. https://cloud.google.com/sql/docs/mysql/import-export?authuser=1

A. Although Cloud SQL doesn't provide a built-in way to automate database exports, you can build your own automation tool using several Google Cloud components. https://cloud.google.com/sql/docs/mysql/import-export#automating_export_operations

had this question today

B is correct

A seems right to me key word: "month-end copy"

Correct Ans - C On demand backup You can create a backup at any time (Here we need backup a month-end copy of the database for three years). You can create on-demand backups for any instance, whether the instance has automatic backups enabled or not. Reason : 1) you can't export a backup. You can only export instance data so export option A is out from answer. Backups encompass the entire database. Exports can select specific contents. As per question You need to retain a month-end copy of the database not specific contents. 2) Automated backups are taken daily, within a 4-hour backup window. Up to seven most recent backups are retained, by default. *Cost** to store all backups .. 3) Option D not applicable **Coldline class** *Cost*

why not D? it is the only one that doesnt store it as Archive class, and since it is for Audit purposes this cant be used as Archive allows LESS than one access per year.

I would go with export not backup. Question stated that this is copy. In addition restore of three years old backup might be not possible in newer version. In addition you can retain max 365 backups.

As question itself states that we need month end backup, automatic backup runs daily which not required as per the question. https://cloud.google.com/sql/docs/mysql/backup-recovery/backups