Your team is running a Cloud SQL for MySQL instance with a 5 TB database that must be available 24/7. You need to save database backups on object storage with minimal operational overhead or risk to…

Question

Options

• AUse Cloud SQL serverless exports.
• BCreate a read replica, and then use the mysqldump utility to export each table.
• CClone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
• DUse the mysqldump utility on the primary database instance to export the backup.

• A
  78% (38)
• B
  4% (2)
• C
  4% (2)
• D
  14% (7)

Explanation

Cloud SQL serverless exports are the Google-recommended approach for exporting large databases with minimal impact on production. Serverless exports offload the export operation to a separate serverless system rather than running it on the primary instance, meaning the 24/7 production workload is not degraded during the backup process. The exported data is written directly to Cloud Storage (object storage). Option B (read replica + mysqldump per table) is operationally complex, slow for 5 TB, and error-prone. Option C (clone + mysqldump) involves cloning a 5 TB instance - which takes time and incurs clone instance costs - before running a slow mysqldump. Option D (mysqldump on the primary) directly impacts production performance during the export, which violates the 24/7 availability requirement.

No community discussion yet for this question.