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 Professional Cloud Database Engineer Exam - Topic 4 Question 42 Discussion

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

You are managing a Cloud SQL for PostgreSQL instance in Google Cloud. You have a primary instance in region 1 and a read replica in region 2. After a failure of region 1, you need to make the Cloud SQL instance available again. You want to minimize data loss and follow Google-recommended practices. What should you do?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Glory
4 months ago
I disagree with D, manual failover adds unnecessary steps.
upvoted 0 times
...
Heike
4 months ago
D could work too, but it might take longer to check logs.
upvoted 0 times
...
Stephaine
4 months ago
Surprised that people are considering B. C seems way more efficient!
upvoted 0 times
...
Brittney
4 months ago
I think B is better. Why restore from another zone when you have a replica?
upvoted 0 times
...
Chauncey
5 months ago
Option C is the way to go! Promoting the read replica is key.
upvoted 0 times
...
Quiana
5 months ago
I’m a bit confused about the best approach. Should we rely on the read replica or go for backups? I guess it depends on how much data we can afford to lose.
upvoted 0 times
...
Tu
5 months ago
I practiced a similar question, and I feel like option D could be useful too, especially if the failover happens automatically. But what if it doesn't?
upvoted 0 times
...
Iluminada
5 months ago
I'm not entirely sure, but I remember something about automatic backups being crucial. Maybe option A could be a fallback if the read replica isn't up to date?
upvoted 0 times
...
Joanna
5 months ago
I think option C makes sense because it involves checking the replication status before promoting the read replica. That seems like a good way to minimize data loss.
upvoted 0 times
...
Stephane
5 months ago
Hmm, I'm not sure about this. There are a lot of details to consider, like the automatic failover status and the location of the backups. I think I'll need to carefully read through each option and the question again to make sure I understand everything before answering.
upvoted 0 times
...
Hassie
5 months ago
I'm a bit confused by all the options. I'm not sure if I should be restoring from backups or trying to fail over to the read replica. Maybe I should review the Google documentation on Cloud SQL failover procedures again.
upvoted 0 times
...
Yen
5 months ago
This seems like a tricky question, but I think the key is to follow Google's recommended practices. Option C looks promising since it involves checking the replication status and then failing over to the read replica.
upvoted 0 times
...
Hector
6 months ago
Okay, I think I've got this. Option C is definitely the way to go. Checking the replication status and then failing over to the read replica is the best way to minimize data loss and follow Google's recommendations. I feel pretty confident about this one.
upvoted 0 times
...
Tamie
6 months ago
Developing an open-source package or SDK seems like a lot of work for an exam question. I think I'd focus on the more practical options like using the API Inspector and NETCONF.
upvoted 0 times
...
Eleni
1 year ago
I'd go with C. Promoting the read replica is the way to go, and checking the replication status is a smart move to ensure data integrity.
upvoted 0 times
Georgene
1 year ago
I agree, promoting the read replica after checking the replication status is the recommended practice. C it is.
upvoted 0 times
...
Rozella
1 year ago
Agreed, checking the replication status is crucial to avoid data loss. Let's go with C.
upvoted 0 times
...
Novella
1 year ago
I think C is the best option. Promoting the read replica seems like the safest choice.
upvoted 0 times
...
...
Elli
1 year ago
Haha, I bet option D would be the one the IT guy who just woke up from a nap would recommend. 'Just check the logs, bro, it'll be fine!'
upvoted 0 times
...
Berry
1 year ago
I'm not sure about that. I think we should restore the Cloud SQL instance from the automatic backups in another zone in region 1.
upvoted 0 times
...
Lashawn
1 year ago
I'm not sure about option B. Restoring from a backup in the same region as the failed instance doesn't seem like it would minimize data loss.
upvoted 0 times
Beckie
1 year ago
Exactly, it's important to prioritize data consistency and minimizing data loss in scenarios like this.
upvoted 0 times
...
Gladys
1 year ago
Restoring from a backup in a different region might not have the most up-to-date data compared to the read replica in region 2.
upvoted 0 times
...
Ilene
1 year ago
I agree, option C seems to follow Google-recommended practices for minimizing data loss in this situation.
upvoted 0 times
...
Carissa
1 year ago
Option C sounds like the best choice. Checking the replication status and failing over to the read replica in region 2 seems like the safest bet.
upvoted 0 times
...
...
Nan
2 years ago
I agree with Laura. That seems like the best option to minimize data loss and follow Google-recommended practices.
upvoted 0 times
...
Laura
2 years ago
I think we should check the replication status using pg_catalog.pg_last_wal_receive_lsn and then fail over to region 2 by promoting the read replica instance.
upvoted 0 times
...
Florencia
2 years ago
C seems like the right choice here. The instructions mention following Google-recommended practices, and that's exactly what option C suggests - checking the replication status and failing over to the read replica.
upvoted 0 times
Barrie
1 year ago
Let's go with option C then.
upvoted 0 times
...
Pok
1 year ago
That sounds like the most reliable choice.
upvoted 0 times
...
Holley
1 year ago
I agree, C involves checking replication status and failing over to the read replica.
upvoted 0 times
...
Golda
2 years ago
I think C is the best option here.
upvoted 0 times
...
...

Save Cancel