Home Certifications FAQ Partners Blog

·EN·DE·FR·ES·PT

Google Cloud · GCP-PCDB · Advanced

Professional Cloud Database Engineer — Practice Questions and Mock Exam

Prepare for GCP-PCDB with original practice questions and clear answer explanations. Ask Alex, your AI tutor, when you need more detail, use your results to identify topics to review, and practice your pacing with timed mock exams.

Start practicing GCP-PCDB free Buy GCP-PCDB access for $29.99

Buy GCP-PCDB access for $29.99 Start practicing GCP-PCDB free

55Mock exam questions

120minTime limit

Checked against Google Cloud · August 2026 · Current exam version

Overview

About the exam

The Professional Cloud Database Engineer certification validates your ability to design, create, manage, and troubleshoot Google Cloud databases. This credential is aimed at database professionals who translate business and technical requirements into scalable, resilient, and cost-effective database solutions. The exam covers a broad range of Google Cloud database services including Cloud SQL (MySQL, PostgreSQL, SQL Server), AlloyDB for PostgreSQL, Spanner, Firestore, Bigtable, and Memorystore, as well as migration and multi-database management scenarios.

Try the practice preview

Try five GCP-PCDB questions

Try five practice questions from the app’s current Professional Cloud Database Engineer question bank, with answers and explanations.

Migrate data solutions1 / 5

You are designing a migration strategy for moving a 5 TB Oracle database to Cloud SQL for PostgreSQL. The application can tolerate a maximum of 30 minutes of downtime. Which migration approach is most appropriate?

AlexFull explanation from Alex

Database Migration Service (DMS) supports continuous migration for Oracle to Cloud SQL for PostgreSQL. During continuous migration, DMS first performs a full dump of source data, then switches to Change Data Capture (CDC) using Oracle LogMiner to replicate ongoing changes. This enables near-zero downtime: you stop source writes, verify data, and promote the destination. For a 5 TB database with a 30-minute downtime window, continuous migration is ideal because CDC keeps the destination synchronized until cutover. A SQL dump export requires extended downtime proportional to database size. Manual re-entry is impractical at scale. Datastream to Cloud Storage via Dataflow adds unnecessary intermediate steps and complexity compared to DMS's native CDC pipeline. Ref: cloud.google.com/database-migration/docs/oracle-to-postgresql/scenario-overview

Sourcedocs.cloud.google.com

Design innovative, scalable, and highly available cloud database solutions2 / 5

A global fintech application requires a relational database that offers strong consistency, horizontal write scalability, and a 99.999% monthly availability SLA that protects against an entire region becoming unavailable. The architecture team wants Google Cloud to handle replication and failover automatically without application-level sharding. Which database configuration should you design?

AlexFull explanation from Alex

Spanner is Google's horizontally scalable, strongly consistent relational database. Its availability is determined by the instance configuration: regional configurations keep replicas within a single region and carry a 99.99% SLA, while multi-region configurations spread read-write replicas across regions and carry the higher 99.999% SLA (under five minutes of downtime per year). Multi-region configurations contain at least three regions and five replicas, and Spanner automatically handles failover when a region becomes unavailable. This contrasts with Cloud SQL, where HA is only zonal-within-a-region. Choosing the instance configuration is therefore the central design lever for both availability and data residency. Exam tip: map the magic number 99.999% directly to Spanner multi-region, and 99.99% (regional Spanner) or 99.95% (Cloud SQL HA) to the lower tiers.

Sourcecloud.google.com

Manage a solution that can span multiple database technologies3 / 5

You are managing a Cloud SQL for MySQL instance and need to configure the maintenance window. The application has peak usage between 9 AM and 6 PM on weekdays. When should you schedule the maintenance window?

AlexFull explanation from Alex

Cloud SQL lets you configure a maintenance window specifying the day and hour for updates. Google's documentation recommends scheduling maintenance during low-traffic periods to minimize user impact. The default maintenance windows are already set to off-peak: weekdays 10 PM–6 AM and weekends. Google's own example shows a retailer scheduling maintenance at midnight on Sundays—the lowest traffic period. With peak usage from 9 AM–6 PM on weekdays, scheduling during off-peak hours (weekends or late night) is correct. Maintenance is fully schedulable (the option “Maintenance cannot be scheduled and occurs randomly” is wrong—it does not occur randomly). Scheduling after backup windows has no correlation with low impact. During peak hours would maximize disruption. You can also set deny maintenance periods for up to 90 days to block updates during critical business periods. Ref: cloud.google.com/sql/docs/mysql/maintenance

Sourcedocs.cloud.google.com

Deploy scalable and highly available databases in Google Cloud4 / 5

You are deploying a Cloud SQL for PostgreSQL instance with high availability and need to test the disaster recovery process. How can you verify that automatic failover works correctly?

AlexFull explanation from Alex

Cloud SQL provides a manual failover capability specifically for testing HA disaster recovery. Google's documentation states: "Testing failover is optional, but is recommended so that you can see how your application responds in the event of a failover." You trigger it via gcloud sql instances failover INSTANCE_NAME or the Cloud SQL Admin API (instances.failover), or through the Console's Failover button. This simulates a zone failure and triggers the automatic failover mechanism to the standby instance, letting you validate application reconnection logic and measure actual failover time. Deleting the primary destroys the instance permanently—this is not a test. Shutting down a zone via Console is not possible for individual users. Disconnecting the network is unreliable and doesn't test the actual Cloud SQL failover mechanism. Ref: cloud.google.com/sql/docs/postgres/configure-ha#initiate-failover

Sourcecloud.google.com

Migrate data solutions5 / 5

You are planning a zero-downtime migration from an on-premises Oracle database to Spanner. Which migration approach should you follow?

AlexFull explanation from Alex

Migrating Oracle to Spanner requires a phased approach because it is a heterogeneous migration—Spanner has a fundamentally different data model (no stored procedures, no triggers, different key design). Google's official migration guide prescribes: (1) convert schema and data model, (2) translate SQL queries, (3) modify the application to write to both databases (dual-write), (4) bulk export/import data via Dataflow, (5) maintain consistency using CDC (e.g., Striim or Oracle LogMiner), (6) validate and cut over. This phased approach enables zero downtime by maintaining both systems in sync until confidence is established. Datastream cannot stream directly into Spanner. DMS does not support direct Oracle-to-Spanner migration. CSV export/import requires downtime and lacks change synchronization. Ref: cloud.google.com/spanner/docs/migrating-oracle-to-cloud-spanner

Sourcedocs.cloud.google.com

Create a free account

Question pool

304 practice questions

The Pass-IT question pool gives you material to practice for GCP-PCDB. A Pass-IT mock exam uses 55 questions and a 120-minute time limit; these are practice settings.

Pool details: GCP-PCDB

Objectives in the guide11 objectives listed in the official guide

across 4 domains in the official exam guide

Pool size304 questions

= The pool size is equivalent to 5 sets of 55 questions; this does not mean that each mock exam uses a separate set.

Blueprint domains4 domains in the exam blueprint

Design innovative, scalable, and highly available cloud database solutions 90 · Manage a solution that can span multiple database technologies 81 · Migrate data solutions 65 · Deploy scalable and highly available databases in Google Cloud 68

Recorded as checked against sources304 of 304

questions recorded as having their answer, options, and explanation checked against official Google Cloud documentation

How questions are made →

Exam domains

What's on the exam

Designing scalable, highly available database solutions carries the most weight at 32%, testing capacity planning against workload metrics, the tradeoff between zonal and multi-regional deployment, database networking and encryption setup, and the judgment call between a Google-managed service and a self-run alternative. Managing a solution across multiple database technologies follows at 25%: IAM and user-level access control, diagnosing slow queries and resource contention, designing backup and recovery around RTO and RPO targets, and tuning cost through scaling and replication choices. Migration planning takes 23%, covering near-zero-downtime strategies, fallback and reverse-replication paths, and matching a migration tool to a specific source and target combination. Deploying databases that survive failure closes the blueprint at 20%: provisioning multi-region replicas and automated failover, verified through ongoing testing rather than designed on paper.

The exam treats operating a database as inseparable from designing one: nearly half the questions sit in ongoing management and migration rather than initial architecture, which rewards candidates who have run a production database through a failover or a cutover.

Exam blueprint: GCP-PCDB

Design innovative, scalable, and highly available cloud database solutions~32%

Match database compute and storage sizing to real usage patterns, weigh high-availability and disaster-recovery tradeoffs, plan how applications will actually connect, and choose between managed and self-run database options based on cost and compliance needs.

≈ 26 h

Manage a solution that can span multiple database technologies~25%

Sort out how applications connect and authenticate across a mixed database estate, keep it monitored with backup and recovery in place, tune it for cost and performance, and automate the routine maintenance that keeps it healthy.

≈ 20 h

Migrate data solutions~23%

Plan database migrations that minimize downtime, keep a fallback and reverse-replication path in case something goes wrong, and pick the right migration tool for the source and target involved.

≈ 18 h

Deploy scalable and highly available databases in Google Cloud~20%

Stand up databases built to survive failure - multi-region replication, read replicas, automated provisioning - and verify the resulting setup through testing and ongoing monitoring.

≈ 16 h

Format

Exam format and question types

The exam draws 50–60 multiple-choice and multiple-select questions inside a 120-minute window, weighted roughly 80% single-answer to 20% multiple-select. There are no case studies on the current exam guide; questions are standalone scenarios testing database design, multi-database management, migration planning, and high-availability deployment across Google Cloud's database services.

Question types: GCP-PCDB

Multiple Choice80%

Select the single answer that best meets the question’s requirements.

Multiple Response20%

Select multiple answers. Follow the question’s instructions on how many to choose.

See Google Cloud for official question-format information. The shares shown describe the Pass-IT practice pool; they do not establish the proportions on the official exam.

Planning

Preparing for GCP-PCDB

The exam runs through Pearson VUE, either online-proctored or at a testing center, and is offered in English and Japanese. The certification holds for 2 years and is renewed every 2 years during the renewal eligibility period.

Preparation and logistics: GCP-PCDB

Preparation

Illustrative study time50–120 h

illustrative planning range: 50 h with relevant experience to 120 h when starting out; your needs may fall outside this range

LevelAdvanced

Recommended backgroundNo formal prerequisites. Recommended 5+ years of overall database experience including 2 years hands-on with Google Cloud database solutions.

Taking and maintaining the certification

DeliveryPearson VUE (online-proctored or testing center)

Retake policy14-day wait after the first failed attempt, 60 days after the second, 365 days after the third. Maximum 4 attempts in a 2-year period.

Certification validity2 years

Recertify every 2 years during the renewal eligibility period

Official guideView on provider site

Study notes

Common pitfalls

Topics to review: GCP-PCDB

01Cloud SQL vs Spanner
Confusing when to use Cloud SQL (single-region relational) vs Spanner (globally distributed relational) based on consistency and scale requirements
02AlloyDB positioning
Not understanding AlloyDB's position as a high-performance PostgreSQL-compatible option between Cloud SQL and Spanner
03Migration tools
Overlooking Database Migration Service and Datastream capabilities for zero-downtime and CDC migrations
04HA vs DR
Confusing high availability (automatic failover within a region) with disaster recovery (cross-region replication and failover)
05IAM for databases
Not distinguishing between Cloud IAM roles and database-level user permissions for access control
06NoSQL selection
Choosing the wrong NoSQL service (Firestore for documents vs Bigtable for wide-column analytics vs Memorystore for caching)

Practice with questions and explanations in Pass-IT →

Questions

Frequently asked questions

Which pitfalls should I review when preparing for Professional Cloud Database Engineer?

Topics to review include Cloud SQL vs Spanner, AlloyDB positioning, Migration tools, HA vs DR, IAM for databases, NoSQL selection. Work through examples to check that you understand the distinctions and can explain your answer.

What does the Professional Cloud Database Engineer exam cover?

Designing scalable and highly available database solutions is the largest section at 32%, followed by managing solutions that span multiple database technologies at 25%. Migrating data solutions takes 23% and deploying databases 20%. Migration is a quarter of the exam, which surprises people who prepared only for greenfield design.

What experience does the Cloud Database Engineer exam assume?

Google Cloud recommends five or more years of overall database work including two years hands-on with its own database services. That is the highest recommended background of any exam in our catalog. Nothing is enforced at booking, but the catalog budget of 80 hours assumes that experience is already there.

How often do you have to recertify as a Cloud Database Engineer?

Every two years, inside the renewal eligibility period. Google Cloud has no continuing-education route, so recertification means sitting an exam rather than logging credits.

How soon can you retake the Cloud Database Engineer exam?

After 14 days for the second attempt, 60 days for the third and 365 days beyond that, capped at four attempts in a two-year period. The escalation is the same across the Google Cloud professional range.

One certification, 12 months

Practice for GCP-PCDB

Focus your practice on one certification, or choose Pro to practice across all certifications.

Buy GCP-PCDB access for $29.99

Start a free practice sessionTry the first 20 questions without a card to see whether the practice suits you.

For eligible purchases: money-back guarantee if you fail your exam.

View guarantee terms →