Your engineers need to pass database credentials to a Kubernetes Pod. The YAML they're using looks similar to the following:

apiVersion: "extensions/v1beta1"

kind: "Deployment"

metadata:

name: "products-service"

namespace: "default"

labels:

app: "products-service"

spec:

replicas: 3

selector:

matchLabels:

app: "products-service"

template:

metadata:

labels:

app: "products-service"

spec:

containers:

-

name: "products" image: "gcr.io/find-seller-app-dev/products:latest" env:

-

name: "database_user" value: "admin"

-

name: "database_password" value: "TheB3stP@ssW0rd"

What is Google's recommended best practice for working with sensitive information inside of Kubernetes?

A. Store the credentials in a ConfigMap.

B. Mount the credentials in a volume.

C. Use an environment variable.

D. Store the credentials in a Secret.

Your security team has asked you to present them some numbers based on the logs that are exported to BigQuery. Due to the team structure, your manager has asked you to determine how much the query will cost. What's the best way to determine the cost?

A. It's not possible to estimate the cost of a query.

B. Create the query and execute the query in "cost estimation mode"

C. Create the query and use the dry-run option to determine the amount of data read, then use the price calculator to determine the cost.

D. Use the BigQuery index viewer to determine how many records you'll be reading.

Your company is running a three-tier web application on virtual machines that use a MySQL database. You need to create an estimated total cost of cloud infrastructure to run this application on Google Cloud instances and Cloud SQL. What should you do?

A. Create a Google spreadsheet with multiple Google Cloud resource combinations. On a separate sheet, import the current Google Cloud prices and use these prices for the calculations within formulas.

B. Use the Google Cloud Pricing Calculator and select the Cloud Operations template to define your web application with as much detail as possible.

C. Implement a similar architecture on Google Cloud, and run a reasonable load test on a smaller scale. Check the billing information, and calculate the estimated costs based on the real load your system usually handles.

D. Use the Google Cloud Pricing Calculator to determine the cost of every Google Cloud resource you expect to use. Use similar size instances for the web server, and use your current on-premises machines as a comparison for Cloud SQL.

You have an application running in Google Kubernetes Engine (GKE) with cluster autoscaling enabled. The application exposes a TCP endpoint. There are several replicas of this application. You have a Compute Engine instance in the same region, but in another Virtual Private Cloud (VPC), called gce-network, that has no overlapping IP ranges with the first VPC. This instance needs to connect to the application on GKE. You want to minimize effort. What should you do?

A. 1. In GKE, create a Service of type LoadBalancer that uses the application's Pods as backend.

2.

Set the service's externalTrafficPolicy to Cluster.

3.

Configure the Compute Engine instance to use the address of the load balancer that has been created.

B. 1. In GKE, create a Service of type NodePort that uses the application's Pods as backend.

2.

Create a Compute Engine instance called proxy with 2 network interfaces, one in each VPC.

3.

Use iptables on this instance to forward traffic from gce-network to the GKE nodes.

4.

Configure the Compute Engine instance to use the address of proxy in gce-network as endpoint.

C. 1. In GKE, create a Service of type LoadBalancer that uses the application's Pods as backend.

2.

Add an annotation to this service: cloud.google.com/load-balancer-type: Internal

3.

Peer the two VPCs together.

4.

Configure the Compute Engine instance to use the address of the load balancer that has been created.

D. 1. In GKE, create a Service of type LoadBalancer that uses the application's Pods as backend.

2.

Add a Cloud Armor Security Policy to the load balancer that whitelists the internal IPs of the MIG's instances.

3.

Configure the Compute Engine instance to use the address of the load balancer that has been created.

You are working with a Cloud SQL MySQL database at your company. You need to retain a month-end copy of the database for three years for audit purposes. What should you do?

A. Set up an export job for the first of the month. Write the export file to an Archive class Cloud Storage bucket.

B. Save the automatic first-of-the-month backup for three years. Store the backup file in an Archive class Cloud Storage bucket.

C. Set up an on-demand backup for the first of the month. Write the backup to an Archive class Cloud Storage bucket.

D. Convert the automatic first-of-the-month backup to an export file. Write the export file to a Coldline class Cloud Storage bucket.