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.
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.
Identify and optimize slow running queries, or set parallel replication flags.
B.
Stop all running queries, and re-create the replicas.
C.
Edit the primary instance to upgrade to a larger disk, and increase vCPU count.
D.
Edit the primary instance to add additional memory.
During an internal audit, you realized that one of your Cloud SQL for MySQL instances does not have high availability (HA) enabled. You want to follow Google-recommended practices to enable HA on your existing instance. What should you do?
A.
Create a new Cloud SQL for MySQL instance, enable HA, and use the export and import option to migrate your data.
B.
Create a new Cloud SQL for MySQL instance, enable HA, and use Cloud Data Fusion to migrate your data.
C.
Use the gcloud instances patch command to update your existing Cloud SQL for MySQL instance.
D.
Shut down your existing Cloud SQL for MySQL instance, and enable HA.
You are managing a set of Cloud SQL databases in Google Cloud. Regulations require that database backups reside in the region where the database is created. You want to minimize operational costs and administrative effort. What should you do?
A.
Configure the automated backups to use a regional Cloud Storage bucket as a custom location.
B.
Use the default configuration for the automated backups location.
C.
Disable automated backups, and create an on-demand backup routine to a regional Cloud Storage bucket.
D.
Disable automated backups, and configure serverless exports to a regional Cloud Storage bucket.
Your ecommerce application connecting to your Cloud SQL for SQL Server is expected to have additional traffic due to the holiday weekend. You want to follow Google-recommended practices to set up alerts for CPU and memory metrics so you can be notified by text message at the first sign of potential issues. What should you do?
A.
Use a Cloud Function to pull CPU and memory metrics from your Cloud SQL instance and to call a custom service to send alerts.
B.
Use Error Reporting to monitor CPU and memory metrics and to configure SMS notification channels.
C.
Use Cloud Logging to set up a log sink for CPU and memory metrics and to configure a sink destination to send a message to Pub/Sub.
D.
Use Cloud Monitoring to set up an alerting policy for CPU and memory metrics and to configure SMS notification channels.