HelioBank is deploying Cloud SQL for MySQL in europe-west1 to support payment processing for example.com. The compliance team requires that data at rest be encrypted with a key that they own and manage in a specific European location, and they must control the key lifecycle including rotation and disablement. They also need all client connections to be encrypted from end to end.
What should they configure?

• A. Create the Cloud SQL for MySQL instance with Google managed encryption keys and secure access using VPC Service Controls
• B. Create the Cloud SQL for MySQL instance using customer managed encryption keys from Cloud KMS in the required region and require SSL or TLS for client connections
• C. Create the Cloud SQL for MySQL instance using customer managed encryption keys and place it behind Cloud VPN for all client connectivity
• D. Create the Cloud SQL for MySQL instance with Google managed encryption keys and require SSL or TLS

You work for a financial services company that wants to use fully managed database services.
Traffic volume for your consumer services products has increased annually at a constant rate with occasional spikes around holidays. You frequently need to upgrade the capacity of your database. You want to use Cloud Spanner and include an automated method to increase your hardware capacity to support a higher level of concurrency. What should you do?

• A. Use direct scaling to implement the Autoscaler-based architecture.
• B. Upgrade the Cloud Spanner instance on a periodic basis during the scheduled maintenance window.
• C. Set up alerts that are triggered when Cloud Spanner utilization metrics breach the threshold, and then schedule an upgrade during the scheduled maintenance window.
• D. Use linear scaling to implement the Autoscaler-based architecture

You want to migrate an on-premises mission-critical PostgreSQL database to Cloud SQL. The database must be able to withstand a zonal failure with less than five minutes of downtime and still not lose any transactions. You want to follow Google-recommended practices for the migration. What should you do?

• A. Build a change data capture (CDC) pipeline to read transactions from the primary instance, and replicate them to a secondary instance.
• B. Take nightly snapshots of the primary database instance, and restore them in a secondary zone.
• C. Enable high availability (HA) for the database to make it regional.
• D. Create a read replica in another region, and promote the read replica if a failure occurs.

You are creating new Cloud SQL for PostgreSQL instances in us-east1and us-east4. You are assigning private IP addresses to the Cloud SQL instances starting with us-east1so you can reach the instance without going through the internet or using external IP addresses.
However, you keep getting a "Network association failed" error message. You are using a shared VPC network. What should you do to resolve the issue-

• A. Assign the private IP by using the gcloud sql instances patchcommand.
• B. Use the Google Cloud console to assign private IP.
• C. Enable the Service Networking APIfor the host and service projects.
• D. Configure Private Services Access prior to assigning a private IP to Cloud SQL.

You have a non-critical business application running on Google Kubernetes Engine (GKE) in the app-dev VPC. You have created an AlloyDB cluster with Private Service Access (PSA) and no public IP address in the db-dev VPC. You want your application to securely connect to AlloyDB in a cost-effective way. What should you do-

• A. Connect by using the private IP address of the AlloyDB cluster directly from the application.
• B. Install a SOCKS proxy in a VM in the db-dev VPC. Install AlloyDB Auth Proxy in your GKE cluster, and connect to the AlloyDB cluster through the SOCKS server and port.
• C. Connect by using AlloyDB Auth Proxy installed in the GKE cluster.
• D. Set up a high availability VPN between the app-dev and db-dev VPCs. Connect the application directly to AlloyDB.