Google PROFESSIONAL-CLOUD-DATABASE-ENGINEER Online Practice Questions and Exam Preparation

Google PROFESSIONAL-CLOUD-DATABASE-ENGINEER Online Questions & Answers

• Question 91:

  You want to migrate your on-premises PostgreSQL database to Compute Engine. You need to migrate this database with the minimum downtime possible. What should you do?

  A. Perform a full backup of your on-premises PostgreSQL, and then, in the migration window, perform an incremental backup.
  B. Create a read replica on Cloud SQL, and then promote it to a read/write standalone instance.
  C. Use Database Migration Service to migrate your database.
  D. Create a hot standby on Compute Engine, and use PgBouncer to switch over the connections.
  D. Create a hot standby on Compute Engine, and use PgBouncer to switch over the connections.

  ---

  Explanation/Reference:

  PgBouncer maintains a pool for connections for each database and user combination. PgBouncer either creates a new database connection for a client or reuses an existing connection for the same user and database. + PgBouncer is a simple PostgreSQL connection pool that allows for several thousand connections at a time. Using Kubernetes Engine to run a Helm Chart w/ PgBouncer based on the great article from futuretech-industries, we were able to set up an easily deployable system to get the most out of our CloudSQL DBs without breaking the bank. https://medium.com/google-cloud/increasing-cloud-sql-postgresql-max-connections-w-pgbouncer-kubernetes-engine-49b0b2894820#:~:text=That%20is %20where,breaking%20the%20bank.

• Question 92:

  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?

  A. Use query parameters to speed up frequently executed queries.
  B. Change the Cloud Spanner configuration from multi-region to single region.
  C. Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables.
  D. Use SQL statements to analyze SPANNER_SYS.QUERY_STATS* tables.
  C. Use SQL statements to analyze SPANNER_SYS.READ_STATS* tables.

  ---

  Explanation/Reference:

  To troubleshoot high read latency, you can use SQL statements to analyze the SPANNER_SYS.READ_STATS* tables. These tables contain statistics about read operations in Cloud Spanner, including the number of reads, read latency, and the number of read errors. By analyzing these tables, you can identify the cause of the high read latency and take appropriate action to resolve the issue. Other options, such as using query parameters to speed up frequently executed queries or changing the Cloud Spanner configuration from multi-region to single region, may not be directly related to the issue of high read latency. Similarly, analyzing the SPANNER_SYS.QUERY_STATS* tables, which contain statistics about query operations, may not be relevant to the issue of high read latency.

• Question 93:

  You need to migrate a 1 TB PostgreSQL database from a Compute Engine VM to Cloud SQL for PostgreSQL. You want to ensure that there is minimal downtime during the migration. What should you do?

  A. Export the data from the existing database, and load the data into a new Cloud SQL database.
  B. Use Migrate for Compute Engine to complete the migration.
  C. Use Datastream to complete the migration.
  D. Use Database Migration Service to complete the migration.
  D. Use Database Migration Service to complete the migration.

  ---

  Explanation/Reference:

  https://www.cloudskillsboost.google/focuses/22792?parent=catalog

• Question 94:

  You are running a mission-critical application on a Cloud SQL for PostgreSQL database with a multi-zonal setup. The primary and read replica instances are in the same region but in different zones. You need to ensure that you split the application load between both instances. What should you do?

  A. Use Cloud Load Balancing for load balancing between the Cloud SQL primary and read replica instances.
  B. Use PgBouncer to set up database connection pooling between the Cloud SQL primary and read replica instances.
  C. Use HTTP(S) Load Balancing for database connection pooling between the Cloud SQL primary and read replica instances.
  D. Use the Cloud SQL Auth proxy for database connection pooling between the Cloud SQL primary and read replica instances.
  B. Use PgBouncer to set up database connection pooling between the Cloud SQL primary and read replica instances.

  ---

  Explanation/Reference:

  https://severalnines.com/blog/how-achieve-postgresql-high-availability-pgbouncer/ https://cloud.google.com/blog/products/databases/using-haproxy-to-scale-read-only-workloads-on-cloud-sql-for-postgresql This answer is correct because PgBouncer is a lightweight connection pooler for PostgreSQL that can help you distribute read requests between the Cloud SQL primary and read replica instances1. PgBouncer can also improve performance and scalability by reducing the overhead of creating new connections and reusing existing ones1. You can install PgBouncer on a Compute Engine instance and configure it to connect to the Cloud SQL instances using private IP addresses or the Cloud SQL Auth proxy2.

• Question 95:

  You are migrating a telehealth care company's on-premises data center to Google Cloud. The migration plan specifies:

  PostgreSQL databases must be migrated to a multi-region backup configuration with cross-region replicas to allow restore and failover in multiple scenarios.

  MySQL databases handle personally identifiable information (PII) and require data residency compliance at the regional level.

  You want to set up the environment with minimal administrative effort. What should you do?

  A. Set up Cloud Logging and Cloud Monitoring with Cloud Functions to send an alert every time a new database instance is created, and manually validate the region.
  B. Set up different organizations for each database type, and apply policy constraints at the organization level.
  C. Set up Pub/Sub to ingest data from Cloud Logging, send an alert every time a new database instance is created, and manually validate the region.
  D. Set up different projects for PostgreSQL and MySQL databases, and apply organizational policy constraints at a project level.
  D. Set up different projects for PostgreSQL and MySQL databases, and apply organizational policy constraints at a project level.

  ---

  Explanation/Reference:

• Question 96:

  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?

  A. Use Cloud SQL serverless exports.
  B. Create a read replica, and then use the mysqldump utility to export each table.
  C. Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
  D. Use the mysqldump utility on the primary database instance to export the backup.
  A. Use Cloud SQL serverless exports.

  ---

  Explanation/Reference:

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

• Question 97:

  You need to provision several hundred Cloud SQL for MySQL instances for multiple project teams over a one-week period. You must ensure that all instances adhere to company standards such as instance naming conventions, database flags, and tags. What should you do?

  A. Automate instance creation by writing a Dataflow job.
  B. Automate instance creation by setting up Terraform scripts.
  C. Create the instances using the Google Cloud Console UI.
  D. Create clones from a template Cloud SQL instance.
  B. Automate instance creation by setting up Terraform scripts.

• Question 98:

  Your digital-native business runs its database workloads on Cloud SQL. Your website must be globally accessible 24/7. You need to prepare your Cloud SQL instance for high availability (HA). You want to follow Google-recommended practices. What should you do? (Choose two.)

  A. Set up manual backups.
  B. Create a PostgreSQL database on-premises as the HA option.
  C. Configure single zone availability for automated backups.
  D. Enable point-in-time recovery.
  E. Schedule automated backups.
  D. Enable point-in-time recovery.
  E. Schedule automated backups.

  ---

  Explanation/Reference:

  D. Enable point-in-time recovery -This feature allows you to restore your database to a specific point in time. It helps protect against data loss and can be used in the event of data corruption or accidental data deletion. E. Schedule automated backups -Automated backups allow you to take regular backups of your database without manual intervention. You can use these backups to restore your database in the event of data loss or corruption.

• Question 99:

  Your organization has a production Cloud SQL for MySQL instance. Your instance is configured with 16 vCPUs and 104 GB of RAM that is running between 90% and 100% CPU utilization for most of the day. You need to scale up the database and add vCPUs with minimal interruption and effort. What should you do?

  A. Issue a gcloud sql instances patch command to increase the number of vCPUs.
  B. Update a MySQL database flag to increase the number of vCPUs.
  C. Issue a gcloud compute instances update command to increase the number of vCPUs.
  D. Back up the database, create an instance with additional vCPUs, and restore the database.
  A. Issue a gcloud sql instances patch command to increase the number of vCPUs.

  ---

  Explanation/Reference:

  https://cloud.google.com/sdk/gcloud/reference/sql/instances/patch

• Question 100:

  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?

  A. Create a Google Kubernetes Engine (GKE) cluster, install MySQL on the cluster, and then import the dump file.
  B. Use the mysqldump utility to take a backup of the existing on-premises database, and then import it into Cloud SQL.
  C. Create a Compute Engine VM, install MySQL on the VM, and then import the dump file.
  D. Create an external replica, and use Cloud SQL to synchronize the data to the replica.
  D. Create an external replica, and use Cloud SQL to synchronize the data to the replica.

  ---

  Explanation/Reference:

  https://cloud.google.com/sql/docs/mysql/replication/configure-replication-from-external