Free Professional-Cloud-Database-Engineer Practice Test Questions and Answers (2026)

Last Update Check

View Mode
Q: 1
Your ecommerce application connecting to your Cloud SQL for SQL Server is expected to have additional traffic due to the holiday weekend. You want to follow Google-recommended practices to set up alerts for CPU and memory metrics so you can be notified by text message at the first sign of potential issues. What should you do?
Options
15 comments in the community discussion
6
Makes sense to pick D here. Cloud Monitoring lets you set alert policies on CPU and memory no code required, and SMS can be configured as a notification channel. A is way more complex than needed. Pretty sure D is Google's best practice, but open to other opinions.
1
I don't think B is right here. D is the only option that natively supports alerting for CPU and memory with SMS through Cloud Monitoring. Error Reporting doesn't do general metric monitoring, it's more for logs/exceptions. Anyone see a reason you'd use B?
Q: 2
Your organization is running a MySQL workload in Cloud SQL. Suddenly you see a degradation in database performance. You need to identify the root cause of the performance degradation. What should you do?
Options
12 comments in the community discussion
6
Option B, Logs let you dig deeper, but first thing is to check metrics like CPU and memory in Cloud Monitoring. A is tempting but can miss the bigger picture.
1
A , Logs Explorer should highlight any error spikes or slow queries logged by MySQL. I usually start there for quick clues when performance drops. Not 100% sure it's the fastest way here though.
Q: 3
Your company has PostgreSQL databases on-premises and on Amazon Web Services (AWS). You are planning multiple database migrations to Cloud SQL in an effort to reduce costs and downtime. You want to follow Google-recommended practices and use Google native data migration tools. You also want to closely monitor the migrations as part of the cutover strategy. What should you do?
Options
18 comments in the community discussion
6
Option A fits best since Database Migration Service (DMS) is Google's native tool, and it's designed for both one-time and minimal-downtime migrations with monitoring built in. Pretty sure that's what Google wants you to pick here, but open if anyone has counterpoints!
3
A. matches official guide recommendations for native migrations. I’ve seen similar on practice tests too.
Q: 4
You are choosing a new database backend for an existing application. The current database is running PostgreSQL on an on-premises VM and is managed by a database administrator and operations team. The application data is relational and has light traffic. You want to minimize costs and the migration effort for this application. What should you do?
Options
15 comments in the community discussion
2
B . Firestore and Spanner are expensive or need app changes, pretty sure D is a trap since it's more admin effort.
Its B, but only if there’s no weird PostgreSQL extensions in use that Cloud SQL can’t support.
Q: 5
You want to migrate an on-premises mission-critical PostgreSQL database to Cloud SQL. The database must be able to withstand a zonal failure with less than five minutes of downtime and still not lose any transactions. You want to follow Google-recommended practices for the migration. What should you do?
Options
16 comments in the community discussion
2
D pretty sure. HA makes the instance regional so zonal failures are handled, matches the RTO requirement.
2
D. but notice that if this was about cross-region resiliency (not just zonal), you'd have to go deeper than HA alone. For zonal failure and <5m downtime though, HA covers it per Google docs.
Q: 6
Your company is evaluating Google Cloud database options for a mission-critical global payments gateway application. The application must be available 24/7 to users worldwide, horizontally scalable, and support open source databases. You need to select an automatically shardable, fully managed database with 99.999% availability and strong transactional consistency. What should you do?
Options
13 comments in the community discussion
2
Honestly, Google keeps pushing Spanner but I always think Cloud SQL could handle these if you pick the right engine and size it up. My choice is B. It claims high availability and supports open source DBs like Postgres and MySQL, so seems workable for most global apps. Maybe I overlook the auto sharding though, not sur
1
D imo, Cloud Spanner is the only one here with global scaling, auto-sharding and that strict 99.999% SLA plus strong consistency. The others either can't hit those uptime guarantees or aren't natively globally distributed. Unless "open source" meant strict MySQL/Postgres required, D's the one. Disagree?
Q: 7
Your team is running a Cloud SQL for MySQL instance with a 5 TB database that must be available 24/7. You need to save database backups on object storage with minimal operational overhead or risk to your production workloads. What should you do?
Options
17 comments in the community discussion
1
I'm not convinced by B or C here. Those both add steps and could still hit performance, especially with a huge 5TB DB. Serverless exports (A) are designed to avoid production impact and automate the job, which matches minimal ops overhead. I'm pretty sure that's the intent, since D is a classic trap for high load ca
1
I don't think it's D, that's more manual and can load the prod instance. A avoids that risk and automates the job.
Q: 8
You are designing a new gaming application that uses a highly transactional relational database to store player authentication and inventory data in Google Cloud. You want to launch the game in multiple regions. What should you do?
Options
18 comments in the community discussion
2
D since Cloud SQL with regional read replica could work for multi-region, pretty sure it's a trap because it isn't truly global transactional but seems plausible if you don't catch the consistency detail.
1
For me, A for this one, since Cloud Spanner is the only option that gives true global consistency and handles high transactions. D looks close but only covers regional, so it's a bit of a trick. Anyone see it differently?
Q: 9
You are the DBA of your organization. You provided a cloned instance from the production Cloud SQL for PostSQL database to the developers for testing purposes. After the creation of the clone. Your developers notice missing data in one of the recently altered tables. What should you do to ensure that all data in included?
Options
18 comments in the community discussion
1
C
1
Had something like this in a mock, C fits best. PITR will include all changes up to a specific point, so any recent alters or missing data should be covered. Dumps can miss new data if not timed right. Pretty sure C is what they want here, but open if someone spots a detail I missed.
Q: 10
You have a non-critical business application running on Google Kubernetes Engine (GKE) in the app- dev VPC. You have created an AllayDB cluster with private Service Access (PSA) and no public IP address in the db-dev VPC. You want your application to securely connect to AllowDB in a cost- effective way. What should you do?
Options
15 comments in the community discussion
5
Option B fits since the app is non-critical and PSA already provides secure path, so direct private IP avoids extra cost or setup. If the VPCs weren’t peered, that’d change the answer. Anybody else disagree?
1
Maybe B. is the way for cost-effective and secure since proxies add needless complexity here. D is kind of a trap.
Q: 11
Your organization is currently updating an existing corporate application that is running in another public cloud to access managed database services in Google Cloud. The application will remain in the other public cloud while the database is migrated to Google Cloud. You want to follow Google- recommended practices for authentication. You need to minimize user disruption during the migration. What should you do?
Options
4 comments in the community discussion
1
Its A, workload identity federation lets you securely connect the app from another cloud without messing with user passwords. B and D would force password changes or syncs, which Google doesn't recommend. C isn't needed if the app isn't moving yet.
A not D. D is a trap because Google Workspace Password Sync is for syncing user passwords, which isn't what managed service access from another cloud needs. A fits Google's own advice if you're keeping the app external.
Q: 12
You host an application in Google Cloud. The application is located in a single region and uses Cloud SQL for transactional dat a. Most of your users are located in the same time zone and expect the application to be available 7 days a week, from 6 AM to 10 PM. You want to ensure regular maintenance updates to your Cloud SQL instance without creating downtime for your users. What should you do?
Options
8 comments in the community discussion
1
Its A, not D. D (HA) helps for failovers but won’t avoid downtime for planned maintenance, while A sets a window with no users active.
1
I get why D looks good since HA setup helps, so I'd pick D for less risk of downtime.
Q: 13
Your company uses the Cloud SQL out-of-disk recommender to analyze the storage utilization trends of production databases over the last 30 days. Your database operations team uses these recommendations to proactively monitor storage utilization and implement corrective actions. You receive a recommendation that the instance is likely to run out of disk space. What should you do to address this storage alert?
Options
6 comments in the community discussion
1
C/D? If you actually need to keep the storage from running out, increasing capacity makes sense, but loading old data into another schema (D) could work if you’re archiving. Depends if archival is an option here.
1
Its C here. If Cloud SQL says you'll run out of disk, the usual fix is bumping up storage-either manually or with automatic storage increase turned on. The other options wouldn't really solve the urgent space issue. Pretty sure about this, but let me know if I'm missing something!
Q: 14
You recently launched a new product to the US market. You currently have two Bigtable clusters in one US region to serve all the traffic. Your marketing team is planning an immediate expansion to APAC. You need to roll out the regional expansion while implementing high availability according to Google-recommended practices. What should you do?
Options
6 comments in the community discussion
1
I think this is same as a common exam questions, on a practice exam. D
1
D fits since you get multi-zone HA in the US and two zones in APAC, which aligns with Google's best practices for Bigtable replication. Targeting 35% CPU is also the recommended guidance. Pretty sure it's D.
Q: 15
Your customer is running a MySQL database on-premises with read replicas. The nightly incremental backups are expensive and add maintenance overhead. You want to follow Google-recommended practices to migrate the database to Google Cloud, and you need to ensure minimal downtime. What should you do?
Options
8 comments in the community discussion
1
Its B in my opinion. Using mysqldump and importing into Cloud SQL seems easier and more straightforward, even though it might mean a bit more downtime. Maybe I'm missing something but that's how I've done smaller migrations before.
Not B, D. Live replication to Cloud SQL helps minimize downtime and Google's docs say this is preferred.
Q: 16
You are evaluating Cloud SQL for PostgreSQL as a possible destination for your on-premises PostgreSQL instances. Geography is becoming increasingly relevant to customer privacy worldwide. Your solution must support data residency requirements and include a strategy to: configure where data is stored control where the encryption keys are stored govern the access to data What should you do?
Options
7 comments in the community discussion
1
Option C. restricting app access based on user region, feels more direct for tough residency rules. D looks good but maybe overkill for just storage. Anyone else tripped up by that?
D . Had something like this in a mock and CMEK plus IAM gives you key management, access controls, and lets you specify data location. C is tempting but D covers all requirements more completely.
Q: 17
Your company is migrating all legacy applications to Google Cloud. All on-premises applications are using legacy Oracle 12c databases with Oracle Real Application Cluster (RAC) for high availability (HA) and Oracle Data Guard for disaster recovery. You need a solution that requires minimal code changes, provides the same high availability you have today on-premises, and supports a low latency network for migrated legacy applications. What should you do?
Options
7 comments in the community discussion
5
B , since Cloud SQL gives you managed HA and a standby option but it's not compatible with Oracle RAC. Minimal code change and same HA as on-prem means Bare Metal Solution (D) is better for full Oracle features, but the question’s pushing for managed options. Open to pushback if anyone knows more.
B
Q: 18
Your company is launching a new globally distributed application with strict requirements for low latency, strong consistency, zero downtime, and high availability (HA). You need to configure a scalable database solution to support anticipated rapid growth and optimal application performance. What should you do?
Options
5 comments in the community discussion
1
C imo. Spanner is the only option here that gives you both strong consistency and global distribution with HA and no downtime. A and B can't guarantee all these, D is more for analytics. Anyone disagree?
C imo. is the one you want. Spanner covers global scale with strong consistency and zero downtime, which matches the scenario best. Official exam guide and labs show Spanner as the go-to for strict HA like this. Correct me if I'm missing something.
Q: 19
You released a popular mobile game and are using a 50 TB Cloud Spanner instance to store game data in a PITR-enabled production environment. When you analyzed the game statistics, you realized that some players are exploiting a loophole to gather more points to get on the leaderboard. Another DBA accidentally ran an emergency bugfix script that corrupted some of the data in the production environment. You need to determine the extent of the data corruption and restore the production environment. What should you do? (Choose two.)
Options
11 comments in the community discussion
1
Nah, it's not D here. A and E are correct because backup/restore is for big corruption (A), while stale read/write (E) is best for smaller bits. Easy to mix up since D looks tempting, but pretty sure it's wrong.
Maybe A and E, but not totally sure since B seems close too. Just going with what matches the docs and the split by "extent of corruption."
Q: 20
Your company is developing a new global transactional application that must be ACID-compliant and have 99.999% availability. You are responsible for selecting the appropriate Google Cloud database to serve as a datastore for this new application. What should you do?
Options
2 comments in the community discussion
B vs C. Practice sets mention Spanner for global ACID stuff, but Cloud SQL is good too so not 100% sure.
A is wrong, B. Spanner gives you global ACID transactions and that super high availability. Saw similar wording in a practice set, this is spot on for clarity.
Question 1 of 20

Premium Access Includes

  • ✓Quiz Simulator
  • ✓Exam Mode
  • ✓Progress Tracking
  • ✓Question Saving
  • ✓Flash Cards
  • ✓Drag & Drops
  • ✓3 Months Access
  • ✓PDF Downloads
Get Premium Access

← Back to all Google exams & practice tests

Scroll to Top