Question 1

Your application uses Cloud SQL for MySQL. Your users run reports on data that relies on near-real time;

however, the additional analytics caused excessive load on the primary database. You created a read replica

for the analytics workloads, but now your users are complaining about the lag in data changes and that their

reports are still slow. You need to improve the report performance and shorten the lag in data replication

without making changes to the current reports. Which two approaches should you implement? (Choose two.)

Options :

A : Create secondary indexes on the replica.

B : Create additional read replicas, and partition your analytics users to use different read replicas.

C :

Disable replication on the read replica, and set the flag for parallel replication on the read replica. Re-enable replication and optimize performance by setting flags on the primary instance.

D :

Disable replication on the primary instance, and set the flag for parallel replication on the primary instance. Re-enable replication and optimize performance by setting flags on the read replica.

E :

Move your analytics workloads to BigQuery, and set up a streaming pipeline to move data and update BigQuery.

Answer: B,C

Question 2

Your company has PostgreSQL databases on-premises and on Amazon Web Services (AWS). You are

planning multiple database migrations to Cloud SQL in an effort to reduce costs and downtime. You want to

follow Google-recommended practices and use Google native data migration tools. You also want to closely

monitor the migrations as part of the cutover strategy. What should you do?

Options :

A : Use Database Migration Service to migrate all databases to Cloud SQL.

B :

Use Database Migration Service for one-time migrations, and use third-party or partner tools for change

data capture (CDC) style migrations.

C :

Use data replication tools and CDC tools to enable migration.

D :

Use a combination of Database Migration Service and partner tools to support the data migration

strategy.

Answer: A

Question 3

You want to migrate an on-premises mission-critical PostgreSQL database to Cloud SQL. The database must be able to withstand a zonal failure with less than five minutes of downtime and still not lose any transactions. You want to follow Google-recommended practices for the migration. What should you do?

Options :

A : Take nightly snapshots of the primary database instance, and restore them in a secondary zone.

B :

Build a change data capture (CDC) pipeline to read transactions from the primary instance, and replicate them to a secondary instance.

C : Create a read replica in another region, and promote the read replica if a failure occurs.

D : Enable high availability (HA) for the database to make it regional.

Answer: D

Question 4

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.)

Options :

A : Use Database Migration Service to migrate the databases to Cloud SQL.

B : Use a cross-region read replica to migrate the databases to Cloud SQL.

C : Use replication from an external server to migrate the databases to Cloud SQL.

D : Use an external read replica to migrate the databases to Cloud SQL.

E : Use a read replica to migrate the databases to Cloud SQL.

Answer: C,E

Question 5

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?

Options :

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.

Answer: B

Higher Test Marks with Free Online Professional-Cloud-Database-Engineer Exam Practice

Buying Options: