Professional-Cloud-Database-Engineer最も有効な質問と解答で勉強

You are running a transactional application on Cloud SQL for PostgreSQL in Google Cloud. The database is running in a high availability configuration within one region. You have encountered issues with data and want to restore to the last known pristine version of the database. What should you do?

• A. Create a clone database from a read replica database, and restore the clone in the same region.
• B. Use the Cloud SQL database import feature. Import last week's dump file from Cloud Storage.
• C. Use the Cloud SQL point-in-time recovery (PITR) feature. Restore the copy from two hours ago to a new database instance.
• D. Create a clone database from a read replica database, and restore the clone into a different zone.

Your Cloud SQL for PostgreSQL database supporting a financial application has been experiencing "deadlock detected" errors during end-of-month processing. You notice that CPU utilization spikes to 90% during these periods, and several long-running queries are consuming significant resources. You need to identify the specific queries causing the deadlocks and implement monitoring to solve similar issues before they cause application failures.
What should you do?

• A. Increase the deadlock_timeoutparameter on the Cloud SQL for PostgreSQL instance. Export logs to Cloud Logging, and create log-based metrics to track deadlock occurrences.
• B. Optimize SQL queries by adding appropriate indexes to frequently accessed columns and rewriting complex joins to use LEFT JOINinstead of INNER JOIN, where applicable.
• C. Use Cloud SQL System Insights to identify long-running queries and number of deadlocks that occurred in the database. Enable a log_lock_waitsflag to determine if lock waits are causing poor performance. Set up Cloud Monitoring alerts for higher CPU utilization and connection count.
• D. Implement connection pooling at the application layer to reduce the number of direct database connections and optimize shared_buffersand work_memparameters in Cloud SQL for PostgreSQL to improve query execution efficiency.

You are migrating your 10 TB on-premises PostgreSQL database to Cloud SQL for PostgreSQL by using Database Migration Service. During the migration, there will be schema changes in the source database. You need to ensure any schema changes are replicated, while keeping disruption to the ongoing migration to a minimum.
What should you do?

• A. Make the schema changes in the destination by using the
  pglogical.replicate_ddl_commandPostgreSQL extension.
• B. Make the schema changes in both source and destination after stopping writes in source.
• C. Make the schema changes in the source by using the pglogical.replicate_ddl_command PostgreSQL extension.
• D. Stop the Database Migration Service migration job. Make the schema changes in the source.Restart the Database Migration Service migration job.

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?

• A. Use Cloud Audit Logs to verify the status.
• B. Use the Google Cloud Console.
• C. Perform the gcloud sql operations list command.
• D. Check the cloudsql.googleapis.com/postgres.log instance log.

You are setting up a Bare Metal Solution environment. You need to update the operating system to the latest version. You need to connect the Bare Metal Solution environment to the internet so you can receive software updates. What should you do?

• A. Setup a static external IP address in your VPC network.
• B. Set up a Cloud NAT gateway on the Compute Engine VM.
• C. Set up Cloud NAT service.
• D. Set up bring your own IP (BYOIP) in your VPC.