Test your Spanner knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What does horizontal scalability mean in the context of a database like Spanner, as opposed to vertical scaling?
Questions in this quiz
What does horizontal scalability mean in the context of a database like Spanner, as opposed to vertical scaling?
What replication/consensus mechanism does Spanner use internally to keep replicas of the same data consistent across machines?
What does it mean that Spanner provides "external consistency" (sometimes called strict serializability) for transactions?
What is Cloud Spanner's relationship to Google's internal Spanner system that predates the public cloud product?
Why might a globally distributed e-commerce inventory system be a good real-world fit for Spanner's architecture?
What does Spanner's support for "interleaved tables" allow, as a schema design feature?
What is a common consideration when choosing a primary key strategy in Spanner, particularly around avoiding "hotspotting"?
What SQL dialect(s) does Spanner support for querying data?
What has historically been the classic tradeoff in distributed database design that Spanner is often cited as addressing?
What does it mean that Spanner is "globally distributed," in terms of where data can be replicated?
How does Spanner support both relational (SQL) query capabilities and horizontal scalability across many machines, unlike a traditional single-node relational database?
What kind of application workload is Spanner particularly well suited for, given its combination of strong consistency and global scale?