Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
Location Chicago IL, USA

Exam Professional Cloud Architect topic 1 question 163 discussion

Actual exam question from Google's Professional Cloud Architect
Question #: 163
Topic #: 1
[All Professional Cloud Architect Questions]

Your company runs several databases on a single MySQL instance. They need to take backups of a specific database at regular intervals. The backup activity needs to complete as quickly as possible and cannot be allowed to impact disk performance.
How should you configure the storage?

  • A. Configure a cron job to use the gcloud tool to take regular backups using persistent disk snapshots.
  • B. Mount a Local SSD volume as the backup location. After the backup is complete, use gsutil to move the backup to Google Cloud Storage.
  • C. Use gcsfise to mount a Google Cloud Storage bucket as a volume directly on the instance and write backups to the mounted location using mysqldump.
  • D. Mount additional persistent disk volumes onto each virtual machine (VM) instance in a RAID10 array and use LVM to create snapshots to send to Cloud Storage
Show Suggested Answer Hide Answer

Suggested Answer: B

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
hannibal1969
Highly Voted 2 years ago
I think it's B. If you use a tool like GCFUSE it will write immediatly to GCS which is a cost benefit because you don't need intermediate storage. In this case however "Quickly as possible" key for understanding. GCFUSE will write to GCS which is much slower than writing directly to an added SSD. During the write to GCS it would also execute reads for a longer period on the production database. Therefor writing to the extra SSD would be my recommended solution. Offloading from the SSD to GCS would not impact the running database because the data is already separated.
upvoted 36 times
kvenkatasudhakar
6 days, 20 hours ago
We cannot attach and mount a local SSD to a running instance. I think it's C (GCFUSE)
upvoted 1 times
...
heelhook_ambassador
1 week, 4 days ago
Thanks!
upvoted 1 times
...
raf2121
3 months, 1 week ago
Point for Discussion Can local SSD be mounted in a running instance.
upvoted 2 times
JasonL_GCP
1 month, 3 weeks ago
Good point, Because Local SSDs are located on the physical machine where your virtual machine instance is running, they can be created only during the instance creation process
upvoted 1 times
...
pr2web
2 months, 4 weeks ago
In addition the mysqldump command can be run with local ssd as destination, and NOT impacting existing DB performance by using the --databases dbname --single-transaction flag. That said, this boils down to which is quicker to complete, a local SSD dump and gsutil to gs://bucket OR gcsfuse the bucket directly on the VM, and mysqldump with the --single-transaction command
upvoted 1 times
...
pr2web
2 months, 4 weeks ago
Yes they can. That's precisely why it makes Local SSD a good scratch / temp storage with very high IOPS. https://cloud.google.com/compute/docs/disks/local-ssd#formatandmount
upvoted 1 times
...
...
...
Rathish
Highly Voted 1 year, 9 months ago
Ans: B Persistent Disk snapshot not required: "They need to take backups of a specific database at regular intervals." "The backup activity needs to complete as quickly as possible and cannot be allowed to impact disk performance." This can be achieved by using both Local SSD & GCS Fuse (mounting GCS as directory), but as the question stats needs to complete as quickly as possible. General Rule: Any addition of components introduce a latency. I could not get write throughput of GCS & Local SSD, even if we consider both provides same throughput, streaming data through network to GCS Bucket introduce latency. Attached Local SSD has advantage in this case, since there is no network involved. From Local SSD to GCS bucket - copy job does not impact the mysql data disk.
upvoted 12 times
...
joe2211
Most Recent 1 week, 3 days ago
Selected Answer: B
vote B
upvoted 2 times
...
BSING246
1 month, 3 weeks ago
B is correct option. Local SSD is fastest option for making the backup of running instance.
upvoted 1 times
...
rottzy
1 month, 3 weeks ago
local SSD - Bad choice for backup Local SSDs are suitable only for temporary storage such as caches, processing space, or low value data. To store data that is not temporary or ephemeral in nature, use one of our durable storage options. https://cloud.google.com/compute/docs/disks/local-ssd gcfuse wouldn't cut it either - latency why not A, if regular backup is required here? on a timely schedule
upvoted 1 times
...
sudarchary
3 months ago
"C" is correct. . Local SSD cannot be mounted on running VMs
upvoted 2 times
pr2web
2 months, 4 weeks ago
You're incorrect. Local SSDs can be mounted on a running VM just fine. Just be aware of the limitations if you shutdown/stop the VM then the ephemeral Local SSD will lose all data. Yes they can. That's precisely why it makes Local SSD a good scratch / temp storage with very high IOPS. https://cloud.google.com/compute/docs/disks/local-ssd#formatandmount Answer B is indeed correct.
upvoted 2 times
...
...
hdlife
4 months, 1 week ago
Got most of the Qs from here, good help. Got Qs on MountKirk Game and HRL case studies around 12-13 Qs
upvoted 1 times
...
purushi
4 months, 2 weeks ago
B is ok, but what about backup at regular intervals. Are we missing cron job here?
upvoted 3 times
AWSPro24
3 weeks, 6 days ago
I considered this but why snapshot the whole disk when you just need one DB from one instance.
upvoted 1 times
...
...
purushi
4 months, 2 weeks ago
B is ok, but what about backup at regular intervals. Are we missing cron job here?
upvoted 1 times
...
bala786
5 months ago
Option B is correct
upvoted 1 times
...
VishalB
5 months, 3 weeks ago
Correct Ans B - https://cloud.google.com/compute/docs/instances/sql-server/best-practices#backing_up When taking regular database backups, be careful not to consume too many persistent disk IOPS. Use the local SSD to stage your backups and then push them to a Cloud Storage bucket.
upvoted 3 times
...
victory108
6 months, 3 weeks ago
B. Mount a Local SSD volume as the backup location. After the backup is complete, use gsutil to move the backup to Google Cloud Storage.
upvoted 2 times
...
un
7 months ago
B is correct
upvoted 2 times
...
jchacana
7 months, 1 week ago
My reason to say C is that in order to perform a "specific database backup" you need to go with a mysqldump command. Other alternatives are all or nothing
upvoted 3 times
...
kakarooky
7 months, 2 weeks ago
B is not. What if VM is restarted after backup done before uploading to Cloud Storage?
upvoted 1 times
pr2web
2 months, 4 weeks ago
The important things is to understand the limitations of a Local SSD. If its a one time thing then yes it'll be the best option. A repeatable option requires something like Filestore instead of Local SSD, to persist through Stop/Starts. However, a local SSD will persist through a reboot. https://cloud.google.com/compute/docs/disks/local-ssd#formatandmount
upvoted 1 times
...
...
ansh0692
7 months, 3 weeks ago
for B, I understand the "quick" part but what about backup of a specific database and in regular interval of times, (mounting local SSD seems manual and it's whole MySQL instance instead of just 1 database, overkill of storage) Because of these reasons I think it's C
upvoted 3 times
...
mrhege
8 months ago
It's B. Mysql has to do the backup to capture those changes too that might not have been flushed to disk yet, so A and D is ruled out. GCSFUSE is sloooow, so that leaves us with option B.
upvoted 1 times
...
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...