nerdexam
Google

PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #112

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…

The correct answer is B. Deploy Cloud Spanner using a multi-region instance, and place your compute resources close to. Cloud Spanner with a multi-region instance provides globally distributed relational storage with low-latency reads, strong consistency, horizontal scalability, and support for existing relational schemas - ideal for global retail transactions and inventory.

Designing and Planning Database Solutions

Question

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?

Options

  • AStore your data in Firestore in a multi-region location, and place your compute resources in one of
  • BDeploy Cloud Spanner using a multi-region instance, and place your compute resources close to
  • CBuild an in-memory cache in Memorystore, and deploy to the specific geographic regions where
  • DDeploy a Bigtable instance with a cluster in one region and a replica cluster in another geographic

How the community answered

(39 responses)
  • A
    10% (4)
  • B
    82% (32)
  • C
    5% (2)
  • D
    3% (1)

Why each option

Cloud Spanner with a multi-region instance provides globally distributed relational storage with low-latency reads, strong consistency, horizontal scalability, and support for existing relational schemas - ideal for global retail transactions and inventory.

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

Firestore is a NoSQL document database and cannot retain a relational schema with joins, foreign keys, and relational integrity constraints.

BDeploy Cloud Spanner using a multi-region instance, and place your compute resources close toCorrect

Cloud Spanner multi-region instances replicate data across multiple geographic regions with strong consistency, enabling low-latency reads by routing requests to the nearest replica. It supports standard SQL and relational schemas, meaning the existing data model can be retained with minimal changes, while automatic sharding handles global scale for sales transactions and inventory lookups without manual partitioning.

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

Memorystore is an in-memory caching service (Redis/Valkey) and is not suitable as a primary storage layer for durable sales transactions and inventory data.

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

Bigtable is a NoSQL wide-column store optimized for high-throughput analytical and time-series workloads; it does not support relational schemas, SQL joins, or multi-row transactions needed for inventory and sales data.

Concept tested: Cloud Spanner multi-region for global relational transactional workloads

Source: https://cloud.google.com/spanner/docs/instances#available-configurations-multi-region

Topics

#Cloud Spanner#Relational Databases#Global Scalability#OLTP

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice