CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Google
  5. PROFESSIONAL-CLOUD-DATABASE-ENGINEER

Free PROFESSIONAL-CLOUD-DATABASE-ENGINEER Exam Braindumps (page: 8)

Page 8 of 34
PDF with 132 Questions

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?

  1. 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.
  2. 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.
  3. 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.
  4. 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(s): B

Explanation:

https://cloud.google.com/datastream/docs/overview.



Your company uses the Cloud SQL out-of-disk recommender to analyze the storage utilization trends of production databases over the last 30 days. Your database operations team uses these recommendations to proactively monitor storage utilization and implement corrective actions. You receive a recommendation that the instance is likely to run out of disk space.
What should you do to address this storage alert?

  1. Normalize the database to the third normal form.
  2. Compress the data using a different compression algorithm.
  3. Manually or automatically increase the storage capacity.
  4. Create another schema to load older data.

Answer(s): C

Explanation:

https://cloud.google.com/sql/docs/mysql/instance-settings#storage-capacity-2ndgen



You are managing a mission-critical Cloud SQL for PostgreSQL instance. Your application team is running important transactions on the database when another DBA starts an on-demand backup. You want to verify the status of the backup.
What should you do?

  1. Check the cloudsql.googleapis.com/postgres.log instance log.
  2. Perform the gcloud sql operations list command.
  3. Use Cloud Audit Logs to verify the status.
  4. Use the Google Cloud Console.

Answer(s): B

Explanation:

https://cloud.google.com/sql/docs/postgres/backup-recovery/backups#troubleshooting-backups Under Troubleshooting: Issue: "You can't see the current operation's status." The Google Cloud console reports only success or failure when the operation is done. It isn't designed to show warnings or other updates. Run the gcloud sql operations list command to list all operations for the given Cloud SQL instance.



You support a consumer inventory application that runs on a multi-region instance of Cloud Spanner. A customer opened a support ticket to complain about slow response times. You notice a Cloud Monitoring alert about high CPU utilization. You want to follow Google-recommended practices to address the CPU performance issue.
What should you do first?

  1. Increase the number of processing units.
  2. Modify the database schema, and add additional indexes.
  3. Shard data required by the application into multiple instances.
  4. Decrease the number of processing units.

Answer(s): A

Explanation:

In case of high CPU utilization like, mentioned in question, refer:
https://cloud.google.com/spanner/docs/identify-latency- point#:~:text=Check%20the%20CPU%20utilization%20of%20the%20instance.%20If%20the%20CPU%

20utilization%20of%20the%20instance%20is%20above%20the%20recommended%20level%2C%20y ou%20should%20manually%20add%20more%20nodes%2C%20or%20set%20up%20auto%20scaling. "Check the CPU utilization of the instance. If the CPU utilization of the instance is above the recommended level, you should manually add more nodes, or set up auto scaling." Indexes and schema are reviewed post identifying query with slow performance. Refer :
https://cloud.google.com/spanner/docs/troubleshooting-performance-regressions#review-schema



Page 8 of 34



Post your Comments and Discuss Google PROFESSIONAL-CLOUD-DATABASE-ENGINEER exam with other Community members:

muksgreen commented on March 01, 2024
brainstorming excellent
JAPAN
upvote