G O O G L E C E R T I F I C A T I O N
Professional Cloud Database Engineer Practice Exam
Exam Number: 1005 | Last updated April 21, 2026 | 996+ questions across 4 vendor-aligned objectives
Earning the Professional Cloud Database Engineer certification signals that you your ability to apply Google Cloud to real business problems. It is built for database engineers, DBAs, and data platform specialists who design, migrate, and operate managed databases on Google Cloud. A passing score proves you can map platform capabilities to outcomes and make defensible technical choices under time pressure.
Heavy-weighted areas define where study time pays back fastest: 26% targets Designing Scalable and Reliable Databases (Cloud SQL high availability, Spanner regional versus multi-region, AlloyDB design); 25% targets Migrating Data Solutions (Database Migration Service, lift-and-shift versus refactor, minimizing downtime).
Supporting domains fill out the blueprint: 25% covers Deploying Scalable and Highly Available Databases in Google Cloud (read replicas, backups, point-in-time recovery, automated failover); 24% covers Managing a Solution That Can Span Multiple Database Options (polyglot persistence, Bigtable for time series, Firestore for operational data). Each still appears on the exam, so none can be safely skipped. Google updates exam guides regularly, so verify domain weights on the official certification page before you finalize a study plan.
Every answer links to the source. Each explanation below includes a hyperlink to the exact Google documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
650
practice exam users
90%
satisfied users
80.9%
passed the exam
4.9/5
quality rating
Test your Cloud Database Engineer knowledge
10 of 996+ questions
Question #1 - Designing Scalable and Reliable Databases
A global ticketing platform must process purchases across 12 regions with strict strong consistency and under 10ms median write latency in each region.
Which Google Cloud database is the best fit?
A) Cloud SQL with cross-region read replicas
B) Bigtable single-cluster
C) Cloud Spanner in a multi-region configuration
D) Firestore in Datastore mode single-region
Show solution
Correct answers: C – Explanation:
Cloud Spanner offers globally strong consistency and horizontal scale across regions. Cloud SQL read replicas are eventually consistent for reads and do not meet strong global write consistency. Bigtable is wide-column and lacks SQL transactions. Firestore single-region does not satisfy multi-region. Source: Check Source
Question #2 - Managing a Solution That Can Span Multiple Database Options
A telemetry platform ingests 500K writes per second of IoT sensor readings and must support rapid range scans by device and timestamp.
Which Google Cloud database matches the workload?
A) Cloud SQL Postgres with a composite index
B) Bigtable with a well-designed row key
C) Firestore in Native mode with a listener
D) BigQuery with streaming inserts only
Show solution
Correct answers: B – Explanation:
Bigtable handles very high write throughput and is optimized for row-key range scans, which is the time-series pattern. Cloud SQL does not sustain 500K writes/sec. Firestore is document-based, not designed for this volume. BigQuery is analytical and not optimized for high-QPS serving. Source: Check Source
Question #3 - Migrating Data Solutions
A DBA must migrate a 2 TB on-premises MySQL instance to Cloud SQL with minimal downtime and continuous change replication during the move.
Which Google Cloud service is purpose-built for this task?
A) Cloud Storage Transfer Service over SFTP
B) mysqldump into a Cloud Storage bucket once
C) Bigtable import utility
D) Database Migration Service with continuous migration
Show solution
Correct answers: D – Explanation:
Database Migration Service supports MySQL to Cloud SQL migrations with continuous replication and minimal downtime. Storage Transfer Service moves files, not live database changes. A one-time mysqldump requires a long downtime window. Bigtable import is unrelated. Source: Check Source
Question #4 - Deploying Scalable and Highly Available Databases in Google Cloud
A Cloud SQL Postgres instance is serving a reporting workload that is generating read contention against the production OLTP traffic.
Which Cloud SQL capability most directly offloads the reports?
A) Add a read replica and route reports there
B) Increase the storage tier to hyperdisk
C) Switch the charset to latin1
D) Disable automated backups to free IOPS
Show solution
Correct answers: A – Explanation:
Read replicas absorb read-heavy workloads so the primary handles OLTP. Storage tier does not separate traffic classes. Charset is unrelated. Disabling backups trades durability for IOPS and violates best practice. Source: Check Source
Question #5 - Designing Scalable and Reliable Databases
A DBA needs a fully managed PostgreSQL-compatible database that delivers strong analytical performance and better price-performance for large OLTP and HTAP workloads than community Postgres on Cloud SQL.
Which Google Cloud service fits?
A) Cloud SQL Postgres single-zone
B) AlloyDB for PostgreSQL
C) Spanner PostgreSQL dialect
D) Firestore in Datastore mode
Show solution
Correct answers: B – Explanation:
AlloyDB is Google’s Postgres-compatible managed database engineered for enterprise OLTP and HTAP performance. Cloud SQL single-zone is not designed for heavy HTAP. Spanner Postgres dialect is a different architecture. Firestore is not Postgres-compatible. Source: Check Source
Question #6 - Managing a Solution That Can Span Multiple Database Options
A mobile app needs a real-time, serverless document store that pushes updates to connected clients and supports offline sync.
Which Google Cloud service matches that profile?
A) Cloud SQL MySQL
B) Bigtable with a tall schema
C) BigQuery materialized views
D) Firestore in Native mode
Show solution
Correct answers: D – Explanation:
Firestore Native mode provides real-time listeners and client-side offline sync for mobile apps. Cloud SQL, Bigtable, and BigQuery do not offer that real-time client sync model. Source: Check Source
Question #7 - Deploying Scalable and Highly Available Databases in Google Cloud
A finance app accidentally ran a bulk delete on a Cloud SQL Postgres table ten minutes ago.
Which feature allows recovery to a point just before the delete?
A) Point-in-time recovery (PITR) on Cloud SQL
B) Cloud Storage lifecycle policies
C) VPC Flow Logs replay
D) Cloud Monitoring alerts
Show solution
Correct answers: A – Explanation:
Point-in-time recovery restores a Cloud SQL instance to any moment within the retention window, which addresses this incident. Storage lifecycle rules manage object tiers, not databases. VPC Flow Logs are network records. Monitoring alerts notify but do not restore. Source: Check Source
Question #8 - Migrating Data Solutions
A team is moving an Oracle RAC OLTP database to Google Cloud and wants to eliminate Oracle licensing while keeping the same relational model and SQL.
Which migration path is most appropriate?
A) Lift-and-shift Oracle to Compute Engine and keep licensing
B) Convert to Bigtable with custom serialization
C) Refactor to AlloyDB or Cloud SQL for PostgreSQL
D) Rewrite everything as flat files in Cloud Storage
Show solution
Correct answers: C – Explanation:
Refactoring to AlloyDB or Cloud SQL for PostgreSQL removes Oracle licensing while preserving a relational model. Lift-and-shift keeps licensing, which violates the constraint. Bigtable and flat files are not relational and break existing SQL. Source: Check Source
Question #9 - Managing a Solution That Can Span Multiple Database Options
An architect must choose a primary store for a catalog that is read-heavy, needs flexible attributes per item, and is served to a global web app with low read latency.
Which service is the best primary store?
A) Cloud SQL with a rigid relational schema
B) Firestore with caching and global reads
C) Bigtable tuned as a time-series store
D) BigQuery as the primary transactional store
Show solution
Correct answers: B – Explanation:
Firestore’s flexible document model and global reads match a read-heavy, flexible-schema catalog. Rigid SQL fights flexible attributes. Bigtable time-series schemas are for sequential keys, not catalog browse. BigQuery is analytical, not a primary transactional store. Source: Check Source
Question #10 - Migrating Data Solutions
During a production cutover, the team notices replication lag rising between the source MySQL and the Cloud SQL target under peak load.
Which action most directly reduces cutover risk?
A) Pause writes briefly, let replication catch up, then flip traffic
B) Cut over immediately and accept data loss
C) Disable monitoring to reduce overhead
D) Recreate the Cloud SQL instance during peak load
Show solution
Correct answers: A – Explanation:
Pausing writes briefly so replication catches up before flipping traffic is the standard minimal-downtime cutover pattern. Cutting over with lag causes inconsistency. Disabling monitoring removes visibility. Recreating during peak load is high risk. Source: Check Source
Get 996+ more questions with source-linked explanations
Every answer traces to the exact Google documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated April 21, 2026
Learn more...
What the Cloud Database Engineer exam measures
- Designing Scalable and Reliable Databases (26%): Apply Google Cloud practices to Cloud SQL high availability, Spanner regional versus multi-region, AlloyDB design.
- Managing a Solution That Can Span Multiple Database Options (24%): Apply Google Cloud practices to polyglot persistence, Bigtable for time series, Firestore for operational data.
- Migrating Data Solutions (25%): Apply Google Cloud practices to Database Migration Service, lift-and-shift versus refactor, minimizing downtime.
- Deploying Scalable and Highly Available Databases in Google Cloud (25%): Apply Google Cloud practices to read replicas, backups, point-in-time recovery, automated failover.
How to prepare for this exam
- Review the Professional Cloud Database Engineer official exam guide end to end before you commit a study plan, so every later hour is spent against the published blueprint.
- Complete the relevant Google Cloud Skills Boost learning path and treat its labs as non-optional rather than extra credit.
- Get hands-on practice in Qwiklabs sandbox, repeating the same tasks from memory until configuration feels routine.
- Apply what you learn in real-world project experience — your day job, a volunteer project, or an open-source contribution — so the concepts stick.
- Master one objective at a time, starting with the highest-weighted domain on the blueprint and moving down from there.
- Use PowerKram learn mode with feedback and sourced links to close gaps while the answer rationale is still fresh.
- Finish with PowerKram exam mode across all objectives under realistic time pressure before you book the real exam.
Career paths and salary outlook
Holding the Professional Cloud Database Engineer certification typically supports roles such as:
- Cloud Database Engineer: roughly $ 125,000 to $175,000 USD per year in the US market (range varies by region, years of experience, and specialization). See current data on Glassdoor.
- Senior Database Administrator: roughly $ 115,000 to $160,000 USD per year in the US market (range varies by region, years of experience, and specialization). See current data on Levels.fyi.
- Data Platform Engineer: roughly $ 130,000 to $180,000 USD per year in the US market (range varies by region, years of experience, and specialization). See current data on Payscale.
Official resources
Work directly from Google’s own preparation resources and treat third-party content as a supplement: