You are developing an application that needs to connect to a Cloud SQL for PostgreSQL database by using the Cloud SQL Auth Proxy. The Cloud SQL Auth Proxy is hosted in a different Google Cloud VPC network. The Cloud SQL for PostgreSQL instance has public and private IP addresses. You are required to use the private IP for security reasons. When testing the connection to the Cloud SQL instance, you can connect by using the public IP address, but you are unable to connect by using the private IP address. How should you fix this issue?

• A.Run the Cloud SQL Auth Proxy as a background service.
• B.Add the --private-ip option when starting the Cloud SQL Auth Proxy.
• C.Set up VPC Network Peering between your VPC and the VPC where the Cloud SQL instance is deployed.
• D.Grant yourself the IAM role that provides access to the Cloud SQL instance.

Comment: *

Name: *

Email: *

Verification: *

You are a developer at a large organization. You are deploying a web application to Google Kubernetes Engine (GKE). The DevOps team has built a CI/CD pipeline that uses Cloud Deploy to deploy the application to Dev, Test, and Prod clusters in GKE. After Cloud Deploy successfully deploys the application to the Dev cluster, you want to automatically promote it to the Test cluster. How should you configure this process following Google-recommended best practices?

• A.1. Create a Cloud Build trigger that listens for SUCCEEDED Pub/Sub messages from the clouddeploy-operations topic.
  2. Configure Cloud Build to include a step that promotes the application to the Test cluster.
• B.1. Create a Cloud Function that calls the Google Cloud Deploy API to promote the application to the Test cluster.
  2. Configure this function to be triggered by SUCCEEDED Pub/Sub messages from the cloud- builds topic.
• C.1. Create a Cloud Function that calls the Google Cloud Deploy API to promote the application to the Test cluster.
  2. Configure this function to be triggered by SUCCEEDED Pub/Sub messages from the clouddeploy-operations topic.
• D.1. Create a Cloud Build pipeline that uses the gke-deploy builder.
  2. Create a Cloud Build trigger that listens for SUCCEEDED Pub/Sub messages from the cloud- builds topic.
  3. Configure this pipeline to run a deployment step to the Test cluster.

Comment: *

Name: *

Email: *

Verification: *

Your team develops services that run on Google Kubernetes Engine. You need to standardize their log data using Google-recommended practices and make the data more useful in the fewest number of steps. What should you do? (Choose two.)

• A.Create aggregated exports on application logs to BigQuery to facilitate log analytics.
• B.Mandate the use of the Logging API in the application code to write structured logs to Cloud Logging.
• C.Mandate the use of the Pub/Sub API to write structured data to Pub/Sub and create a Dataflow streaming pipeline to normalize logs and write them to BigQuery for analytics.
• D.Write log output to standard output (stdout) as single-line JSON to be ingested into Cloud Logging as structured logs.
• E.Create aggregated exports on application logs to Cloud Storage to facilitate log analytics.

Comment: *

Name: *

Email: *

Verification: *

Your website is deployed on Compute Engine. Your marketing team wants to test conversion rates between 3 different website designs.
Which approach should you use?

• A.Deploy the website on App Engine and use traffic splitting.
• B.Deploy the website on App Engine as three separate services.
• C.Deploy the website on Cloud Functions and use traffic splitting.
• D.Deploy the website on Cloud Functions as three separate functions.

Comment: *

Name: *

Email: *

Verification: *

You are planning to migrate a MySQL database to the managed Cloud SQL database for Google Cloud. You have Compute Engine virtual machine instances that will connect with this Cloud SQL instance. You do not want to whitelist IPs for the Compute Engine instances to be able to access Cloud SQL.
What should you do?

• A.Enable private IP for the Cloud SQL instance.
• B.Whitelist a project to access Cloud SQL, and add Compute Engine instances in the whitelisted project.
• C.Create a role in Cloud SQL that allows access to the database from external instances, and assign the Compute Engine instances to that role.
• D.Create a CloudSQL instance on one project. Create Compute engine instances in a different project.Create a VPN between these two projects to allow internal access to CloudSQL.

Comment: *

Name: *

Email: *

Verification: *