Pass exam with Professional-Cloud-Database-Engineer Top Exam Collection for sure one-shot

Your company is developing a global ecommerce website on Google Cloud. Your development team is working on a shopping cart service that is durable and elastically scalable with live traffic.
Business disruptions from unplanned downtime are expected to be less than 5 minutes per month. In addition, the application needs to have very low latency writes. You need a data storage solution that has high write throughput and provides 99.99% uptime. What should you do?

• A. Use Bigtable for data storage.
• B. Use Memorystore for data storage.
• C. Use Cloud SQL for data storage.
• D. Use Cloud Spanner for data storage.

You want to migrate an on-premises MySQL database to Cloud SQL. The on-premises database currently has 16 cores and 64-GB of RAM and averages 75% CPU utilization to support an application with over 100.000 tables. You need to specify the most cost-effective machine size you need when migrating to Cloud SQL for MySQL. What should you do-

• A. Select a Cloud SQL for MySQL database with a machine configuration of 12 cores and 48-GB of RAM.
• B. Select a Cloud SQL for MySQL database with a machine configuration of 64 cores and 768-GB of RAM.
• C. Select a Cloud SQL for MySQL database with a machine configuration of 16 cores and 64-GB of RAM.
• D. Select a Cloud SQL for MySQL database with a machine configuration of 32 cores and 256-GB of RAM.

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. 1. Pause the on-premises applications.
  2. Use the mysqldump utility to dump the database content in compressed format.
  3. Run gsutil -m to move the dump file to Cloud Storage.
  4. Use the Cloud SQL for MySQL import option.
  5. After the import operation is complete, re-point the applications to the Cloud SQL for MySQL instance.
• B. 1 Pause the on-premises applications.
  2. Use the mysqldump utility to dump the database content in CSV format.
  3. Run gsutil -m to move the dump file to Cloud Storage.
  4. Use the Cloud SQL for MySQL import option.
  5. After the import operation is complete, re-point the applications to the Cloud SQL for MySQL instance.
• C. 1. Build a Cloud Data Fusion pipeline for each table to migrate data from the on-premises MySQL database to Cloud SQL for MySQL.
  2. Schedule downtime to run each Cloud Data Fusion pipeline.
  3. Verify that the migration was successful.
  4. Re-point the applications to the Cloud SQL for MySQL instance.
• D. 1. Use Database Migration Service to connect to your on-premises database, and choose continuous replication.
  2. After the on-premises database is migrated, promote the Cloud SQL for MySQL instance, and connect applications to your Cloud SQL instance.

You are migrating your on-premises Oracle database to Cloud SQL for PostgreSQL by using Database Migration Service. You observed one of your important production tables DML changes are not getting replicated on the target. All other tables are getting migrated to the target without any errors.
What could be the problem and what should you do to resolve it?

• A. The table is an index-organized table. Change it to a normal heap-organized table.
• B. Supplemental logging has not been enabled for the database. Enable supplemental logging.
• C. The table has a column of type NCLOB. Drop the column.
• D. The Oracle table does not have a primary key created. Create a primary key on the table.

Your team is building a new inventory management application that will require read and write database instances in multiple Google Cloud regions around the globe. Your database solution requires 99.99% availability and global transactional consistency. You need a fully managed backend relational database to store inventory changes. What should you do?

• A. Use Cloud Spanner.
• B. Use Cloud SQL for MySQL
• C. Use Firestore.
• D. Use Bigtable.