Examkin

Question

Difficulty: HardProvisioning Storage and Database Systems

An organization is deploying an enterprise application requiring a relational database on Google Cloud to handle financial transactions across three continents. The transaction volume requires predictable low latency (<10 ms reads and writes) globally, automatic horizontal scaling without manual sharding, and strong serializable consistency. As a Principal Cloud Architect, which database provisioning strategy should you select to meet these technical requirements while minimizing operational maintenance?

  1. Provision a Cloud Spanner instance configured with a multi-region instance configuration spanning the required geographical regions.Answer
  2. B
    Provision a Cloud SQL for PostgreSQL instance with cross-region read replicas in each target continent and execute automated application failovers.
  3. C
    Provision a multi-node Compute Engine cluster running self-managed PostgreSQL with custom continuous replication and manual database sharding.
  4. D
    Provision a multi-region Cloud Bigtable cluster with multi-cluster routing enabled to support global write transactions.

Answer

Provision a Cloud Spanner instance configured with a multi-region instance configuration.
Cloud Spanner is the fully managed enterprise database service on Google Cloud engineered specifically for multi-region transactional workloads requiring strong (external) consistency, high availability, and automatic horizontal scaling without manual sharding.

Step-by-Step Solution

1
Analyze the technical requirements
Identified global distribution across three continents, strict serializable consistency for financial transactions, high write scalability without sharding, and minimal operational maintenance.
Relational transactions across multiple continents require true distributed ACID capabilities.
2
Evaluate GCP managed database offerings against requirements
Cloud Spanner is designed specifically for globally distributed relational workloads requiring strong consistency and automatic horizontal partitioning.
Cloud SQL lacks multi-region write scalability, while Bigtable is NoSQL and lacks multi-row ACID transactional semantics.

Key Concept

Selecting and provisioning globally consistent relational database services (Cloud Spanner vs Cloud SQL)
Rate this question

Topics

Provisioning Storage and Database Systems

More questions from this topic