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 Architect (PR000213) Exam - Topic 1 Question 88 Discussion

A production database virtual machine on Google Compute Engine has an ext4-formatted persistent disk for data files The database is about to run out of storage space How can you remediate the problem with the least amount of downtime?
A) In the Cloud Platform Console, increase the size of the persistent disk and use the resize2fs command in Linux.
B) Shut down the virtual machine, use the Cloud Platform Console to increase the persistent disk size, then restart the virtual machine.
C) In the Cloud Platform Console, increase the size of the persistent disk and verify the new space is ready to use with the fdisk command in Linux.
D) In the Cloud Platform Console, create a new persistent disk attached to the virtual machine, format and mount it, and configure the database service to move the files to the new disk.
E) In the Cloud Platform 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.

Google Professional Cloud Architect (PR000213) Exam - Topic 1 Question 88 Discussion

Actual exam question for Google's Professional Cloud Architect (PR000213) exam
Question #: 88
Topic #: 1
[All Professional Cloud Architect (PR000213) Questions]

A production database virtual machine on Google Compute Engine has an ext4-formatted persistent disk for data files The database is about to run out of storage space How can you remediate the problem with the least amount of downtime?

Show Suggested Answer Hide Answer
Suggested Answer: A

When an application becomes slow, the first step you should take is to gather information about the underlying cause of the problem. One way to do this is by inspecting the logs and metrics from the instances where the application is deployed. Google Cloud Platform (GCP) provides tools such as Cloud Logging and Cloud Monitoring that can help you to collect and analyze this information. By reviewing the logs and metrics from the instances, you may be able to identify issues such as resource shortages (e.g. CPU, memory, or disk), network problems, or application errors that are causing the performance issues. Once you have identified the underlying cause of the problem, you can take steps to resolve it.


by Vanna at Jul 16, 2024, 08:04 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sina
9 months ago
Wait, E involves a lot of steps! Is that really the best option?
upvoted 0 times
...
Shawna
9 months ago
D sounds complicated, why not just resize the existing disk?
upvoted 0 times
...
Teri
10 months ago
C seems unnecessary, fdisk isn't needed for just resizing.
upvoted 0 times
...
Katy
10 months ago
I think B is safer, though. Better to shut it down first.
upvoted 0 times
...
Valentin
10 months ago
Option A is the quickest way to do it!
upvoted 0 times
...
An
10 months ago
I recall that using fdisk is more about partitioning, so I’m leaning towards option A, but I’m not entirely sure if that’s the best approach for minimizing downtime.
upvoted 0 times
...
Joaquin
11 months ago
I practiced a similar question where we had to consider downtime, and I feel like option B might be too disruptive since it requires shutting down the VM.
upvoted 0 times
...
Marion
11 months ago
I think option A sounds right since it mentions using resize2fs, but I’m not confident about the least downtime part.
upvoted 0 times
...
Phung
11 months ago
I remember that increasing the disk size in the Cloud Console is usually a quick fix, but I'm not sure if I need to shut down the VM first.
upvoted 0 times
...
Teddy
11 months ago
I'm leaning towards option E. Taking a snapshot and restoring to a larger disk seems like a good way to avoid downtime and ensure the data is migrated properly. I'll need to double-check the steps, but this seems like the safest and most straightforward option.
upvoted 0 times
...
Jacob
11 months ago
Option D seems like the most comprehensive solution to me. Creating a new disk, moving the data, and reconfiguring the database service would ensure I don't run into any issues with the resizing. It might take a bit more time, but it's probably the most reliable approach.
upvoted 0 times
...
Renato
11 months ago
This looks like a straightforward question about increasing storage space for a database. I think option A is the best approach - it allows me to resize the disk without having to shut down the VM, which would minimize downtime.
upvoted 0 times
...
Lonna
11 months ago
Hmm, I'm a bit unsure about this one. I'm not familiar with the resize2fs command, so I'm not sure if that's the best way to go. Option B seems safer, even though it requires a restart. I'll have to look into the different commands and approaches more closely.
upvoted 0 times
...
Delila
11 months ago
I'm confident that option A, Skills-based Routing, is the best solution here. It allows us to route cases based on the agent's language and knowledge, which is exactly what the question is asking for.
upvoted 0 times
...
Dierdre
11 months ago
Ah yes, denormalization - that's the term I was looking for. Rejoining relations makes sense as the opposite of normalization. I feel confident about this one.
upvoted 0 times
...
Dyan
1 year ago
I'm just glad I don't have to deal with this problem. WhoDyanr has to do this is in for a fun time. Good luck, folks!
upvoted 0 times
...
Janey
1 year ago
Option E with the snapshot sounds like a good idea, but it might take a bit longer to execute. Still, better safe than sorry when it comes to production databases.
upvoted 0 times
Anthony
1 year ago
I think I would go with option B to increase the disk size and restart the virtual machine. It seems like the quickest solution with minimal downtime.
upvoted 0 times
...
Gaston
1 year ago
I agree, downtime can be costly so it's important to plan ahead for these situations.
upvoted 0 times
...
Ashley
1 year ago
Option E with the snapshot sounds like a good idea, but it might take a bit longer to execute. Still, better safe than sorry when it comes to production databases.
upvoted 0 times
...
...
Virgina
1 year ago
Haha, Option B is like the IT version of 'have you tried turning it off and on again?' Gotta love the classic reboot approach.
upvoted 0 times
Twana
1 year ago
C: Option B might be the easiest solution in this case.
upvoted 0 times
...
Bulah
1 year ago
B: I agree, it's a quick fix that often does the trick.
upvoted 0 times
...
Cecil
1 year ago
A: Yeah, sometimes a simple restart can work wonders.
upvoted 0 times
...
...
Omer
1 year ago
I'm leaning towards Option D. Creating a new disk and migrating the data seems like a more robust solution in case the resize operation goes wrong.
upvoted 0 times
Deangelo
1 year ago
But what if something goes wrong during the resize? Option D seems like a safer bet.
upvoted 0 times
...
Gail
1 year ago
I think Option B might be quicker though. Just shutting down the VM and resizing the disk could be faster.
upvoted 0 times
...
Whitley
1 year ago
Option D sounds like a good plan. It's always safer to move the data to a new disk.
upvoted 0 times
...
...
James
1 year ago
Option A seems like the easiest and quickest way to add more storage space without having to shut down the VM. The resize2fs command should do the trick.
upvoted 0 times
Zack
1 year ago
User 2
upvoted 0 times
...
Maryrose
1 year ago
User 1
upvoted 0 times
...
...
Sheron
1 year ago
I think option B) Shut down the virtual machine, increase the disk size, and then restart it is the safest choice to avoid downtime.
upvoted 0 times
...
Misty
1 year ago
I disagree, I believe option E) Create a snapshot of the persistent disk and restore it to a new larger disk is the way to go.
upvoted 0 times
...
Nada
1 year ago
I think the best option is A) Increase the size of the persistent disk and use the resize2fs command in Linux.
upvoted 0 times
...

Save Cancel