Google Professional Cloud Database Engineer Exam - Topic 3 Question 56 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam

Question #: 56
Topic #: 3

[All Professional Cloud Database Engineer Questions]

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?

AStore your data in Firestore in a multi-region location, and place your compute resources in one of the constituent regions.

BDeploy Cloud Spanner using a multi-region instance, and place your compute resources close to the default leader region.

CBuild an in-memory cache in Memorystore, and deploy to the specific geographic regions where your application resides.

DDeploy a Bigtable instance with a cluster in one region and a replica cluster in another geographic region.

Show Suggested Answer

Suggested Answer: B

by Kenny at Apr 30, 2025, 06:31 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ira

2 months ago

Totally agree, low latency is key for customer experience!

upvoted 0 times

...

Helaine

2 months ago

Wait, can Spanner really handle all that without issues?

upvoted 0 times

...

Shayne

3 months ago

Definitely go with Spanner, it’s built for this kind of workload.

upvoted 0 times

...

Farrah

3 months ago

I think Firestore might not handle relational schemas well.

upvoted 0 times

...

Serita

3 months ago

Cloud Spanner is great for scaling and transactions!

upvoted 0 times

...

Elke

3 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.

upvoted 0 times

...

Jordan

4 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.

upvoted 0 times

...

Refugia

4 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?

upvoted 0 times

...

Shaunna

4 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.

upvoted 0 times

...

Sherrell

4 months 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.

upvoted 0 times

...

Jaime

4 months 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.

upvoted 0 times

...

Joesph

5 months 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.

upvoted 0 times

...

Jerrod

5 months 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.

upvoted 0 times

...

Erin

8 months ago

I prefer option A, Firestore seems like a reliable choice for our storage needs.

upvoted 0 times

...

Steffanie

8 months ago

I'm not sure, I think option D could also work well for us.

upvoted 0 times

...

Wenona

8 months ago

I agree with Aretha, Cloud Spanner seems like the best choice for our needs.

upvoted 0 times

...

Aretha

8 months ago

I think we should go with option B.

upvoted 0 times

...

Georgiann

9 months 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.

upvoted 0 times

...

Henriette

10 months ago

Haha, Memorystore for a retail company's sales transactions? That's like trying to store the entire inventory in your brain!

upvoted 0 times

...

Elinore

10 months 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.

upvoted 0 times

Rasheeda

8 months 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.

upvoted 0 times

...

Vallie

8 months ago

B) Deploy Cloud Spanner using a multi-region instance, and place your compute resources close to the default leader region.

upvoted 0 times

...

Kirby

9 months ago

A) Store your data in Firestore in a multi-region location, and place your compute resources in one of the constituent regions.

upvoted 0 times

...

Tien

10 months 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.

upvoted 0 times

Refugia

9 months ago

Definitely, using Cloud Spanner with a multi-region instance will help ensure scalability and reliability for our global expansion.

upvoted 0 times

...

Georgene

9 months ago

I agree, Cloud Spanner would be a great choice for maintaining the relational schema and handling transactions with low latency.

upvoted 0 times

...

Macy

9 months 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.

upvoted 0 times

...