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 9 Question 48 Discussion

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

You are designing for a write-heavy application. During testing, you discover that the write workloads are performant in a regional Cloud Spanner instance but slow down by an order of magnitude in a multi-regional instance. You want to make the write workloads faster in a multi-regional instance. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

https://cloud.google.com/spanner/docs/instance-configurations#multi-region-best-practices Best practices For optimal performance, follow these best practices: Design a schema that prevents hotspots and other performance issues. For optimal write latency, place compute resources for write-heavy workloads within or close to the default leader region. For optimal read performance outside of the default leader region, use staleness of at least 15 seconds. To avoid single-region dependency for your workloads, place critical compute resources in at least two regions. A good option is to place them next to the two different read-write regions so that any single region outage will not impact all of your application. Provision enough compute capacity to keep high priority total CPU utilization under 45% in each region.


Contribute your Thoughts:

Gladys
1 months ago
I think we should also consider placing the bulk of the read and write workloads closer to the default leader region to optimize performance.
upvoted 0 times
...
Josefa
2 months ago
Option A sounds promising. Placing the workloads closer to the default leader region could reduce latency and improve write performance.
upvoted 0 times
...
Gary
2 months ago
I agree with Toi. Adding more read-write replicas can help distribute the workload and improve performance.
upvoted 0 times
...
Toi
2 months ago
I think we should add more read-write replicas to make the write workloads faster.
upvoted 0 times
...
Louis
2 months ago
Haha, keep the total CPU utilization under 45%? That's like asking a cheetah to run at the speed of a sloth. Good one, Option D!
upvoted 0 times
Loren
26 days ago
Yeah, keeping the CPU under 45% seems like a tough task. Option D might be the best bet.
upvoted 0 times
...
Stephen
28 days ago
I think adding more read-write replicas could also help distribute the workload.
upvoted 0 times
...
Maryann
1 months ago
Option D is definitely a good one. We need to keep the CPU utilization in check.
upvoted 0 times
...
Cammy
1 months ago
Yeah, placing the bulk of the read and write workloads closer to the default leader region could also be a good solution.
upvoted 0 times
...
Georgiana
1 months ago
Maybe adding more read-write replicas would help speed up the write workloads.
upvoted 0 times
...
Margurite
2 months ago
I agree, keeping CPU utilization under 45% seems impossible.
upvoted 0 times
...
Lisbeth
2 months ago
Option D is definitely not realistic in a write-heavy application.
upvoted 0 times
...
...
Malissa
2 months ago
I'm not sure about that. Wouldn't increasing the staleness to 15 seconds (Option B) be a simpler solution to improve write performance?
upvoted 0 times
...
Elli
2 months ago
Option C seems like the way to go. Adding more read-write replicas should help distribute the workload and improve overall performance in a multi-regional instance.
upvoted 0 times
Junita
2 months ago
D) Keep the total CPU utilization under 45% in each region.
upvoted 0 times
...
Dortha
2 months ago
C) Adding more read-write replicas can definitely help improve performance in a multi-regional instance.
upvoted 0 times
...
Bok
2 months ago
A) Place the bulk of the read and write workloads closer to the default leader region.
upvoted 0 times
...
Lezlie
2 months ago
C) Add more read-write replicas.
upvoted 0 times
...
...

Save Cancel