Topic 1 Question 57
You are working on a new centralized inventory management system to track items available in 200 stores, which each have 500 GB of data. 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?
Use Oracle Real Application Cluster (RAC) databases on Bare Metal Solution for Oracle.
Use sharded Cloud SQL instances with one or more stores per database instance.
Use a Biglable cluster with autoscaling.
Use Cloud Spanner with a custom autoscaling solution.
ユーザの投票
コメント(7)
- 正解だと思う選択肢: B
Cloud SQL sharding looks like a good option since we need to minimize costs
and we don't need global scaling https://cloud.google.com/community/tutorials/horizontally-scale-mysql-database-backend-with-google-cloud-sql-and-proxysql👍 3chelbsik2022/12/26 D. A SQL database architecture rules out Bigtable. Minimizing costs rules out Oracle RAC. That leaves B and D. B would work with each Cloud SQL instance being dedicated to a few stores which would not impact other Cloud SQL instances already running. The downside is the scaling up/down. To change the vCPU on a Cloud SQL instance requires it to be re-started and that’s disruption. Spanner also doesn’t autoscale by itself, but there’s a tool available for Spanner called Autoscaler which can automate scaling up/down. So on balance, D is the best answer. https://cloud.google.com/spanner/docs/autoscaling-overview
👍 3dynamic_dba2023/03/12- 正解だと思う選択肢: D
CloudSQL max out at 64TB, so unable to told 200 * 500 GB of data. D: choose Spanner
👍 2JayGeotab2023/01/28
シャッフルモード