MENU
Your organization is running a critical production database on a virtual machine (VM) on Compute Engine. The VM has an ext4-formatted persistent disk for data files. The database will soon run out of storage space. You need to implement a solution that avoids downtime. What should you do?
Suggested Answer: A
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
https://cloud.google.com/sql/docs/mysql/backup-recovery/backing-up#locationbackups You can use a custom location for on-demand and automatic backups. For a complete list of valid location values, see the Instance locations.
35 comments · newest first
VI
Viola
11 months ago
D might work, but it seems unnecessary.
HE
Helga
11 months ago
Wait, can you really resize without downtime?
VI
Virgina
11 months ago
C sounds too complicated for no downtime.
OM
Omer
11 months ago
I think B is better for checking the new space.
GE
Gerardo
12 months ago
Option A is the way to go! Just resize and extend.
CA
Carylon
12 months ago
I recall that creating a new disk and moving files could be a solution, but I'm not confident if option D is the best approach for avoiding downtime.
AN
Anissa
1 year ago
I practiced a similar question where we had to avoid downtime, and I feel like option C could lead to more downtime because of the unmounting and restarting process.
AL
Alexia
1 year ago
I'm not entirely sure, but I think fdisk is more for partitioning rather than resizing. So, option B might not be the best choice.
AL
Alba
1 year ago
I remember studying about resizing persistent disks, and I think option A sounds right since it mentions using resize2fs after increasing the disk size.
RA
Raul
1 year ago
I'm leaning towards option D - creating a new disk and moving the database files over. That seems like the safest approach to me, and it avoids having to resize the existing disk.
SH
Shenika
1 year ago
Okay, this is a good one. I like the idea of creating a snapshot and restoring to a larger disk in option C. That way, I can avoid any downtime and make sure the data is migrated properly.
KR
Krissy
1 year ago
Hmm, I'm a bit unsure about this one. Increasing the disk size is probably the right approach, but I'm not sure if I should use resize2fs or fdisk. I'll have to double-check the details on those commands.
CH
Chau
1 year ago
This seems like a straightforward question about expanding storage for a database. I think I'll go with option A - increasing the disk size and using resize2fs to extend the file system.
RE
Regenia
1 year ago
I'm not sure about this one. The syntax is a bit different from what I'm used to seeing in the Cobra SDK examples. I'll need to review the documentation carefully before making a decision.
SH
Sheron
1 year ago
Maybe the database is running out of space because it's storing all the memes the IT team has been sharing. Gotta love those cloud-based comedy clubs!
AS
Asha
1 year ago
Haha, those IT memes must be taking up a lot of space! Good thing we can easily expand the storage without downtime.
RE
Renato
1 year ago
C) In the Google Cloud Console, create a snapshot of the persistent disk, restore the snapshot to a new larger disk, unmount the old disk, mount the new disk, and restart the database service.
AN
Annabelle
1 year ago
A) In the Google Cloud Console, increase the size of the persistent disk, and use the resize2fs command to extend the disk.
RU
Ruthann
1 year ago
Option B? Really? Verifying the new space with fdisk? That's so 90s. This is the cloud, folks, let's live in the present!
MA
Malinda
1 year ago
Option A is the way to go! Resizing the disk and extending the file system is a simple one-step solution. No need to complicate things.
KA
Kaitlyn
1 year ago
User 3: Thanks for the advice, I'll go with option A then.
TA
Tawanna
1 year ago
User 2: I agree, it's the simplest solution.
ED
Edison
1 year ago
User 1: Option A is definitely the best choice.
GR
Gracie
1 year ago
I'd go with option D. Creating a new disk and moving the files over seems like the safest and most straightforward approach.
KI
King
1 year ago
That's true, option D is a straightforward solution to the storage space issue.
LU
Luke
1 year ago
I agree, creating a new disk and transferring the files seems like the best way to avoid downtime.
KI
Kiley
1 year ago
Option D sounds like a good plan. Moving the files to a new disk is a safe bet.
FE
Fernanda
2 years ago
Option C looks like the best choice to me. Avoiding downtime is the key requirement, and that's exactly what the snapshot and restore process does.
CA
Carylon
1 year ago
It might be faster, but there could be risks involved. Using a snapshot is a safer option.
AL
Alecia
1 year ago
But wouldn't resizing the disk directly be faster?
CA
Cary
1 year ago
I agree, using a snapshot to restore to a larger disk will minimize downtime.
BR
Brande
1 year ago
Option C looks like the best choice to me.
MI
Mi
2 years ago
I'm not sure about option A. I think option C might be a safer choice as it involves creating a snapshot and restoring it to a new larger disk to avoid any potential issues.
JO
Johnna
2 years ago
I agree with Jacki. Option A seems like the most efficient solution to avoid any downtime for our critical production database.
JA
Jacki
2 years ago
I think option A is the best choice because it allows us to increase the size of the persistent disk and extend the disk without any downtime.