New Year Sale 2026! 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 6 Question 30 Discussion

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

Your company uses Bigtable for a user-facing application that displays a low-latency real-time dashboard. You need to recommend the optimal storage type for this read-intensive database. What should you do?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Solange
3 months ago
SSDs are faster, but balancing reads might be worth considering.
upvoted 0 times
...
Leslie
3 months ago
Mixed storage types could work, but SSDs are still better for reads.
upvoted 0 times
...
Brandon
4 months ago
Wait, why would anyone recommend HDD for this? Seems outdated!
upvoted 0 times
...
Elvera
4 months ago
I disagree, splitting instances could help with load balancing too.
upvoted 0 times
...
Otis
4 months ago
SSDs are definitely the way to go for low-latency!
upvoted 0 times
...
Daniel
4 months ago
Mixed storage types could be useful in some scenarios, but for a read-intensive database, I think A is probably the most optimal choice.
upvoted 0 times
...
Josue
4 months ago
HDDs are usually slower, so I doubt C is the best recommendation for a real-time dashboard. I feel like it’s not the right fit.
upvoted 0 times
...
Diane
5 months ago
I'm not entirely sure, but I think splitting the instance could help with load balancing. It seems like B could be a valid option too.
upvoted 0 times
...
Mel
5 months ago
I remember reading that SSDs are generally better for read-intensive applications because of their speed. I think A might be the right choice.
upvoted 0 times
...
Madonna
5 months ago
For a real-time dashboard, I think the key is minimizing latency, so SSD is probably the way to go. But I'll make sure to consider the other options too before deciding.
upvoted 0 times
...
Antione
5 months ago
I'm a bit confused here. Is there any advantage to using hard disk drives (HDD) or a mixed storage type? I'll need to think through the tradeoffs more carefully.
upvoted 0 times
...
Quinn
5 months ago
Hmm, I'm not sure if that's the best approach. Splitting the Bigtable instance might help load balance the reads, so I'll consider that option as well.
upvoted 0 times
...
Timmy
5 months ago
This seems pretty straightforward - a read-intensive Bigtable application needs fast storage, so I'd recommend solid-state drives (SSD).
upvoted 0 times
...
Barrett
5 months ago
This seems like a pretty simple question. The solution provided is a link to the Okta support website, so I'm confident that the answer is yes, this is where an Okta Administrator should submit a case.
upvoted 0 times
...
Charlie
5 months ago
I'm a bit confused by this question. I'm not entirely sure what the current account of a balance of payments includes. I'll have to review my notes and try to eliminate the options that don't seem to fit.
upvoted 0 times
...
Salome
5 months ago
This seems like a straightforward question about distribution system effectiveness. I'll focus on the criteria that directly measure how well the system is meeting customer needs.
upvoted 0 times
...
Twana
5 months ago
I've learned about Cisco ONE software in my networking classes, so I'm confident I can identify the feature that is not part of it.
upvoted 0 times
...
Mila
10 months ago
I heard Bigtable was so fast, it could read your mind before you even thought of the question. Maybe we should just recommend a crystal ball instead?
upvoted 0 times
...
Erasmo
10 months ago
Mixed storage types? That's like trying to serve sushi and steak on the same plate - it just doesn't work. Stick with the SSD, it's the clear winner here.
upvoted 0 times
Filiberto
8 months ago
Splitting the instance might help with load balancing, but SSD is still the best choice for optimal storage.
upvoted 0 times
...
Dana
8 months ago
I agree, SSD will provide the best performance for read-intensive databases.
upvoted 0 times
...
Annmarie
8 months ago
SSD is definitely the way to go for low-latency real-time dashboards.
upvoted 0 times
...
...
Junita
10 months ago
Hard disk drives (HDD)? Really? That's like trying to race a Ferrari with a donkey-powered cart. Not a chance!
upvoted 0 times
...
Delisa
10 months ago
Splitting the Bigtable instance into two instances might work, but that's a lot of additional overhead and complexity. I'd rather keep it simple and go with the SSD option.
upvoted 0 times
...
Delisa
10 months ago
Solid-state drives (SSD) are definitely the way to go for a read-intensive database. The low latency and high performance of SSDs make them the optimal choice here.
upvoted 0 times
Kindra
9 months ago
Splitting the instance into two could also help with load balancing the reads.
upvoted 0 times
...
Pearlene
9 months ago
I agree, SSDs provide high performance and low latency which is perfect for real-time dashboards.
upvoted 0 times
...
Na
10 months ago
SSD is definitely the best choice for low-latency read-intensive databases.
upvoted 0 times
...
...
Deane
11 months ago
I'm not sure, maybe we should consider mixed storage types to balance cost and performance.
upvoted 0 times
...
Amira
11 months ago
I agree with Cordell, SSDs are faster and more suitable for read-intensive applications.
upvoted 0 times
...
Cordell
11 months ago
I think we should go with solid-state drives (SSD) for low-latency.
upvoted 0 times
...

Save Cancel