You have a container deployed on Google Kubernetes Engine. The container can sometimes be slow to launch, so you have implemented a liveness probe. You notice that the liveness probe occasionally fails on launch. What should you do?

• A.Add a startup probe.
• B.Increase the initial delay for the liveness probe.
• C.Increase the CPU limit for the container.
• D.Add a readiness probe.

Comment: *

Name: *

Email: *

Verification: *

You have an application deployed in Google Kubernetes Engine (GKE). You need to update the application to make authorized requests to Google Cloud managed services. You want this to be a one-time setup, and you need to follow security best practices of auto-rotating your security keys and storing them in an encrypted store. You already created a service account with appropriate access to the Google Cloud service. What should you do next?

• A.Assign the Google Cloud service account to your GKE Pod using Workload Identity.
• B.Export the Google Cloud service account, and share it with the Pod as a Kubernetes Secret.
• C.Export the Google Cloud service account, and embed it in the source code of the application.
• D.Export the Google Cloud service account, and upload it to HashiCorp Vault to generate a dynamic service account for your application.

Comment: *

Name: *

Email: *

Verification: *

You recently developed a new service on Cloud Run. The new service authenticates using a custom service and then writes transactional information to a Cloud Spanner database. You need to verify that your application can support up to 5,000 read and 1,000 write transactions per second while identifying any bottlenecks that occur. Your test infrastructure must be able to autoscale. What should you do?

• A.Build a test harness to generate requests and deploy it to Cloud Run. Analyze the VPC Flow Logs using Cloud Logging.
• B.Create a Google Kubernetes Engine cluster running the Locust or JMeter images to dynamically generate load tests. Analyze the results using Cloud Trace.
• C.Create a Cloud Task to generate a test load. Use Cloud Scheduler to run 60,000 Cloud Task transactions per minute for 10 minutes. Analyze the results using Cloud Monitoring.
• D.Create a Compute Engine instance that uses a LAMP stack image from the Marketplace, and use Apache Bench to generate load tests against the service. Analyze the results using Cloud Trace.

Comment: *

Name: *

Email: *

Verification: *

You are building a highly available and globally accessible application that will serve static content to users. You need to configure the storage and serving components. You want to minimize management overhead and latency while maximizing reliability for users. What should you do?

• A.1. Create a managed instance group. Replicate the static content across the virtual machines (VMs)
  2. Create an external HTTP(S) load balancer.
  3. Enable Cloud CDN, and send traffic to the managed instance group.
• B.1. Create an unmanaged instance group. Replicate the static content across the VMs.
  2. Create an external HTTP(S) load balancer
  3. Enable Cloud CDN, and send traffic to the unmanaged instance group.
• C.1. Create a Standard storage class, regional Cloud Storage bucket. Put the static content in the bucket
  2. Reserve an external IP address, and create an external HTTP(S) load balancer
  3. Enable Cloud CDN, and send traffic to your backend bucket
• D.1. Create a Standard storage class, multi-regional Cloud Storage bucket. Put the static content in the bucket.
  2. Reserve an external IP address, and create an external HTTP(S) load balancer.
  3. Enable Cloud CDN, and send traffic to your backend bucket.

Comment: *

Name: *

Email: *

Verification: *

You need to configure a Deployment on Google Kubernetes Engine (GKE). You want to include a check that verifies that the containers can connect to the database. If the Pod is failing to connect, you want a script on the container to run to complete a graceful shutdown. How should you configure the Deployment?

• A.Create two jobs: one that checks whether the container can connect to the database, and another that runs the shutdown script if the Pod is failing.
• B.Create the Deployment with a livenessProbe for the container that will fail if the container can't connect to the database. Configure a Prestop lifecycle handler that runs the shutdown script if the container is failing.
• C.Create the Deployment with a PostStart lifecycle handler that checks the service availability. Configure a PreStop lifecycle handler that runs the shutdown script if the container is failing.
• D.Create the Deployment with an initContainer that checks the service availability. Configure a Prestop lifecycle handler that runs the shutdown script if the Pod is failing.

Comment: *

Name: *

Email: *

Verification: *