A multinational financial services company is re-architecting its core payment processing and ledger management system on Google Cloud. The system architecture must satisfy the following technical requirements: Provide globally distributed ACID transactions across multiple geographic regions with external consistency. Colocate customer account records with their associated payment transaction ledger records on storage splits to optimize join queries and eliminate cross-node communication. Prevent hotspotting on storage splits during high-throughput, write-intensive transactional workloads. Which database solution and schema design strategy should the company implement?

Deploy Cloud Spanner in a multi-region instance configuration; define the schema using table interleaving between parent Customer accounts and child Ledger records, and use universally unique identifiers (UUIDs) or bit-reversed sequences as primary keys.: ### What Cloud Spanner with Table Interleaving Is **Cloud Spanner** is a fully managed, mission-critical relational database service designed for global scale, zero scheduled downtime, and strict transactional consistency (ACID). It provides horizontal scaling across regions while maintaining relational schema structures, secondary indexes, and SQL support. ### How It Meets the Requirements * **Globally Distributed ACID Transactions:** A multi-region **Cloud Spanner** configuration utilizes synchronous Paxos consensus replication to guarantee external consistency and serializable isolation across multi-regional topologies. * **Optimizing Joins and Eliminating Cross-Node Overhead:** Implementing **table interleaving** physically colocates child `Ledger` rows with their parent `Customer` row in the same split. This allows queries that join parent and child data on the primary key hierarchy to execute locally within the same storage split, avoiding distributed cross-process network hops. * **Preventing Split Hotspots:** Using distributed primary key strategies such as **UUIDs** or **bit-reversed sequences** evenly distributes write throughput across the entire keyspace, preventing hot-spotting on specific splits. ### Key Advantages and Capabilities * **Table Interleaving:** Ensures strong spatial locality on disk for hierarchical, 1-to-N relational entities. * **Automatic Resharding and Balancing:** Spanner dynamically splits and balances data as load and dataset size grow. * **High Availability:** Multi-region configurations offer industry-leading availability of up to 99.999% (five 9s). * **Synchronous Replication:** Protects against regional outages without data loss. ### Why This Is Optimal Cloud Spanner is the only fully managed Google Cloud database engine designed specifically to deliver global relational transactions with sub-10ms latencies alongside schema-level features like table interleaving and fine-tuned primary key distribution.

Spanner Interleaved Schema Global Acid Transactions | professional-cloud-data-engineer

Spanner Interleaved Schema Global Acid Transactions

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A multinational financial services company is re-architecting its core payment processing and ledger management system on Google Cloud. The system architecture must satisfy the following technical requirements:

Provide globally distributed ACID transactions across multiple geographic regions with external consistency.
Colocate customer account records with their associated payment transaction ledger records on storage splits to optimize join queries and eliminate cross-node communication.
Prevent hotspotting on storage splits during high-throughput, write-intensive transactional workloads.

Which database solution and schema design strategy should the company implement?

Deploy Cloud Storage with the Standard storage class; write payment ledger events as Apache Iceberg tables governed by BigLake metastore, and execute updates via BigQuery federated queries.

Deploy Cloud Bigtable with multi-cluster routing; configure a single column family for transactions, and structure row keys with an auto-incrementing transaction sequence prefix.

Deploy Cloud Spanner in a single-region configuration; create independent tables for Customer accounts and Ledger records, and use monotonically increasing timestamps as the primary key for high-speed indexing.

Deploy Cloud Spanner in a multi-region instance configuration; define the schema using table interleaving between parent Customer accounts and child Ledger records, and use universally unique identifiers (UUIDs) or bit-reversed sequences as primary keys.

Professional Cloud Data Engineer

Spanner Interleaved Schema Global Acid Transactions

Related questions