Free PROFESSIONAL CLOUD DATABASE ENGINEER Exam Braindumps
Professional Cloud Database Engineer Questions 46–50 (page: 11)

Updated On: 10-Feb-2026

You are choosing a database backend for a new application. The application will ingest data points from IoT sensors. You need to ensure that the application can scale up to millions of requests per second with sub-10ms latency and store up to 100 TB of history.
What should you do?

  1. Use Cloud SQL with read replicas for throughput.
  2. Use Firestore, and rely on automatic serverless scaling.
  3. Use Memorystore for Memcached, and add nodes as necessary to achieve the required throughput.
  4. Use Bigtable, and add nodes as necessary to achieve the required throughput.

Answer(s): D

Explanation:

https://cloud.google.com/memorystore/docs/redis/redis-overview



You are designing a payments processing application on Google Cloud. The application must continue to serve requests and avoid any user disruption if a regional failure occurs. You need to use AES-256 to encrypt data in the database, and you want to control where you store the encryption key.
What should you do?

  1. Use Cloud Spanner with a customer-managed encryption key (CMEK).
  2. Use Cloud Spanner with default encryption.
  3. Use Cloud SQL with a customer-managed encryption key (CMEK).
  4. Use Bigtable with default encryption.

Answer(s): A

Explanation:

Yes default encryption comes with AES-256 but the question states that you need to control where you store the encryption keys. that can be achieved by CMEK.



You are managing a Cloud SQL for MySQL environment in Google Cloud. You have deployed a primary instance in Zone A and a read replica instance in Zone B, both in the same region. You are notified that the replica instance in Zone B was unavailable for 10 minutes. You need to ensure that the read replica instance is still working.
What should you do?

  1. Use the Google Cloud Console or gcloud CLI to manually create a new clone database.
  2. Use the Google Cloud Console or gcloud CLI to manually create a new failover replica from backup.
  3. Verify that the new replica is created automatically.
  4. Start the original primary instance and resume replication.

Answer(s): C

Explanation:

Recovery Process: Once Zone-B becomes available again, Cloud SQL will initiate the recovery process for the impacted read replica. The recovery process involves the following steps: 1. Synchronization:
Cloud SQL will compare the data in the recovered read replica with the primary instance in Zone-A. If there is any data divergence due to the unavailability period, Cloud SQL will synchronize the read replica with the primary instance to ensure data consistency. 2. Catch-up Replication: The recovered read replica will start catching up on the changes that occurred on the primary instance during its unavailability. It will apply the necessary updates from the primary instance's binary logs (binlogs) to bring the replica up to date. 3. Resuming Read Traffic: Once the synchronization and catch-up replication processes are complete, the read replica in Zone-B will resume its normal operation. It will be able to serve read traffic and stay updated with subsequent changes from the primary instance.



You are migrating an on-premises application to Google Cloud. The application requires a high availability (HA) PostgreSQL database to support business-critical functions. Your company's disaster recovery strategy requires a recovery time objective (RTO) and recovery point objective (RPO) within 30 minutes of failure. You plan to use a Google Cloud managed service.
What should you do to maximize uptime for your application?

  1. Deploy Cloud SQL for PostgreSQL in a regional configuration. Create a read replica in a different zone in the same region and a read replica in another region for disaster recovery.
  2. Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Take periodic backups, and use this backup to restore to a new Cloud SQL for PostgreSQL instance in another region during a disaster recovery event.
  3. Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross- region read replica, and promote the read replica as the primary node for disaster recovery.
  4. Migrate the PostgreSQL database to multi-regional Cloud Spanner so that a single region outage will not affect your application. Update the schema to support Cloud Spanner data types, and refactor the application.

Answer(s): C

Explanation:

The best answer is deploy an HA configuration and have a read replica you could promote to the primary in a different region



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?

  1. Use Cloud SQL serverless exports.
  2. Create a read replica, and then use the mysqldump utility to export each table.
  3. Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
  4. Use the mysqldump utility on the primary database instance to export the backup.

Answer(s): A

Explanation:

https://cloud.google.com/blog/products/databases/introducing-cloud-sql-serverless-exports



Viewing page 11 of 28
Viewing questions 51 - 55 out of 197 questions


Post your Comments and Discuss Google PROFESSIONAL CLOUD DATABASE ENGINEER exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!