MENU
You work for a large retail and ecommerce company that is starting to extend their business globally. Your company plans to migrate to Google Cloud. You want to use platforms that will scale easily, handle transactions with the least amount of latency, and provide a reliable customer experience. You need a storage layer for sales transactions and current inventory levels. You want to retain the same relational schema that your existing platform uses. What should you do?
Suggested Answer: B
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
27 comments · newest first
IR
Ira
10 months ago
Totally agree, low latency is key for customer experience!
HE
Helaine
10 months ago
Wait, can Spanner really handle all that without issues?
SH
Shayne
11 months ago
Definitely go with Spanner, it’s built for this kind of workload.
FA
Farrah
11 months ago
I think Firestore might not handle relational schemas well.
SE
Serita
11 months ago
Cloud Spanner is great for scaling and transactions!
EL
Elke
11 months ago
I was leaning towards Memorystore for caching, but it doesn't really handle transactions like we need. I guess we need a proper database solution instead.
JO
Jordan
11 months ago
I think we practiced a similar question where we had to choose between Spanner and Bigtable. If we want low latency and scalability, Spanner seems to fit better.
RE
Refugia
12 months ago
I'm not entirely sure, but I feel like Firestore is more suited for NoSQL. We need to stick with a relational schema, right?
SH
Shaunna
12 months ago
I remember we discussed the importance of using a relational database for transactions, so I think Cloud Spanner might be the right choice here.
SH
Sherrell
1 year ago
I'm a bit confused by the options here. Memorystore seems like it might not be the best fit since we need to store actual transaction and inventory data, not just cache it. I'll need to review the differences between the database options more carefully.
JA
Jaime
1 year ago
Okay, let's think this through. We need a managed service that can scale easily, handle transactions, and provide low latency. I'm leaning towards option B with Cloud Spanner since it's a fully managed relational database service.
JO
Joesph
1 year ago
Hmm, I'm a bit unsure about this one. The requirement to retain the existing relational schema makes me think Firestore might not be the best fit. I'll need to research Cloud Spanner and Bigtable a bit more to decide.
JE
Jerrod
1 year ago
This question seems straightforward - we need a scalable, low-latency storage solution that can handle transactions and inventory. I think option B with Cloud Spanner is the way to go.
ER
Erin
1 year ago
I prefer option A, Firestore seems like a reliable choice for our storage needs.
ST
Steffanie
1 year ago
I'm not sure, I think option D could also work well for us.
WE
Wenona
1 year ago
I agree with Aretha, Cloud Spanner seems like the best choice for our needs.
AR
Aretha
1 year ago
I think we should go with option B.
GE
Georgiann
1 year ago
Bigtable might work, but it's more for big data use cases. We need a relational database that can handle transactions, not a NoSQL solution.
HE
Henriette
1 year ago
Haha, Memorystore for a retail company's sales transactions? That's like trying to store the entire inventory in your brain!
EL
Elinore
1 year ago
I agree, Cloud Spanner sounds like the best choice. It's designed for global-scale relational databases, and the multi-region setup will ensure high availability.
RA
Rasheeda
1 year ago
I agree, Cloud Spanner sounds like the best choice. It's designed for global-scale relational databases, and the multi-region setup will ensure high availability.
VA
Vallie
1 year ago
B) Deploy Cloud Spanner using a multi-region instance, and place your compute resources close to the default leader region.
KI
Kirby
1 year ago
A) Store your data in Firestore in a multi-region location, and place your compute resources in one of the constituent regions.
TI
Tien
1 year ago
Option B seems like the way to go. Cloud Spanner's multi-region instances and low-latency transactions are perfect for this use case.
RE
Refugia
1 year ago
Definitely, using Cloud Spanner with a multi-region instance will help ensure scalability and reliability for our global expansion.
GE
Georgene
1 year ago
I agree, Cloud Spanner would be a great choice for maintaining the relational schema and handling transactions with low latency.
MA
Macy
1 year ago
Option B seems like the way to go. Cloud Spanner's multi-region instances and low-latency transactions are perfect for this use case.