Free Google Cloud-Digital-Leader Actual Exam Questions - Question 14 Discussion
countries, Customers buy products, add them to carts or check-in stock from different parts of the
world with different timestamps, you need to choose a database that can scale globally without any
hassle and lots of developer support, it should be consistent across regions, can scale horizontally to
support enormous user, automatically replicates, shards and even auto transaction pro-cessing.
Which of the following database do you choose?
B imo, only option with strong global consistency and seamless scaling.
It’s B for sure, only one that does global strong consistency with auto-sharding.
B definitely fits best since it offers strong consistency and global scaling without extra dev hassle. Firestore is good but lacks the same level of transactional support and horizontal scaling worldwide.
Totally agree with B here. Cloud Spanner’s global consistency and built-in sharding make it perfect for worldwide e-commerce with heavy transactions. A doesn’t handle global scale as smoothly. B
Agreed, B fits best since it handles global scaling and consistency automatically.
Option B makes the most sense here. Cloud Spanner is one of the few managed databases that offers true global consistency combined with horizontal scaling. The other options either lack strong consistency across regions or don’t scale automatically at a global level. Firestore is great for flexible data models but isn’t built for massive transactional workloads like this. Cloud Storage is just object storage, so it doesn’t fit the transactional needs at all. Cloud SQL is relational but doesn’t auto-scale globally or handle multi-region transactions as seamlessly as Spanner does.
Maybe B here, Cloud Spanner is built exactly for global scale with strong consistency and auto-sharding. The other options don’t handle multi-region transactions or scaling that smoothly.
It’s B because Cloud Spanner is designed for global consistency and horizontal scaling without complex developer intervention, unlike Cloud SQL or Firestore which don’t handle global transactions as well.
This one’s definitely about global scale and strong consistency, which Cloud Spanner (B) nails with its automatic sharding and multi-region replication. Cloud SQL (A) can’t handle that level of horizontal scaling or global consistency, and Firestore (C) is more about flexible document storage but lacks strong transactional support across regions. Cloud Storage (D) is just for object storage, not databases. So, B makes the most sense here.
B Cloud Spanner is built for exactly this kind of global, consistent, and scalable workload. Cloud SQL can't handle the global scale and automatic sharding as smoothly.
B vs C? Cloud Spanner offers global consistency, Firestore less so.
B, Cloud Spanner fits best for global scale and strong consistency.