CloudExamCheap

PCDBE Practice Exam: Professional Cloud Database Engineer

197 questions · 120 min timed mode · Google Cloud · Updated 2026

Cloud SQL, Spanner, Bigtable, Firestore — run GCP databases like a professional, not a gambler.

What you'll be tested on

Sample PCDBE questions

You are developing a new application on a VM that is on your corporate network. The application will use Java Database Connectivity (JDBC) to connect to Cloud SQL for PostgreSQL. Your Cloud SQL instance is configured with IP address 192.168.3.48, and SSL is disabled. You want to ensure that your application can access your database instance without requiring configuration changes to your database. What should you do?
  1. Define a connection string using your Google username and password to point to the external (public) IP address of your Cloud SQL instance.
  2. Define a connection string using a database username and password to point to the internal (private) IP address of your Cloud SQL instance.
  3. Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the internal (private) IP address of your Cloud SQL instance.
  4. Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the external (public) IP address of your Cloud SQL instance.
Show answerC — Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the internal (private) IP address of your Cloud SQL instance.
The instance IP 192.168.3.48 is a private IP, and the app runs outside Google Cloud on a corporate network, so a direct private-IP connection will not route. The Cloud SQL Auth proxy solves this: it runs on the client, authenticates with a service account, and establishes a secure tunnel to the instance even when SSL is disabled and no database changes are made. Options A and D rely on a public IP, which is not configured here and would expose the instance. Option B fails because private IPs are unreachable from outside the VPC without the proxy or VPN.
Your company wants to move to Google Cloud. Your current data center is closing in six months. You are running a large, highly transactional Oracle application footprint on VMWare. You need to design a solution with minimal disruption to the current architecture and provide ease of migration to Google Cloud. What should you do?
  1. Migrate applications and Oracle databases to Google Cloud VMware Engine (VMware Engine).
  2. Migrate applications and Oracle databases to Compute Engine.
  3. Migrate applications to Cloud SQL.
  4. Migrate applications and Oracle databases to Google Kubernetes Engine (GKE).
Show answerA — Migrate applications and Oracle databases to Google Cloud VMware Engine (VMware Engine).
Google Cloud VMware Engine lets you lift-and-shift the existing VMware environment, including Oracle workloads, into Google Cloud with minimal architectural change, which matches the requirement for minimal disruption and easy migration within six months. Running Oracle on Compute Engine requires re-architecting, licensing management, and manual setup. Cloud SQL does not support Oracle, so migrating applications there would require a full database replatform. GKE containerization is also a major refactor and Oracle is not a typical containerized fit. VMware Engine preserves the current architecture while meeting the deadline.
Your customer has a global chat application that uses a multi-regional Cloud Spanner instance. The application has recently experienced degraded performance after a new version of the application was launched. Your customer asked you for assistance. During initial troubleshooting, you observed high read latency. What should you do?
  1. Use query parameters to speed up frequently executed queries.
  2. Change the Cloud Spanner configuration from multi-region to single region.
  3. Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables.
  4. Use SQL statements to analyze SPANNER_SYS.QUERY_STATS* tables.
Show answerC — Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables.
High read latency in Spanner should be investigated with the SPANNER_SYS.READ_STATS tables, which contain built-in statistics about read operations, including read shapes and latency, helping you identify which reads or key ranges are slow or hotspotting. QUERY_STATS tables analyze query execution statistics, which is useful for slow queries, but the observed symptom is read latency specifically, making READ_STATS the right first tool. Query parameters help with query plan caching, not diagnosing reads. Changing from multi-region to single region is a drastic architectural change, not a troubleshooting step.

Access plans

AccessPrice
3 months$8.99$3.99
1 year$14.99$8.99
Lifetime$24.99$14.99
Practice PCDBE now →
Free preview inside — try 5 questions before you pay anything.

FAQ

How many practice questions are in this PCDBE bank?
197 questions covering the current PCDBE Professional Cloud Database Engineer syllabus, every one with the correct answer and an explanation.
How long is the real PCDBE exam?
The official PCDBE exam gives you 120 minutes. Our timed exam mode uses the same limit so the pace feels familiar.
What does PCDBE access cost?
Plans start at $3.99 for 3 months. One payment, no subscription — and far cheaper than retaking the real exam.