Q: 7
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 your production workloads. What should you do?
Options
Discussion
I'm not convinced by B or C here. Those both add steps and could still hit performance, especially with a huge 5TB DB. Serverless exports (A) are designed to avoid production impact and automate the job, which matches minimal ops overhead. I'm pretty sure that's the intent, since D is a classic trap for high load cases.
I don't think it's D, that's more manual and can load the prod instance. A avoids that risk and automates the job.
D , since a lot of practice dumps and labs show using mysqldump on the primary for exports. Thought it was the standard way, but maybe there's a better GCP-native route. Would double-check the official guide because these scenarios can trip you up.
A imo, serverless exports are made for this use case. Minimal ops work and no extra stress on prod DB, which you need with 24/7 uptime. The other options add risk or steps, so I think A fits best. Disagree?
B or C here. Creating a read replica and using mysqldump seems like a safe choice since it won't affect the primary workload directly, which matters for 24/7 uptime. The official Google cloud SQL docs and some practice exams cover backup strategies pretty well, but I might be missing something subtle about serverless exports vs replica dumps.
Had something like this in a mock, definitely A. Serverless exports go straight to Cloud Storage and don't put extra load on prod. The other options risk downtime or add manual steps, pretty sure that's not what Google tests here. Agree?
Not D, running mysqldump on primary is risky for prod load. A is built for low overhead and safety.
Option D (if the DB is under heavy load, direct mysqldump could actually cause downtime).
A , serverless exports in Cloud SQL are built for this. D is a typical pitfall but it hits the live database and adds risk. I think A's what Google expects for least ops overhead, unless I'm missing some special scenario.
Ugh, Google keeps adding new features after every cert update. Not D, A is what they want now. Serverless exports let you dump to Cloud Storage without touching the prod instance, so there's less risk and way less manual work involved. Pretty sure that's what they're testing here, but happy to hear arguments for B or C if I'm missing something.
Be respectful. No spam.