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

Google Exam Professional Cloud Database Engineer 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.


Contribute your Thoughts:

Gracie
2 days 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
...
Fernanda
13 days 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
...
Mi
17 days 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
28 days 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 months 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
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77