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 Associate Cloud Engineer Exam - Topic 5 Question 113 Discussion

Actual exam question for Google's Associate Cloud Engineer exam
Question #: 113
Topic #: 5
[All Associate Cloud Engineer Questions]

Your customer has implemented a solution that uses Cloud Spanner and notices some read latency-related performance issues on one table. This table is accessed only by their users using a primary key. The table schema is shown below.

You want to resolve the issue. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

As mentioned in Schema and data model, you should be careful when choosing a primary key to not accidentally create hotspots in your database. One cause of hotspots is having a column whose value monotonically increases as the first key part, because this results in all inserts occurring at the end of your key space. This pattern is undesirable because Cloud Spanner divides data among servers by key ranges, which means all your inserts will be directed at a single server that will end up doing all the work. https://cloud.google.com/spanner/docs/schema-design#primary-key-prevent-hotspots


by Blair at Nov 23, 2025, 06:23 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Mona
1 day ago
I’m leaning towards Option A. It seems more straightforward.
upvoted 0 times
...
Yan
7 days ago
Indexing is key! It can really speed up reads.
upvoted 0 times
...
Evan
12 days ago
I feel like Option B might help. It focuses on indexing.
upvoted 0 times
...
Jerry
17 days ago
Wait, are we really seeing latency issues with Cloud Spanner? That's unexpected!
upvoted 0 times
...
Tamera
22 days ago
Totally agree, primary key optimization is key here!
upvoted 0 times
...
Barrie
27 days ago
Not sure if that's the only issue, could be network-related too.
upvoted 0 times
...
Micaela
2 months ago
I'm leaning towards Option B, but I'd want to make sure it doesn't introduce any new issues with the data.
upvoted 0 times
...
Aleisha
2 months ago
Haha, Option D is like trying to put a band-aid on a broken leg. Let's stick to the more practical solutions here.
upvoted 0 times
...
Helaine
2 months ago
Option A seems like the most straightforward solution, but I'm curious to hear if there are any potential downsides.
upvoted 0 times
...
Vicki
2 months ago
Option D is an interesting idea, but I'm not convinced it will fully address the performance issues.
upvoted 0 times
...
Denise
2 months ago
Option B seems like a good solution, but I'd like to hear more about the potential drawbacks.
upvoted 0 times
...
Salena
2 months ago
Option C looks promising, but I'm not sure if it's the best choice.
upvoted 0 times
...
Sheridan
3 months ago
I think one of the options might involve adjusting the schema or adding an index, but I can't remember the details.
upvoted 0 times
...
Alline
3 months ago
I feel like I should consider the primary key access pattern, but I can't recall if that means I should focus on sharding or something else.
upvoted 0 times
...
Eloisa
3 months ago
This reminds me of a practice question where we had to choose between indexing strategies. I think that might be relevant here too.
upvoted 0 times
...
Esteban
3 months ago
I remember reading about optimizing read performance in Cloud Spanner, but I'm not sure which option specifically addresses latency issues.
upvoted 0 times
...
Verda
3 months ago
This is a great opportunity to showcase my understanding of Cloud Spanner. I'm confident I can analyze the situation and select the optimal solution.
upvoted 0 times
...
Roy
3 months ago
I'm a bit confused by the options here. I'll need to do some research on Cloud Spanner best practices to make sure I choose the right approach.
upvoted 0 times
...
Virgina
4 months ago
I think optimizing the primary key could help with latency.
upvoted 0 times
...
Craig
4 months ago
Cloud Spanner is designed for high availability and scalability.
upvoted 0 times
...
Colby
4 months ago
Okay, let's think this through step-by-step. The key is to understand the root cause of the performance problem and select the most appropriate solution.
upvoted 0 times
...
Kathryn
4 months ago
This is a tough one, but I think I'd go with Option C. It seems like the most comprehensive solution.
upvoted 0 times
...
Herschel
4 months ago
I think this question is tricky. Read latency can be tough to diagnose.
upvoted 0 times
...
Elmira
5 months ago
Hmm, the table schema seems straightforward, but the read latency issue is concerning. I'll need to carefully review the options and consider the trade-offs.
upvoted 0 times
...
Laurena
5 months ago
This looks like a classic Cloud Spanner performance issue. I'd start by analyzing the table schema and usage patterns to identify potential bottlenecks.
upvoted 0 times
...

Save Cancel