MENU
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?
Suggested Answer: A
Get Premium Professional Cloud Database Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
31 comments · newest first
SO
Solange
11 months ago
SSDs are faster, but balancing reads might be worth considering.
LE
Leslie
11 months ago
Mixed storage types could work, but SSDs are still better for reads.
BR
Brandon
11 months ago
Wait, why would anyone recommend HDD for this? Seems outdated!
EL
Elvera
11 months ago
I disagree, splitting instances could help with load balancing too.
OT
Otis
12 months ago
SSDs are definitely the way to go for low-latency!
DA
Daniel
12 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.
JO
Josue
1 year 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.
DI
Diane
1 year 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.
ME
Mel
1 year 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.
MA
Madonna
1 year 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.
AN
Antione
1 year 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.
QU
Quinn
1 year 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.
TI
Timmy
1 year ago
This seems pretty straightforward - a read-intensive Bigtable application needs fast storage, so I'd recommend solid-state drives (SSD).
BA
Barrett
1 year 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.
CH
Charlie
1 year 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.
SA
Salome
1 year 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.
TW
Twana
1 year 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.
MI
Mila
1 year 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?
ER
Erasmo
1 year 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.
FI
Filiberto
1 year ago
Splitting the instance might help with load balancing, but SSD is still the best choice for optimal storage.
DA
Dana
1 year ago
I agree, SSD will provide the best performance for read-intensive databases.
AN
Annmarie
1 year ago
SSD is definitely the way to go for low-latency real-time dashboards.
JU
Junita
1 year ago
Hard disk drives (HDD)? Really? That's like trying to race a Ferrari with a donkey-powered cart. Not a chance!
DE
Delisa
1 year 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.
DE
Delisa
1 year 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.
KI
Kindra
1 year ago
Splitting the instance into two could also help with load balancing the reads.
PE
Pearlene
1 year ago
I agree, SSDs provide high performance and low latency which is perfect for real-time dashboards.
NA
Na
1 year ago
SSD is definitely the best choice for low-latency read-intensive databases.
DE
Deane
2 years ago
I'm not sure, maybe we should consider mixed storage types to balance cost and performance.
AM
Amira
2 years ago
I agree with Cordell, SSDs are faster and more suitable for read-intensive applications.
CO
Cordell
2 years ago
I think we should go with solid-state drives (SSD) for low-latency.