MENU
You are working on a new centralized inventory management system to track items available in 200 stores, which each have 500 GB of dat
a. You are planning a gradual rollout of the system to a few stores each week. You need to design an SQL database architecture that minimizes costs and user disruption during each regional rollout and can scale up or down on nights and holidays. What should you do?
Suggested Answer: C
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
39 comments · newest first
LA
Lai
11 months ago
Not sure about Cloud Spanner, it might complicate things too much.
CO
Cory
11 months ago
Bigtable with autoscaling sounds interesting, but is it reliable enough?
GE
Georgiann
11 months ago
Wait, are we really considering Oracle RAC? Seems overkill for this.
LI
Linwood
11 months ago
Totally agree, it scales well with multiple stores!
RI
Rikki
12 months ago
I think sharded Cloud SQL is the way to go for cost efficiency.
CH
Chau
12 months ago
I recall that Oracle RAC can be complex and might not be the best for gradual rollouts. I wonder if that would cause more disruption than necessary.
CL
Clorinda
1 year ago
I practiced a similar question about database architecture, and I feel like Cloud Spanner might be the best choice for scalability, but I’m unsure about the custom autoscaling part.
TY
Ty
1 year ago
I think using sharded Cloud SQL instances could help with scaling, but I’m not entirely confident about how that would work with 200 stores.
IZ
Izetta
1 year ago
I remember we discussed the importance of minimizing costs during rollouts, but I'm not sure which option would be the most cost-effective.
LO
Lorenza
1 year ago
I'm a bit lost on this one. There are a lot of factors to consider, and I'm not sure I fully understand the implications of each solution. I'll need to review the material again before attempting this.
AL
Alana
1 year ago
This is a great question that really tests our understanding of database architectures. I'm confident I can work through the tradeoffs and select the best option.
AM
Ammie
1 year ago
Okay, I think I have a strategy here. The key is finding a database solution that can scale up and down easily to handle the varying load across days and holidays. I'm leaning towards option B or D.
AS
Ashton
1 year ago
Hmm, I'm a bit unsure about this one. The details around the 200 stores and 500 GB of data per store seem important, but I'm not sure which option best addresses those specifics.
JA
Janey
1 year ago
This looks like a tricky database design question. I'll need to carefully consider the requirements around cost, scalability, and minimizing user disruption.
HE
Herman
1 year ago
You know, if this was the Dark Ages, they'd probably just use a quill and parchment for the inventory. No databases, no problems!
NU
Nu
1 year ago
D) Cloud Spanner with a custom autoscaling solution could work well too.
JO
Jospeh
1 year ago
C) Use a Bigtable cluster with autoscaling.
CL
Clay
1 year ago
B) That sounds like a solid option for a gradual rollout.
AL
Alba
1 year ago
A) Use Oracle Real Application Cluster (RAC) databases on Bare Metal Solution for Oracle.
HE
Herman
1 year ago
Sharded Cloud SQL is definitely the way to go. Easy to scale up or down, and you can even automate it for nights and holidays. Wouldn't want the store managers calling me at 3 AM because the system crashed, you know?
CA
Carman
1 year ago
True, that could be a good option for minimizing costs and user disruption during regional rollouts.
RE
Reena
1 year ago
I think using Cloud Spanner with a custom autoscaling solution could also work well.
GE
Georgiana
1 year ago
C) Agreed, it's important to have a system that can scale up or down easily without causing disruptions.
PA
Pansy
1 year ago
Agreed, it's easy to scale up or down and automate for nights and holidays.
FE
Felicidad
1 year ago
Sharded Cloud SQL is definitely the way to go.
LE
Leslee
1 year ago
B) Definitely, sharded Cloud SQL is the best option for this scenario.
RA
Ramonita
1 year ago
A) Use sharded Cloud SQL instances with one or more stores per database instance.
KA
Karl
2 years ago
Cloud Spanner, huh? That could work, but I bet it'd cost an arm and a leg. I'd stick with the good old sharded Cloud SQL - it's tried and true.
GA
Gayla
2 years ago
Bigdata solution like Bigtable? Nah, this is a fairly simple inventory management system, no need for that kind of heavy-duty stuff.
CO
Corinne
1 year ago
B) I agree, that seems like a more cost-effective and scalable solution for this project.
SA
Sanda
1 year ago
A) Use sharded Cloud SQL instances with one or more stores per database instance.
LA
Lashunda
2 years ago
That's a valid point, Martha. We should consider the cost implications as well before making a decision.
LA
Lajuana
2 years ago
Hmm, Oracle RAC on Bare Metal seems like overkill for this scenario. I'd go with the sharded Cloud SQL instances to keep things scalable and cost-effective.
OR
Orville
1 year ago
Cloud Spanner with a custom autoscaling solution might be worth considering as well.
FE
Felix
1 year ago
I think using a Bigtable cluster with autoscaling could also be a good option.
BR
Brent
1 year ago
Sharded Cloud SQL instances would definitely be more cost-effective and scalable.
SA
Santos
1 year ago
I agree, Oracle RAC on Bare Metal does seem like overkill.
MA
Martha
2 years ago
I disagree, I believe option B, using sharded Cloud SQL instances, would be more cost-effective and efficient for our needs.
LA
Lashunda
2 years ago
I think we should go with option D, Cloud Spanner with a custom autoscaling solution. It will allow us to scale up or down easily.