About the Exam

Professional Cloud Database Engineer is a Google Cloud certification for database professionals with substantial Google Cloud and overall database experience. It covers designing scalable and highly available cloud database solutions, managing solutions across multiple database products, migrating data solutions, and deploying databases in Google Cloud. Passing demonstrates you can translate business and technical requirements into scalable, cost-effective Google Cloud database solutions.

Exam Topics

Design scalable and highly available cloud database solutions0%
Manage a solution that can span multiple database solutions0%
Migrate data solutions0%
Deploy scalable and highly available databases in Google Cloud0%

How to Use This Practice Exam

Browse — Read each question, select your answer, and reveal the explanation.
Exam Mode — Simulate real exam conditions with a timed session and score report.
Learn Mode — Spaced repetition schedules questions you struggle with for long-term retention.

Download the Full Exam PDF

Get every question and answer in a clean, printable PDF built for offline study. Purchase once, keep permanent access, and re-download the latest version anytime.

Get PDF

Learn More

Last updated June 29, 2026 at 3:33 AM

Topic filter

Retired questions

Question sort

Questions per page

QuestionQ1

Deploy scalable and highly available databases in Google Cloud

An online delivery business that mainly serves retail customers uses Cloud SQL for MySQL for its inventory and scheduling application. As part of the high-availability and disaster-recovery design, the required recovery time objective (RTO) and recovery point objective (RPO) must be measured in minutes rather than hours. You need a high-availability configuration that can recover with no data loss during either a zonal or regional failure. What should you do?

Explanation

Cloud SQL high availability uses synchronous replication across zones within a region, so a zonal failover can occur without data loss. Cross-region replicas provide disaster-recovery capability for a regional outage, but their replication is asynchronous; replication lag determines the possible data-loss window during regional recovery.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ2

Deploy scalable and highly available databases in Google Cloud

Your company is building a global ecommerce website on Google Cloud. The development team is creating a shopping-cart service that must be durable and elastically scalable under live traffic. Business disruption from unplanned downtime must remain below 5 minutes per month. Additionally, the application requires very low-latency writes. You need a data-storage solution with high write throughput and 99.99% uptime. What should you do?

Explanation

Cloud Spanner is a horizontally scalable, strongly consistent ACID database suited to durable ecommerce transaction data such as shopping carts. A regional Spanner instance has a 99.99% monthly uptime SLA, satisfying the less-than-five-minutes-per-month availability target, and Spanner scales compute and storage to support high write throughput. Multi-region configurations can provide even higher availability when required.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ3

Deploy scalable and highly available databases in Google Cloud

You are designing a highly available (HA) Cloud SQL for PostgreSQL instance for use by 100 databases. Each database contains 80 tables migrated from your on-premises environment to Google Cloud. The applications that use these databases run in multiple US regions, and you must ensure low latency for both read and write operations. What should you do?

Explanation

A regional Cloud SQL HA configuration provides a primary and standby across separate zones, enabling automatic failover and preserving availability for writes. Cross-region read replicas in us-east1 and us-west1 place read capacity nearer to applications in those regions, which improves read latency while the HA primary handles writes in its configured region.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ4

Design scalable and highly available cloud database solutions

You are designing a payments-processing application on Google Cloud. The application must keep serving requests and prevent user disruption if a regional failure happens. You need to use AES-256 to encrypt database data and want to control where the encryption key is stored. What should you do?

Explanation

Cloud Spanner multi-region configurations replicate data across regions and maintain availability during regional failures. Spanner supports customer-managed encryption keys (CMEK) in Cloud KMS, which lets the customer control key location, lifecycle, permissions, and rotation. Cloud KMS symmetric encryption keys use AES-256.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ5

Migrate data solutions

You are planning to migrate a large Oracle database to AlloyDB for PostgreSQL. The database contains a substantial amount of application logic in stored procedures that must be migrated to the target database. You want to minimize both the migration effort and migration downtime. What should you do?

Explanation

Database Migration Service conversion workspaces convert Oracle schema and supported code objects, including stored procedures, to PostgreSQL syntax. A continuous Database Migration Service job performs the initial data backfill and then uses change data capture (CDC) to keep AlloyDB synchronized until cutover, which reduces downtime. Legacy conversion workspaces are older, more limited, use Ora2Pg-based conversion, and are not recommended for migrations.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ6

Deploy scalable and highly available databases in Google Cloud

Your company is adopting AlloyDB for a business-critical application with these requirements:

RTO: Under 4 hours
RPO: 6 hours (maximum tolerated data loss)
Daily backups with a 7-day retention period

You must design a solution that meets these requirements.

What should you do?

Explanation

AlloyDB automated backups can be scheduled daily and retained for seven days. Enabling continuous backup and recovery provides point-in-time recovery and an RPO of zero, which is more stringent than a maximum six-hour data-loss tolerance; it also supports recovery from a recent point in time for the required recovery objective.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

Back home