Topic 1 Question 171
You are working with a Cloud SQL MySQL database at your company. You need to retain a month-end copy of the database for three years for audit purposes. What should you do?
Set up an export job for the first of the month. Write the export file to an Archive class Cloud Storage bucket.
Save the automatic first-of-the-month backup for three years. Store the backup file in an Archive class Cloud Storage bucket.
Set up an on-demand backup for the first of the month. Write the backup to an Archive class Cloud Storage bucket.
Convert the automatic first-of-the-month backup to an export file. Write the export file to a Coldline class Cloud Storage bucket.
ユーザの投票
コメント(17)
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.
👍 45TAvenger2021/03/14First 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.”
👍 16JieHeng2021/06/26A is incorrect because there is no need to create an export job as the export functionality is built-in with Cloud SQL- i would go with B
👍 4vamgcp2021/09/26
シャッフルモード