Test your Spanner knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What does it mean that Spanner is "globally distributed," in terms of where data can be replicated?
In this round
What does it mean that Spanner is "globally distributed," in terms of where data can be replicated?
What SQL dialect(s) does Spanner support for querying data?
What does Spanner's support for "interleaved tables" allow, as a schema design feature?
What does it mean that Spanner offers both a "GoogleSQL" interface and a "PostgreSQL-compatible" interface as separate dialect options?
What is Google Cloud Spanner?
How does Spanner support both relational (SQL) query capabilities and horizontal scalability across many machines, unlike a traditional single-node relational database?
What is Spanner's "TrueTime" API, and why is it central to Spanner's design?
What kind of application workload is Spanner particularly well suited for, given its combination of strong consistency and global scale?
How does Spanner typically handle read scalability for read-heavy workloads?
What is a common consideration when choosing a primary key strategy in Spanner, particularly around avoiding "hotspotting"?
What does it mean that Spanner provides "external consistency" (sometimes called strict serializability) for transactions?
What does horizontal scalability mean in the context of a database like Spanner, as opposed to vertical scaling?