Google Professional-Cloud-Database-Engineer Exam Questions Free Practice Test

Viewing page 1 out of 5 pages

Viewing questions 1-10 out of questions

Questions # 1:

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:

Use Cloud SQL serverless exports.

Create a read replica, and then use the mysqldump utility to export each table.

Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.

Use the mysqldump utility on the primary database instance to export the backup.

Questions # 2:

You are a DBA on a Cloud Spanner instance with multiple databases. You need to assign these privileges to all members of the application development team on a specific database:

Can read tables, views, and DDL

Can write rows to the tables

Can add columns and indexes

Cannot drop the database

What should you do?

Options:

Assign the Cloud Spanner Database Reader and Cloud Spanner Backup Writer roles.

Assign the Cloud Spanner Database Admin role.

Assign the Cloud Spanner Database User role.

Assign the Cloud Spanner Admin role.

Questions # 3:

You use Python scripts to generate weekly SQL reports to assess the state of your databases and determine whether you need to reorganize tables or run statistics. You want to automate this report but need to minimize operational costs and overhead. What should you do?

Options:

Create a VM in Compute Engine, and run a cron job.

Create a Cloud Composer instance, and create a directed acyclic graph (DAG).

Create a Cloud Function, and call the Cloud Function using Cloud Scheduler.

Create a Cloud Function, and call the Cloud Function from a Cloud Tasks queue.

Questions # 4:

You currently have a MySQL database running on Cloud SQL with a read replica in a different zone for non-mission critical analytics workloads. You want to enable high availability (HA) for the analytic workloads while keeping costs low. What should you do?

Options:

Increase the size of the read replica Instance and enable MA.

Enable HA on the current read replica.

Create a new HA instance in the same zone db lie primary.

Create a new MA Instance in a different region than the primary.

Questions # 5:

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?

Options:

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.

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.

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.

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.

Questions # 6:

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:

Create a Google Kubernetes Engine (GKE) cluster, install MySQL on the cluster, and then import the dump file.

Use the mysqldump utility to take a backup of the existing on-premises database, and then import it into Cloud SQL.

Create a Compute Engine VM, install MySQL on the VM, and then import the dump file.

Create an external replica, and use Cloud SQL to synchronize the data to the replica.

Questions # 7:

Your application follows a microservices architecture and uses a single large Cloud SQL instance, which is starting to have performance issues as your application grows. in the Cloud Monitoring dashboard, the CPU utilization looks normal You want to followGoogle-recommended practices to resolve and prevent these performance issues while avoiding any major refactoring. What should you do?

Options:

Use Cloud Spanner instead of Cloud SQL.

Increase the number of CPUs for your instance.

Increase the storage size for the instance.

Use many smaller Cloud SQL instances.

Questions # 8:

You need to redesign the architecture of an application that currently uses Cloud SQL for PostgreSQL. The users of the application complain about slow query response times. You want to enhance your application architecture to offer sub-millisecond query latency. What should you do?

Options:

Configure Firestore, and modify your application to offload queries.

Configure Bigtable, and modify your application to offload queries.

Configure Cloud SQL for PostgreSQL read replicas to offload queries.

Configure Memorystore, and modify your application to offload queries.

Questions # 9:

Your organization needs to migrate a critical, on-premises MySQL database to Cloud SQL for MySQL. The on-premises database is on a version of MySQL that is supported by Cloud SQL and uses the InnoDB storage engine. You need to migrate the database while preserving transactions and minimizing downtime. What should you do?

Options:

Use Database Migration Service to connect to your on-premises database, and choose continuous replication.

After the on-premises database is migrated, promote the Cloud SQL for MySQL instance, and connect applications to your Cloud SQL instance.

Build a Cloud Data Fusion pipeline for each table to migrate data from the on-premises MySQL database to Cloud SQL for MySQL.

Schedule downtime to run each Cloud Data Fusion pipeline.

Verify that the migration was successful.

Re-point the applications to the Cloud SQL for MySQL instance.

Pause the on-premises applications.

Use the mysqldump utility to dump the database content in compressed format.

Run gsutil –m to move the dump file to Cloud Storage.

Use the Cloud SQL for MySQL import option.

After the import operation is complete, re-point the applications to the Cloud SQL for MySQL instance.

Pause the on-premises applications.

Use the mysqldump utility to dump the database content in CSV format.

Run gsutil –m to move the dump file to Cloud Storage.

Use the Cloud SQL for MySQL import option.

After the import operation is complete, re-point the applications to the Cloud SQL for MySQL instance.

Questions # 10:

You need to issue a new server certificate because your old one is expiring. You need to avoid a restart of your Cloud SQL for MySQL instance. What should you do in your Cloud SQL instance?

Pass the Google Cloud Database Engineer Professional-Cloud-Database-Engineer Questions and answers with CertsForce