professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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:
Which database solution and schema design strategy should the company implement?
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 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 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.
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 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 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.
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.
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.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.
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.