Cloud Spanner for global distribution in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Cloud Spanner handle global consistency?

Cloud Spanner is designed for global distribution. What mechanism does it use to ensure strong consistency across regions?

A It uses a global lock manager to lock data before any transaction.

B It uses TrueTime API to assign timestamps and coordinate transactions globally.

C It replicates data asynchronously and resolves conflicts later.

D It relies on client-side conflict detection and retries.

💡 Hint

Think about how Spanner achieves external consistency with minimal latency.

Cloud Spanner uses Google's TrueTime API, which provides tightly synchronized clocks with bounded uncertainty. This allows Spanner to assign globally consistent timestamps to transactions, ensuring strong consistency across regions.

❓ Architecture

intermediate

Choosing Spanner instance configuration for global users

You have users in North America, Europe, and Asia. You want low latency reads and writes globally. Which Spanner instance configuration is best?

A Multi-region instance with nodes in US, Europe, and Asia regions.

B Single-region instance in US-central1 only.

C Single-region instance in US-central1 with multi-region replicas.

D Multi-region instance with nodes only in US and Europe.

💡 Hint

Consider where your users are and how Spanner distributes data.

A multi-region instance with nodes in all user regions reduces latency by placing data close to users and ensures high availability globally.

❓ security

advanced

Securing data in Cloud Spanner for global distribution

Which option correctly describes how Cloud Spanner secures data at rest and in transit globally?

A Data is encrypted at rest using Google-managed keys only; in transit encryption is optional.

B Data is encrypted only in transit; at rest it is stored unencrypted for performance.

C Data is encrypted at rest and in transit only within a single region.

D Data is encrypted at rest using customer-managed keys and in transit using TLS.

💡 Hint

Think about Google Cloud's default encryption and customer control options.

Cloud Spanner encrypts data at rest by default using Google-managed keys but also supports customer-managed encryption keys. All data in transit is encrypted using TLS to protect data globally.

✅ Best Practice

advanced

Optimizing schema design for global Cloud Spanner instances

Which schema design practice helps reduce latency and improve performance in a globally distributed Cloud Spanner instance?

A Avoid primary keys to allow flexible querying across regions.

B Use wide tables with many nullable columns to reduce joins.

C Use interleaved tables to colocate related data physically.

D Use many small tables with no foreign keys to simplify replication.

💡 Hint

Think about how data locality affects distributed database performance.

Interleaved tables store related rows physically close, reducing cross-node communication and improving latency in global instances.

🧠 Conceptual

expert

Impact of TrueTime uncertainty on transaction commit latency

Cloud Spanner uses TrueTime with bounded uncertainty for global consistency. How does increasing TrueTime uncertainty affect transaction commit latency?

A Higher uncertainty increases commit latency because Spanner waits longer to ensure consistency.

B Higher uncertainty decreases commit latency by allowing faster commits.

C TrueTime uncertainty has no effect on commit latency as commits are asynchronous.

D Higher uncertainty causes Spanner to abort more transactions but does not affect latency.

💡 Hint

Consider why Spanner waits before committing transactions.

Spanner waits out the uncertainty window to guarantee external consistency. Larger uncertainty means longer wait times, increasing commit latency.