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?

• A.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.
• B.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.
• C.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.
• D.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.

Comment: *

Name: *

Email: *

Verification: *

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?

• A.Use Bigtable, and add nodes as necessary to achieve the required throughput.
• B.Use Memorystore for Memcached, and add nodes as necessary to achieve the required throughput.
• C.Use Firestore, and rely on automatic serverless scaling.
• D.Use Cloud SQL with read replicas for throughput.

Comment: *

Name: *

Email: *

Verification: *

You are configuring a brand new PostgreSQL database instance in Cloud SQL. Your application team wants to have an optimal and highly available environment with automatic failover to avoid any unplanned outage. What should you do?

• A.Create two read-write Cloud SQL instances in two different regions with a standby instance in another zone.
• B.Create one regional Cloud SQL instance with a read replica in another region.
• C.Create two read-write Cloud SQL instances in two different zones with a standby instance in another region.
• D.Create one regional Cloud SQL instance in one zone with a standby instance in another zone in the same region.

Comment: *

Name: *

Email: *

Verification: *

An analytics team needs to read data out of Cloud SQL for SQL Server and update a table in Cloud Spanner. You need to create a service account and grant least privilege access using predefined roles. What roles should you assign to the service account?

• A.roles/cloudsql.instanceUser and roles/spanner.databaseUser
• B.roles/cloudsql.client and roles/spanner.databaseReader
• C.roles/cloudsql.editor and roles/spanner.admin
• D.roles/cloudsql.viewer and roles/spanner.databaseUser

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *