Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Architect Topic 1 Question 88 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 88
Topic #: 1
[All Professional Cloud Architect 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.


Contribute your Thoughts:

Dyan
1 months 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 months 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
7 days 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
19 days ago
I agree, downtime can be costly so it's important to plan ahead for these situations.
upvoted 0 times
...
Ashley
20 days 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 months 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
Bulah
2 days ago
B: I agree, it's a quick fix that often does the trick.
upvoted 0 times
...
Cecil
4 days ago
A: Yeah, sometimes a simple restart can work wonders.
upvoted 0 times
...
...
Omer
2 months 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 months ago
But what if something goes wrong during the resize? Option D seems like a safer bet.
upvoted 0 times
...
Gail
1 months 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 months ago
Option D sounds like a good plan. It's always safer to move the data to a new disk.
upvoted 0 times
...
...
James
2 months 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 months ago
User 2
upvoted 0 times
...
Maryrose
2 months ago
User 1
upvoted 0 times
...
...
Sheron
2 months 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
2 months 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
3 months 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
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