Professional-Cloud-Database-Engineer 試験問題を無料オンラインアクセス

You plan to use Database Migration Service to migrate data from a PostgreSQL on-premises instance to Cloud SQL. You need to identify the prerequisites for creating and automating the task. What should you do? (Choose two.)

• A.Ensure that pglogical is installed on the source PostgreSQL database.
• B.Disable all foreign key constraints on the source PostgreSQL database.
• C.Shut down the database before the Data Migration Service task is started.
• D.Ensure that all PostgreSQL tables have a primary key.
• E.Drop or disable all users except database administration users.

You are configuring a new application that has access to an existing Cloud Spanner database.
The new application reads from this database to gather statistics for a dashboard. You want to follow Google-recommended practices when granting Identity and Access Management (IAM) permissions. What should you do?

• A.Create a new service account, and grant it the spanner.databases.select permission.
• B.Create a new service account, and grant it the Cloud Spanner Database Reader role.
• C.Create a new service account, and grant it the Cloud Spanner Database Admin role.
• D.Reuse the existing service account that populates this database.

You are migrating your 2 TB on-premises PostgreSQL cluster to Compute Engine. You want to set up your new environment in an Ubuntu virtual machine instance in Google Cloud and seed the data to a new instance. You need to plan your database migration to ensure minimum downtime. What should you do?

• A.1. Take a full export while the database is offline.
  2. Create a bucket in Cloud Storage.
  3. Transfer the dump file to the bucket you just created.
  4. Import the dump file into the Google Cloud primary server.
• B.1. Take a full backup while the database is online.
  2. Create a bucket in Cloud Storage.
  3. Transfer the backup to the bucket you just created.
  4. Restore the backup into the Google Cloud primary server.
  5. Create a recovery.conf file in the $PG_DATA directory.
  6. Stop the source database.
  7. Transfer the write ahead logs to the bucket you created before.
  8. Start the PostgreSQL service.
  9. Wait until Google Cloud primary server syncs with the running primary server.
• C.1. Take a full export while the database is offline.
  2. Create a bucket in Cloud Storage.
  3. Transfer the dump file to the bucket you just created.
  4. Restore the backup into the Google Cloud primary server.
• D.1. Take a full export while the database is online.
  2. Create a bucket in Cloud Storage.
  3. Transfer the dump file and write-ahead logs to the bucket you just created.
  4. Restore the dump file into the Google Cloud primary server.
  5. Create a recovery.conf file in the $PG_DATA directory.
  6. Stop the source database.
  7. Transfer the write-ahead logs to the bucket you created before.
  8. Start the PostgreSQL service.
  9. Wait until the Google Cloud primary server syncs with the running primary server.

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.1. Create migration job using Database Migration Service.
  2. Set the migration job type to One-time, and perform this migration during a maintenance window.
  3. 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.
  4. Update your application connections to the new instance.
• B.1. Use the mysqldump utility to manually initiate a backup of MySQL during the application maintenance window.
  2. Move the files to Cloud Storage, and import each database into your Cloud SQL instance.
  3. Continue to dump each database until all the databases are migrated.
  4. Update your application connections to the new instance.
• C.1. Create migration job using Database Migration Service.
  2. 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.
  3. Wait for the replication delay to minimize, initiate a promotion of the new Cloud SQL instance, and wait for the migration job to complete.
  4. Update your application connections to the new instance.
• D.1. Create a Cloud SQL for MySQL instance for your databases, and configure Datastream to stream your database changes to Cloud SQL.
  2. 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.
  3. Delete your stream when all changes are moved to Cloud SQL for MySQL, and update your application to use the new instance.

When comparing Google Cloud managed NoSQL services, which cost component should you consistently emphasize for a precise TCO analysis?

• A.Query execution and index upkeep costs
• B.CMEK for data at rest
• C.Storage capacity costs