PROFESSIONAL-CLOUD-DATABASE-ENGINEER Online Practice Questions and Answers

During an internal audit, you realized that one of your Cloud SQL for MySQL instances does not have high availability (HA) enabled. You want to follow Google-recommended practices to enable HA on your existing instance. What should you do?

A. Create a new Cloud SQL for MySQL instance, enable HA, and use the export and import option to migrate your data.

B. Create a new Cloud SQL for MySQL instance, enable HA, and use Cloud Data Fusion to migrate your data.

C. Use the gcloud instances patch command to update your existing Cloud SQL for MySQL instance.

D. Shut down your existing Cloud SQL for MySQL instance, and enable HA.

Your organization has hundreds of Cloud SQL for MySQL instances. You want to follow Google-recommended practices to optimize platform costs. What should you do?

A. Use Query Insights to identify idle instances.

B. Remove inactive user accounts.

C. Run the Recommender API to identify overprovisioned instances.

D. Build indexes on heavily accessed tables.

You want to migrate your PostgreSQL database from another cloud provider to Cloud SQL. You plan on using Database Migration Service and need to assess the impact of any known limitations. What should you do? (Choose two.)

A. Identify whether the database has over 512 tables.

B. Identify all tables that do not have a primary key.

C. Identity all tables that do not have at least one foreign key.

D. Identify whether the source database is encrypted using pgcrypto extension.

E. Identify whether the source database uses customer-managed encryption keys (CMEK).

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 follow Google- recommended practices to resolve and prevent these performance issues while avoiding any major refactoring. What should you do?

A. Use Cloud Spanner instead of Cloud SQL.

B. Increase the number of CPUs for your instance.

C. Increase the storage size for the instance.

D. Use many smaller Cloud SQL instances.

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?

A. Create 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.

B. Create 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.

C. Create 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.

D. Use 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.

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?

A. Migrate the existing database to Firestore.

B. Migrate the existing database to Cloud SQL for PostgreSQL.

C. Migrate the existing database to Cloud Spanner.

D. Migrate the existing database to PostgreSQL running on Compute Engine.

You are developing a new application on a VM that is on your corporate network. The application will use Java Database Connectivity (JDBC) to connect to Cloud SQL for PostgreSQL. Your Cloud SQL instance is configured with IP address 192.168.3.48, and SSL is disabled. You want to ensure that your application can access your database instance without requiring configuration changes to your database. What should you do?

A. Define a connection string using your Google username and password to point to the external (public) IP address of your Cloud SQL instance.

B. Define a connection string using a database username and password to point to the internal (private) IP address of your Cloud SQL instance.

C. Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the internal (private) IP address of your Cloud SQL instance.

D. Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the external (public) IP address of your Cloud SQL instance.

You work in the logistics department. Your data analysis team needs daily extracts from Cloud SQL for MySQL to train a machine learning model. The model will be used to optimize next-day routes. You need to export the data in CSV format. You want to follow Google-recommended practices. What should you do?

A. Use Cloud Scheduler to trigger a Cloud Function that will run a select * from table(s) query to call the cloudsql.instances.export API.

B. Use Cloud Scheduler to trigger a Cloud Function through Pub/Sub to call the cloudsql.instances.export API.

C. Use Cloud Composer to orchestrate an export by calling the cloudsql.instances.export API.

D. Use Cloud Composer to execute a select * from table(s) query and export results.

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.

You are running a transactional application on Cloud SQL for PostgreSQL in Google Cloud. The database is running in a high availability configuration within one region. You have encountered issues with data and want to restore to the last known pristine version of the database. What should you do?

A. Create a clone database from a read replica database, and restore the clone in the same region.

B. Create a clone database from a read replica database, and restore the clone into a different zone.

C. Use the Cloud SQL point-in-time recovery (PITR) feature. Restore the copy from two hours ago to a new database instance.

D. Use the Cloud SQL database import feature. Import last week's dump file from Cloud Storage.