Q: 8
You are designing a new gaming application that uses a highly transactional relational database to
store player authentication and inventory data in Google Cloud. You want to launch the game in
multiple regions. What should you do?
Options
Discussion
D since Cloud SQL with regional read replica could work for multi-region, pretty sure it's a trap because it isn't truly global transactional but seems plausible if you don't catch the consistency detail.
For me, A for this one, since Cloud Spanner is the only option that gives true global consistency and handles high transactions. D looks close but only covers regional, so it's a bit of a trick. Anyone see it differently?
Spanner (A) is built for global scale, strong consistency, and lots of transactions at once. Cloud SQL can't handle multi-region writes, so it's not ideal here. Pretty sure about this but let me know if I'm missing something.
Honestly not D, since regional replicas can't guarantee transactions globally. A is made for this use case.
A imo, pretty sure that's what the official guide recommends for multi-region transactional workloads. Saw similar in practice tests too.
Why does Google keep making Cloud SQL sound like it works for global transactions? This one is A all day.
If high transactional consistency is needed across multiple regions, Cloud Spanner (A) is the only real fit. Cloud SQL with replicas can't do cross-region write consistency. I think it's A unless they're asking for something less strict around transactions.
A tbh, since Spanner is designed for global, highly transactional apps. D is regional, so doesn't really fit multi-region needs.
Be respectful. No spam.
