


The database engineer exam asks you to pick a database and defend it. A workload arrives with a consistency requirement, a scale target, a latency budget and a migration constraint, and Cloud SQL, Spanner, Bigtable, Firestore, AlloyDB and BigQuery each fail some of those in ways you're expected to know.
You get 300 questions across six papers of 50, matched to the exam guide: designing scalable and highly available cloud database solutions, managing a solution that can span multiple database solutions, migrating data solutions, and deploying scalable and highly available databases in Google Cloud.
Service selection carries the exam. Spanner's external consistency and split behaviour, Bigtable's row key design and the hotspotting that follows a bad one, Cloud SQL's high availability and read replica options, AlloyDB's positioning against Cloud SQL, and Firestore's query limitations are all worked through with the trade-off stated rather than implied.
Migration gets its own weight, including Database Migration Service, minimising downtime, handling schema differences, and validating a cutover. Backup, point-in-time recovery, encryption with customer-managed keys and IAM for database access complete the coverage.
Each explanation names the requirement that eliminates the alternatives. Answer order randomises. Work all six papers before booking.
Disclaimer: This is an independent preparation course. It is not affiliated with, endorsed by, or sponsored by Google LLC. Google Cloud, Spanner, Bigtable and BigQuery are trademarks of Google LLC. All questions are original practice items written by the author.