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?
Suggested Answer: C
Get Premium Professional Cloud Database Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
44 comments · newest first
QU
Quentin
11 months ago
D is too risky, it could impact performance during the dump.
JU
Juan
11 months ago
Wait, can you really use serverless exports for this size?
TA
Tammi
11 months ago
C sounds complicated, why not just use A?
RE
Ressie
11 months ago
I disagree, B seems more reliable for backups.
CH
Chauncey
12 months ago
A is the best option for minimal overhead!
LI
Lizbeth
12 months ago
Cloning the instance sounds familiar, but I feel like it might be more complex than just using serverless exports.
RO
Ronny
1 year ago
I think creating a read replica could work, but I wonder if it would really reduce the risk to production workloads.
SI
Silvana
1 year ago
I'm not entirely sure, but using mysqldump on the primary instance might not be the best choice for 24/7 availability.
RA
Rasheeda
1 year ago
I remember discussing the Cloud SQL serverless exports in class; it seems like a good option for minimizing overhead.
AL
Allene
1 year ago
Whew, a 5 TB database backup is no small task. I'll need to pay close attention to the details and make sure I don't miss anything important.
SU
Sunny
1 year ago
This is a good test of our Cloud SQL knowledge. I'm confident I can work through this step-by-step and arrive at the best solution.
ME
Merrilee
1 year ago
Okay, I think I've got a strategy here. I'll start by considering the operational overhead and risk factors for each approach.
AL
Alecia
1 year ago
Hmm, I'm a bit unsure about this. I'll need to review the Cloud SQL documentation to make sure I understand the differences between the backup options.
GL
Glen
1 year ago
This looks like a tricky one. I'll need to think through the pros and cons of each option carefully.
AN
Annett
1 year ago
Hmm, I'm a bit unsure about the steps in the job analysis process. I'll need to review my notes to make sure I understand this properly.
CA
Carrol
1 year ago
I'm feeling a little lost on this one. The wording of the question is throwing me off, and I'm not entirely sure how to approach solving it. I'll need to re-read the details carefully and try to break it down.
AH
Ahmed
1 year ago
Okay, let's see. If "disable-aging" is executed, that means the MAC addresses won't be removed from the FDB over time, right? So option C seems like the most likely answer - aging will be disabled for both local and remote MAC addresses in the VPLS.
LO
Lourdes
1 year ago
Hey, at least it's not a 50 TB database, right? That would be a real backup nightmare!
ON
Ona
1 year ago
C) Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
NU
Nu
1 year ago
B) Create a read replica, and then use the mysqldump utility to export each table.
VI
Vincent
1 year ago
A) Use Cloud SQL serverless exports.
JA
Jamal
1 year ago
D) Directly mysqldump the primary database? Yikes, that could really impact my production workloads. Not a fan of that idea.
MI
Mitzie
1 year ago
C) Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
CU
Curtis
1 year ago
B) Create a read replica, and then use the mysqldump utility to export each table.
DE
Detra
1 year ago
A) Use Cloud SQL serverless exports.
JU
Judy
1 year ago
C) Cloning the instance and then mysqldump? Seems a bit overkill for a 5 TB database. I'll pass on that one.
GI
Giuseppe
1 year ago
C) Cloning the instance and then mysqldump? Seems a bit overkill for a 5 TB database. I'll pass on that one.
LA
Laurel
1 year ago
B) Create a read replica, and then use the mysqldump utility to export each table.
VI
Vi
1 year ago
A) Use Cloud SQL serverless exports.
HA
Haydee
2 years ago
B) Creating a read replica and using mysqldump sounds like a good plan. Keeps the production workload safe.
NE
Nelida
1 year ago
User 4: Using mysqldump on the primary database instance seems like a risky option for such a critical database.
MI
Mirta
1 year ago
User 3: Cloning the Cloud SQL instance and then using mysqldump to export the data could work too.
TY
Ty
1 year ago
User 2: Creating a read replica and using mysqldump sounds like a good plan. Keeps the production workload safe.
CA
Carrol
1 year ago
User 1: I think using Cloud SQL serverless exports would be the best option.
DE
Denae
1 year ago
B) Creating a read replica and using mysqldump sounds like a good plan. Keeps the production workload safe.
KA
Karima
1 year ago
A) Use Cloud SQL serverless exports.
PA
Paul
2 years ago
That's a good point, but I still think serverless exports are more efficient in this scenario.
OR
Ora
2 years ago
I disagree, I believe option C is better because cloning the instance ensures data consistency.
ER
Erin
2 years ago
A) Cloud SQL serverless exports seem like the easiest option. Minimal operational overhead is exactly what I need!
JE
Jerry
1 year ago
C) Cloning the instance and using mysqldump could work as well, but it might be more complex.
JO
Jospeh
1 year ago
A) True, but I prefer the simplicity of Cloud SQL serverless exports.
FR
France
1 year ago
B) Creating a read replica and using mysqldump sounds like a good option too.
PR
Precious
2 years ago
A) Cloud SQL serverless exports seem like the easiest option. Minimal operational overhead is exactly what I need!
PA
Paul
2 years ago
I think option A is the best choice for minimal operational overhead.