Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Database Engineer Exam - Topic 2 Question 46 Discussion

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?
A) In the Google Cloud Console, increase the size of the persistent disk, and use the resize2fs command to extend the disk.
B) In the Google Cloud Console, increase the size of the persistent disk, and use the fdisk command to verify that the new space is ready to use
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.
D) In the Google Cloud Console, create a new persistent disk attached to the VM, and configure the database service to move the files to the new disk.

Google Professional Cloud Database Engineer Exam - Topic 2 Question 46 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam
Question #: 46
Topic #: 2
[All Professional Cloud Database Engineer Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

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.


by Wilson at Sep 18, 2024, 12:00 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Viola
7 months ago
D might work, but it seems unnecessary.
upvoted 0 times
...
Helga
8 months ago
Wait, can you really resize without downtime?
upvoted 0 times
...
Virgina
8 months ago
C sounds too complicated for no downtime.
upvoted 0 times
...
Omer
8 months ago
I think B is better for checking the new space.
upvoted 0 times
...
Gerardo
8 months ago
Option A is the way to go! Just resize and extend.
upvoted 0 times
...
Carylon
9 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.
upvoted 0 times
...
Anissa
9 months 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.
upvoted 0 times
...
Alexia
9 months 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.
upvoted 0 times
...
Alba
9 months 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.
upvoted 0 times
...
Raul
9 months 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.
upvoted 0 times
...
Shenika
9 months 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.
upvoted 0 times
...
Krissy
9 months 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.
upvoted 0 times
...
Chau
9 months 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.
upvoted 0 times
...
Regenia
9 months 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.
upvoted 0 times
...
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!
upvoted 0 times
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.
upvoted 0 times
...
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.
upvoted 0 times
...
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.
upvoted 0 times
...
...
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!
upvoted 0 times
...
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.
upvoted 0 times
Kaitlyn
1 year ago
User 3: Thanks for the advice, I'll go with option A then.
upvoted 0 times
...
Tawanna
1 year ago
User 2: I agree, it's the simplest solution.
upvoted 0 times
...
Edison
1 year ago
User 1: Option A is definitely the best choice.
upvoted 0 times
...
...
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.
upvoted 0 times
King
1 year ago
That's true, option D is a straightforward solution to the storage space issue.
upvoted 0 times
...
Luke
1 year ago
I agree, creating a new disk and transferring the files seems like the best way to avoid downtime.
upvoted 0 times
...
Kiley
1 year ago
Option D sounds like a good plan. Moving the files to a new disk is a safe bet.
upvoted 0 times
...
...
Fernanda
1 year 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.
upvoted 0 times
Carylon
1 year ago
It might be faster, but there could be risks involved. Using a snapshot is a safer option.
upvoted 0 times
...
Alecia
1 year ago
But wouldn't resizing the disk directly be faster?
upvoted 0 times
...
Cary
1 year ago
I agree, using a snapshot to restore to a larger disk will minimize downtime.
upvoted 0 times
...
Brande
1 year ago
Option C looks like the best choice to me.
upvoted 0 times
...
...
Mi
1 year 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.
upvoted 0 times
...
Johnna
1 year ago
I agree with Jacki. Option A seems like the most efficient solution to avoid any downtime for our critical production database.
upvoted 0 times
...
Jacki
1 year 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.
upvoted 0 times
...

Save Cancel