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 Database Engineer Exam - Topic 9 Question 48 Discussion

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?
A) Place the bulk of the read and write workloads closer to the default leader region.
B) Use staleness of at least 15 seconds.
C) Add more read-write replicas.
D) Keep the total CPU utilization under 45% in each region.

Google Professional Cloud Database Engineer Exam - 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.


by Launa at Nov 14, 2024, 01:04 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Dallas
6 months ago
Keeping CPU under 45% sounds too conservative.
upvoted 0 times
...
Lina
6 months ago
More replicas could help, but is it worth the cost?
upvoted 0 times
...
Garry
7 months ago
Wait, does staleness really help that much?
upvoted 0 times
...
Chantell
7 months ago
Totally agree, proximity matters!
upvoted 0 times
...
Ronnie
7 months ago
A seems like the best option to reduce latency.
upvoted 0 times
...
Hassie
7 months ago
Keeping CPU utilization under 45% seems like a good practice, but I doubt it would directly address the write performance issue we're facing.
upvoted 0 times
...
Rashida
8 months ago
Adding more read-write replicas sounds familiar, but I’m not clear on how much that would actually speed things up in a multi-regional setup.
upvoted 0 times
...
Hassie
8 months ago
I think using staleness might be a good idea, especially since it can reduce the load on the system. I saw a similar question about read consistency in our practice tests.
upvoted 0 times
...
Ty
8 months ago
I remember something about placing workloads closer to the leader region could help with performance, but I'm not entirely sure if that's the best option here.
upvoted 0 times
...
Shawnna
8 months ago
Ah, I see what they're getting at. If the write workloads are slow in the multi-regional instance, then we need to find a way to make them faster. Using staleness of at least 15 seconds could be a good way to optimize performance, but I'd want to understand the implications of that approach.
upvoted 0 times
...
Cordie
8 months ago
I'm a bit confused on this one. The options seem to be focused on different strategies, but I'm not sure which one would be the most effective. Maybe I should re-read the question and think about the tradeoffs of each approach.
upvoted 0 times
...
Deeanna
8 months ago
Okay, let me think this through. The question says the write workloads are slow in the multi-regional instance, so I'm guessing we need to find a way to improve that. Placing the workloads closer to the default leader region could be a good approach.
upvoted 0 times
...
Willard
8 months ago
Hmm, this is an interesting one. I think the key is to figure out how to optimize the write workloads in the multi-regional instance. Maybe adding more read-write replicas could help distribute the load?
upvoted 0 times
...
Gladys
2 years 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 years 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 years ago
I agree with Toi. Adding more read-write replicas can help distribute the workload and improve performance.
upvoted 0 times
...
Toi
2 years ago
I think we should add more read-write replicas to make the write workloads faster.
upvoted 0 times
...
Louis
2 years 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
1 year ago
Yeah, keeping the CPU under 45% seems like a tough task. Option D might be the best bet.
upvoted 0 times
...
Stephen
1 year ago
I think adding more read-write replicas could also help distribute the workload.
upvoted 0 times
...
Maryann
1 year ago
Option D is definitely a good one. We need to keep the CPU utilization in check.
upvoted 0 times
...
Cammy
1 year 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
2 years ago
Maybe adding more read-write replicas would help speed up the write workloads.
upvoted 0 times
...
Margurite
2 years ago
I agree, keeping CPU utilization under 45% seems impossible.
upvoted 0 times
...
Lisbeth
2 years ago
Option D is definitely not realistic in a write-heavy application.
upvoted 0 times
...
...
Malissa
2 years 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 years 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 years ago
D) Keep the total CPU utilization under 45% in each region.
upvoted 0 times
...
Dortha
2 years ago
C) Adding more read-write replicas can definitely help improve performance in a multi-regional instance.
upvoted 0 times
...
Bok
2 years ago
A) Place the bulk of the read and write workloads closer to the default leader region.
upvoted 0 times
...
Lezlie
2 years ago
C) Add more read-write replicas.
upvoted 0 times
...
...

Save Cancel