Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Database Engineer Topic 2 Question 47 Discussion

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

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?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Herman
1 months 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!
upvoted 0 times
...
Herman
2 months 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?
upvoted 0 times
Carman
5 days ago
True, that could be a good option for minimizing costs and user disruption during regional rollouts.
upvoted 0 times
...
Reena
6 days ago
I think using Cloud Spanner with a custom autoscaling solution could also work well.
upvoted 0 times
...
Georgiana
14 days ago
C) Agreed, it's important to have a system that can scale up or down easily without causing disruptions.
upvoted 0 times
...
Pansy
16 days ago
Agreed, it's easy to scale up or down and automate for nights and holidays.
upvoted 0 times
...
Felicidad
18 days ago
Sharded Cloud SQL is definitely the way to go.
upvoted 0 times
...
Leslee
1 months ago
B) Definitely, sharded Cloud SQL is the best option for this scenario.
upvoted 0 times
...
Ramonita
1 months ago
A) Use sharded Cloud SQL instances with one or more stores per database instance.
upvoted 0 times
...
...
Karl
2 months 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.
upvoted 0 times
...
Gayla
2 months ago
Bigdata solution like Bigtable? Nah, this is a fairly simple inventory management system, no need for that kind of heavy-duty stuff.
upvoted 0 times
Corinne
1 months ago
B) I agree, that seems like a more cost-effective and scalable solution for this project.
upvoted 0 times
...
Sanda
2 months ago
A) Use sharded Cloud SQL instances with one or more stores per database instance.
upvoted 0 times
...
...
Lashunda
2 months ago
That's a valid point, Martha. We should consider the cost implications as well before making a decision.
upvoted 0 times
...
Lajuana
2 months 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.
upvoted 0 times
Orville
30 days ago
Cloud Spanner with a custom autoscaling solution might be worth considering as well.
upvoted 0 times
...
Felix
1 months ago
I think using a Bigtable cluster with autoscaling could also be a good option.
upvoted 0 times
...
Brent
1 months ago
Sharded Cloud SQL instances would definitely be more cost-effective and scalable.
upvoted 0 times
...
Santos
1 months ago
I agree, Oracle RAC on Bare Metal does seem like overkill.
upvoted 0 times
...
...
Martha
2 months ago
I disagree, I believe option B, using sharded Cloud SQL instances, would be more cost-effective and efficient for our needs.
upvoted 0 times
...
Lashunda
2 months 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.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77