You have a Compute Engine instance hosting a production application. You want to receive an email if the instance consumes more than 90% of its CPU resources for more than 15 minutes.
You want to use Google services. What should you do?

• A.1. Create a consumer Gmail account.
  2. Write a script that monitors the CPU usage.
  3. When the CPU usage exceeds the threshold, have that script send an email using the Gmail account and smtp.gmail.com on port 25 as SMTP server.
• B.1. In Stackdriver Logging, create a logs-based metric to extract the CPU usage by using this regular expression: CPU Usage: ([0-9] {1,3})%
  2. In Stackdriver Monitoring, create an Alerting Policy based on this metric.
  3. Configure your email address in the notification channel.
• C.1. Create a Stackdriver Workspace, and associate your Google Cloud Platform (GCP) project with it.
  2. Create an Alerting Policy in Stackdriver that uses the threshold as a trigger condition.
  3. Configure your email address in the notification channel.
• D.1. Create a Stackdriver Workspace, and associate your GCP project with it.
  2. Write a script that monitors the CPU usage and sends it as a custom metric to Stackdriver.
  3. Create an uptime check for the instance in Stackdriver.

Comment: *

Name: *

Email: *

Verification: *

You are planning to migrate a database and a backend application to a Standard Google Kubernetes Engine (GKE) cluster. You need to prevent data loss and make sure there are enough nodes available for your backend application based on the demands of your workloads. You want to follow Google-recommended practices and minimize the amount of manual work required. What should you do?

• A.Run your database as a StatefulSet. Configure cluster autoscaling to handle changes in the demands of your workloads.
• B.Run your database as a Deployment. Configure cluster autoscaling to handle changes in the demands of your workloads.
• C.Run your database as a single Pod. Run the resize command when you notice changes in the demands of your workloads.
• D.Run your database as a DaemonSet. Run the resize command when you notice changes in the demands of your workloads.

Comment: *

Name: *

Email: *

Verification: *

You want to deploy an application on Cloud Run that processes messages from a Cloud Pub/Sub topic. You want to follow Google-recommended practices. What should you do?

• A.1. Create a service account.2. Give the Cloud Run Invoker role to that service account for your Cloud Run application.3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint.
• B.1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.2. Create a Cloud Pub/Sub subscription for that topic.3. Make your application pull messages from that subscription.
• C.1. Deploy your application on Cloud Run on GKE with the connectivity set to Internal.2. Create a Cloud Pub/Sub subscription for that topic.3. In the same Google Kubernetes Engine cluster as your application, deploy a container that takes the messages and sends them to your application.
• D.1. Create a Cloud Function that uses a Cloud Pub/Sub trigger on that topic.2. Call your application on Cloud Run from the Cloud Function for every message.

Comment: *

Name: *

Email: *

Verification: *

You are deploying a web application using Compute Engine. You created a managed instance group (MIG) to host the application. You want to follow Google-recommended practices to implement a secure and highly available solution. What should you do?

• A.Use SSL proxy load balancing for the MIG and an A record in your DNS private zone with the load balancer's IP address.
• B.Use SSL proxy load balancing for the MIG and a CNAME record in your DNS public zone with the load balancer's IP address.
• C.Use HTTP(S) load balancing for the MIG and a CNAME record in your DNS private zone with the load balancer's IP address.
• D.Use HTTP(S) load balancing for the MIG and an A record in your DNS public zone with the load balancer's IP address.

Comment: *

Name: *

Email: *

Verification: *

You create a Deployment with 2 replicas in a Google Kubernetes Engine cluster that has a single preemptible node pool. After a few minutes, you use kubectlto examine the status of your Pod and observe that one of them is still in Pendingstatus:

What is the most likely cause?

• A.The pending Pod's resource requests are too large to fit on a single node of the cluster.
• B.Too many Pods are already running in the cluster, and there are not enough resources left to schedule the pending Pod.
• C.The node pool is configured with a service account that does not have permission to pull the container image used by the pending Pod.
• D.The pending Pod was originally scheduled on a node that has been preempted between the creation of the Deployment and your verification of the Pods' status. It is currently being rescheduled on a new node.

Comment: *

Name: *

Email: *

Verification: *