Practice Free Professional Cloud Database Engineer Exam Online Questions
You need to issue a new server certificate because your old one is expiring. You need to avoid a restart of your Cloud SQL for MySQL instance.
What should you do in your Cloud SQL instance?
- A . Issue a rollback, and download your server certificate.
- B . Create a new client certificate, and download it.
- C . Create a new server certificate, and download it.
- D . Reset your SSL configuration, and download your server certificate.
C
Explanation:
https://cloud.google.com/sql/docs/sqlserver/configure-ssl-instance#server-certs
You are developing a new application on a VM that is on your corporate network. The application will use Java Database Connectivity (JDBC) to connect to Cloud SQL for PostgreSQL. Your Cloud SQL instance is configured with IP address 192.168.3.48, and SSL is disabled. You want to ensure that your application can access your database instance without requiring configuration changes to your database.
What should you do?
- A . Define a connection string using your Google username and password to point to the external (public) IP address of your Cloud SQL instance.
- B . Define a connection string using a database username and password to point to the internal (private) IP address of your Cloud SQL instance.
- C . Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the internal (private) IP address of your Cloud SQL instance.
- D . Define a connection string using Cloud SQL Auth proxy configured with a service account to point to the external (public) IP address of your Cloud SQL instance.
C
Explanation:
The Cloud SQL connectors are libraries that provide encryption and IAM-based authorization when connecting to a Cloud SQL instance. They can’t provide a network path to a Cloud SQL instance if one is not already present. Other ways to connect to a Cloud SQL instance include using a database client or the Cloud SQL Auth proxy.
https://cloud.google.com/sql/docs/postgres/connect-connectors
https://github.com/GoogleCloudPlatform/cloud-sql-jdbc-socket-factory/blob/main/docs/jdbc-postgres.md
Your organization deployed a new version of a critical application that uses Cloud SQL for MySQL with high availability (HA) and binary logging enabled to store transactional information. The latest release of the application had an error that caused massive data corruption in your Cloud SQL for MySQL database. You need to minimize data loss.
What should you do?
- A . Open the Google Cloud Console, navigate to SQL > Backups, and select the last version of the automated backup before the corruption.
- B . Reload the Cloud SQL for MySQL database using the LOAD DATA command to load data from CSV files that were used to initialize the instance.
- C . Perform a point-in-time recovery of your Cloud SQL for MySQL database, selecting a date and time before the data was corrupted.
- D . Fail over to the Cloud SQL for MySQL HA instance. Use that instance to recover the transactions that occurred before the corruption.
C
Explanation:
Binary Logging enabled, with that you can identify the point of time the data was good and recover from that point time. https://cloud.google.com/sql/docs/mysql/backup-recovery/pitr#perform_the_point-in-time_recovery_using_binary_log_positions
You work for a large retail and ecommerce company that is starting to extend their business globally. Your company plans to migrate to Google Cloud. You want to use platforms that will scale easily, handle transactions with the least amount of latency, and provide a reliable customer experience. You need a storage layer for sales transactions and current inventory levels. You want to retain the same relational schema that your existing platform uses.
What should you do?
- A . Store your data in Firestore in a multi-region location, and place your compute resources in one of the constituent regions.
- B . Deploy Cloud Spanner using a multi-region instance, and place your compute resources close to the default leader region.
- C . Build an in-memory cache in Memorystore, and deploy to the specific geographic regions where your application resides.
- D . Deploy a Bigtable instance with a cluster in one region and a replica cluster in another geographic region.