Professional-Cloud-Database-Engineer 무료 덤프문제 온라인 액세스

You are migrating your on-premises PostgreSQL database to Spanner. You need to identify a solution for handling existing integer-based table primary keys. You want minimal changes to the applications while also following Google-recommended practices. What should you do-

• A.Generate values by using BIT_REVERSED_POSITIVEsequences.
• B.Use a UUID function that generates UUID Version 4 values as primary keys.
• C.Update default primary key values to max(primary_key) + 1.
• D.Use application generated sequential integer values as primary keys.

Your e-learning platform runs on a Cloud SQL for PostgreSQL instance (16 VCPUs, 60 GB memory and 1TB SSD) serving users in North America. Your analytics team runs complex reporting queries that often consume 80% of CPU resources, causing slow response times for student transactions during peak hours. Current workload includes 8,000 transactions per second with 60% reads and 40% writes. The reporting queries involve JOIN operations across multiple large tables with millions of rows requiring highly efficient analytical processing. The platform also experiences sudden spikes in analytical reporting demand, requiring an elastic scaling of read capacity. You need to improve the query performance for your analytics team to run their reports efficiently without impacting transactional users. You also need to plan for future traffic growth.
What should you do-

• A.Migrate to AlloyDB for PostgreSQL with a 16 vCPU primary instance and enable columnar engine for analytical workloads, using read pools for query isolation.
• B.Upgrade the Cloud SQL for PostgreSQL instance to db-n1-highmem-32and implement connection pooling with PgBouncerto handle increased load.
• C.Migrate to AlloyDB for PostgreSQL and upgrade the machine type of the primary instance to 32 vCPU. Create materialized views for common analytical queries.
• D.Upgrade to Cloud SAL for PostgreSQL Enterprise Edition and route transaction and analytical queries to the primary instance.

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

Your organization has hundreds of Cloud SQL for MySQL instances. You want to follow Google- recommended practices to optimize platform costs. What should you do?

• A.Build indexes on heavily accessed tables.
• B.Remove inactive user accounts.
• C.Run the Recommender API to identify overprovisioned instances.
• D.Use Query Insights to identify idle instances.

Your organization has a production Cloud SQL for MySQL instance. Your instance is configured with 16 vCPUs and 104 GB of RAM that is running between 90% and 100% CPU utilization for most of the day. You need to scale up the database and add vCPUs with minimal interruption and effort. What should you do?

• A.Back up the database, create an instance with additional vCPUs, and restore the database.
• B.Issue a gcloud compute instances update command to increase the number of vCPUs.
• C.Update a MySQL database flag to increase the number of vCPUs.
• D.Issue a gcloud sql instances patch command to increase the number of vCPUs.