Google Exam Professional Cloud Database Engineer 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

Georgiann

18 days 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

21 days 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

22 days 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

...

Tien

27 days 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

...