Online Access Free Professional-Cloud-Database-Engineer Exam Questions

Your team recently released a new version of a highly consumed application to accommodate additional user traffic. Shortly after the release, you received an alert from your production monitoring team that there is consistently high replication lag between your primary instance and the read replicas of your Cloud SQL for MySQL instances. You need to resolve the replication lag. What should you do?

• A.Edit the primary instance to upgrade to a larger disk, and increase vCPU count.
• B.Edit the primary instance to add additional memory.
• C.Identify and optimize slow running queries, or set parallel replication flags.
• D.Stop all running queries, and re-create the replicas.

You are responsible for designing a new database for an airline ticketing application in Google Cloud. This application must be able to:
Work with transactions and offer strong consistency.
Work with structured and semi-structured (JSON) data.
Scale transparently to multiple regions globally as the operation grows.
You need a Google Cloud database that meets all the requirements of the application. What should you do?

• A.Use Cloud SQL for PostgreSQL with both cross-region read replicas.
• B.Use a Bigtable instance with clusters in multiple regions.
• C.Use Firestore in Datastore mode.
• D.Use Cloud Spanner in a multi-region configuration.

You are deploying a Cloud SOL for MySQL database to serve a non-critical application. The database size is
10 GB and will be updated every night with data stored in a Cloud Storage bucket. The database serves read- only traffic from the application during the day. The data locally requirement of This application mandates that data must reside in a single region. You want to minimize the cost of running this database while maintaining an RTO of 1 day. What should you do?

• A.Create a Cloud SQL for MySQL instance with high availability (HA) disabled. Create a read replica in a second region.
• B.Create a Cloud SQL for MySQL instance with high availability (HA) enabled. Configure automated backups of the Cloud SQL instance and use the default backup location.
• C.Create a Cloud SQL for MySQL instance with high availability (HA) disabled. Configure automated backups of the Cloud SQL instance and use a custom backup location to store backups in a Cloud Storage bucket in the same region.
• D.Create a Cloud SQL for MySQL instance with high availability (HA) disabled. Create a read replica in the same zone.

You are migrating an on-premises application to Google Cloud. The application requires a high availability (HA) PostgreSQL database to support business-critical functions. Your company's disaster recovery strategy requires a recovery time objective (RTO) and recovery point objective (RPO) within 30 minutes of failure.
You plan to use a Google Cloud managed service. What should you do to maximize uptime for your application?

• A.Deploy Cloud SQL for PostgreSQL in a regional configuration. Create a read replica in a different zone in the same region and a read replica in another region for disaster recovery.
• B.Migrate the PostgreSQL database to multi-regional Cloud Spanner so that a single region outage will not affect your application. Update the schema to support Cloud Spanner data types, and refactor the application.
• C.Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Take periodic backups, and use this backup to restore to a new Cloud SQL for PostgreSQL instance in another region during a disaster recovery event.
• D.Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross-region read replica, and promote the read replica as the primary node for disaster recovery.

You are managing a Cloud SQL for PostgreSQL instance in Google Cloud. You have a primary instance in region 1 and a read replica in region 2. After a failure of region 1, you need to make the Cloud SQL instance available again. You want to minimize data loss and follow Google-recommended practices. What should you do?

• A.Check your instance operational log for the automatic failover status. Look for time, type, and status of the operations. If the failover operation is successful, no action is necessary. Otherwise, manually perform gcloud sql instances failover .
• B.Check "Lag Bytes" in the monitoring dashboard for the primary instance in the read replica instance.
  Check the replication status usingpg_catalog.pg_last_wal_receive_lsn(). Then, fail over to region 2 by promoting the read replica instance.
• C.Restore the Cloud SQL instance from the automatic backups in another zone in region 1.
• D.Restore the Cloud SQL instance from the automatic backups in region 3.