Important Google Professional Cloud Database Engineer Exam Questions

CertPrep • Google • Professional Cloud Database Engineer Exam Questions

Select Certification Providers

Select Certification Exam

Get Full Version

Google Professional Cloud Database Engineer Exam

Attempt the Google Cloud Certified practice test and solve real exam-like Professional Cloud Database Engineer questions to prepare efficiently and increase your chances of success. Our Google Professional Cloud Database Engineer practice questions match the actual Professional Cloud Database Engineer exam format, helping you enhance confidence and improve performance. With our Professional Cloud Database Engineer practice exam software, you can analyze your performance, identify weak areas, and work on them effectively to boost your final Google Cloud Certified exam score.

Vendor:	Google
Exam Name:	Professional Cloud Database Engineer
Registration Code:	Professional-Cloud-Database-Engineer
Related Certification:	Google Cloud Certified Certification
Exam Audience:	Database Engineers, Cloud Architects, and Data Professionals,

Total Questions

141

Last Updated

23-05-2026

Exam Duration

240 MINUTES

Upgrade to Premium

GET FULL PDF

Question: 1

You are managing a Cloud SQL for PostgreSQL instance in Google Cloud. You need to test the high availability of your Cloud SQL instance by performing a failover. You want to use the cloud command.

What should you do?

AUse gcloud sql instances failover <PrimaryInstanceName>.

BUse gcloud sql instances failover <ReplicaInstanceName>.

CUse gcloud sql instances promote-replica <PrimaryInstanceName>.

DUse gcloud sql instances promote-replica <ReplicaInstanceName>.

Answer: A

Question: 2

Your company is shutting down their data center and migrating several MySQL and PostgreSQL databases to Google Cloud. Your database operations team is severely constrained by ongoing production releases and the lack of capacity for additional on-premises backups. You want to ensure that the scheduled migrations happen with minimal downtime and that the Google Cloud databases stay in sync with the on-premises data changes until the applications can cut over.

What should you do? (Choose two.)

AUse an external read replica to migrate the databases to Cloud SQL.

BUse a read replica to migrate the databases to Cloud SQL.

CUse Database Migration Service to migrate the databases to Cloud SQL.

DUse a cross-region read replica to migrate the databases to Cloud SQL.

EUse replication from an external server to migrate the databases to Cloud SQL.

Answer: C, E

Question: 3

You are writing an application that will run on Cloud Run and require a database running in the Cloud SQL managed service. You want to secure this instance so that it only receives connections from applications running in your VPC environment in Google Cloud. What should you do?

A1. Create your instance with a specified external (public) IP address.
2. Choose the VPC and create firewall rules to allow only connections from Cloud Run into your instance.
3. Use Cloud SQL Auth proxy to connect to the instance.

B1. Create your instance with a specified external (public) IP address.
2. Choose the VPC and create firewall rules to allow only connections from Cloud Run into your instance.
3. Connect to the instance using a connection pool to best manage connections to the instance.

C1. Create your instance with a specified internal (private) IP address.
2. Choose the VPC with private service connection configured.
3. Configure the Serverless VPC Access connector in the same VPC network as your Cloud SQL instance.
4. Use Cloud SQL Auth proxy to connect to the instance.

D1. Create your instance with a specified internal (private) IP address.
2. Choose the VPC with private service connection configured.
3. Configure the Serverless VPC Access connector in the same VPC network as your Cloud SQL instance.
4. Connect to the instance using a connection pool to best manage connections to the instance.

Answer: D

Explanation:

https://cloud.google.com/sql/docs/mysql/connect-run#configure https://cloud.google.com/sql/docs/mysql/connect-run#connection-pools

Question: 4

Your company is migrating the existing infrastructure for a highly transactional application to Google Cloud. You have several databases in a MySQL database instance and need to decide how to transfer the data to Cloud SQL. You need to minimize the downtime for the migration of your 500 GB instance. What should you do?

ACreate a Cloud SQL for MySQL instance for your databases, and configure Datastream to stream your database changes to Cloud SQL.
Select the Backfill historical data check box on your stream configuration to initiate Datastream to backfill any data that is out of sync between the source and destination.
Delete your stream when all changes are moved to Cloud SQL for MySQL, and update your application to use the new instance.

BCreate migration job using Database Migration Service.
Set the migration job type to Continuous, and allow the databases to complete the full dump phase and start sending data in change data capture (CDC) mode.
Wait for the replication delay to minimize, initiate a promotion of the new Cloud SQL instance, and wait for the migration job to complete.
Update your application connections to the new instance.

CCreate migration job using Database Migration Service.
Set the migration job type to One-time, and perform this migration during a maintenance window.
Stop all write workloads to the source database and initiate the dump. Wait for the dump to be loaded into the Cloud SQL destination database and the destination database to be promoted to the primary database.
Update your application connections to the new instance.

DUse the mysqldump utility to manually initiate a backup of MySQL during the application maintenance window.
Move the files to Cloud Storage, and import each database into your Cloud SQL instance.
Continue to dump each database until all the databases are migrated.
Update your application connections to the new instance.

Answer: B

Explanation:

https://cloud.google.com/datastream/docs/overview.

Question: 5

Your company uses Cloud Spanner for a mission-critical inventory management system that is globally available. You recently loaded stock keeping unit (SKU) and product catalog data from a company acquisition and observed hot-spots in the Cloud Spanner database. You want to follow Google-recommended schema design practices to avoid performance degradation. What should you do? (Choose two.)

AUse an auto-incrementing value as the primary key.

BNormalize the data model.

CPromote low-cardinality attributes in multi-attribute primary keys.

DPromote high-cardinality attributes in multi-attribute primary keys.

EUse bit-reverse sequential value as the primary key.

Answer: D, E

Explanation:

https://cloud.google.com/spanner/docs/schema-design D because high cardinality means you have more unique values in the collumn. That's a good thing for a hot-spotting issue. E because Spanner specifically has this feature to reduce hot spotting. Basically, it generates unique values https://cloud.google.com/spanner/docs/schema-design#bit_reverse_primary_key

D . Promote high-cardinality attributes in multi-attribute primary keys.

This is a correct answer because promoting high-cardinality attributes in multi-attribute primary keys can help avoid hotspots in Cloud Spanner.High-cardinality attributes are those that have many distinct values, such as UUIDs, email addresses, or timestamps1.By placing high-cardinality attributes first in the primary key, you can ensure that the rows are distributed more evenly across the key space, and avoid having too many requests sent to the same server2.

E . Use bit-reverse sequential value as the primary key.

SAVE TIME & QUICKLY PREPARE WITH REAL QUESTIONS