You need to grant access for three users so that they can view and edit table data on a Cloud Spanner instance. What should you do?

• A.Run gcloud iam roles describe roles/spanner.databaseUser.
  Add the users to a new group. Add the group to the role.
• B.Run gcloud iam roles describe roles/spanner.viewer - -project my-project.
  Add the users to the role.
• C.Run gcloud iam roles describe roles/spanner.viewer - -project my-project.
  Add the users to a new group. Add the group to the role.
• D.Run gcloud iam roles describe roles/spanner.databaseUser.
  Add the users to the role.

Comment: *

Name: *

Email: *

Verification: *

You need to set up a policy so that videos stored in a specific Cloud Storage Regional bucket are moved to Coldline after 90 days, and then deleted after one year from their creation.
How should you set up the policy?

• A.Use gsutil rewrite and set the Delete action to 365 days.
• B.Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions.
  Set the SetStorageClass action to 90 days and the Delete action to 275 days (365-90)
• C.Use gsutil rewrite and set the Delete action to 275 days (365-90).
• D.Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions.
  Set the SetStorageClass action to 90 days and the Delete action to 365 days.

Comment: *

Name: *

Email: *

Verification: *

Your boss has asked you to set up the CFO as a user inside Google Cloud. Before walking away, she said, "And obviously you know which role to assign him."
Which role was she likely talking about, and why is it obvious? (Select one role and one reason)

• A.Role: Billing Account Viewer
• B.Reason:: This role will ensure the CFO can perform any billing task that they may need.
• C.Reason: This role will ensure the CFO has full access to the project.
• D.Role: Project Owner
• E.Reason: This role will ensure the CFO has access to view the spending data.
• F.Role: Billing Account Admin

Comment: *

Name: *

Email: *

Verification: *

You are building a product on top of Google Kubernetes Engine (GKE). You have a single GKE cluster. For each of your customers, a Pod is running in that cluster, and your customers can run arbitrary code inside their Pod. You want to maximize the isolation between your customers' Pods. What should you do?

• A.Use Binary Authorization and whitelist only the container images used by your customers' Pods.
• B.Use the Container Analysis API to detect vulnerabilities in the containers used by your customers' Pods.
• C.Create a GKE node pool with a sandbox type configured to gvisor. Add the parameter runtimeClassName: gvisor to the specification of your customers' Pods.
• D.Use the cos_containerd image for your GKE nodes. Add a nodeSelector with the value cloud.google.com/gke-os-distribution: cos_containerd to the specification of your customers' Pods.

Comment: *

Name: *

Email: *

Verification: *

You created a Kubernetes deployment by running kubectl run nginx image=nginx replicas=1.
After a few days, you decided you no longer want this deployment. You identified the pod and deleted it by running kubectl delete pod. You noticed the pod got recreated.
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-84748895c4-nqqmt 1/1 Running 0 9m41s
$ kubectl delete pod nginx-84748895c4-nqqmt
pod nginx-84748895c4-nqqmt deleted
$ kubectl get pods
NAME READY STATUS RESTARTS AGE
nginx-84748895c4-k6bzl 1/1 Running 0 25s
What should you do to delete the deployment and avoid pod getting recreated?

• A.kubectl delete deployment nginx
• B.kubectl delete deployment=nginx
• C.kubectl delete pod nginx-84748895c4-k6bzl -no-restart 2
• D.kubectl delete inginx

Comment: *

Name: *

Email: *

Verification: *