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. 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.
• B.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.
• C.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.
• D.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.

Comment: *

Name: *

Email: *

Verification: *

You are building an archival solution for your data warehouse and have selected Cloud Storage to archive your dat a. Your users need to be able to access this archived data once a quarter for some regulatory requirements. You want to select a cost-efficient option. Which storage option should you use?

• A.Cold Storage
• B.Nearline Storage
• C.Regional Storage
• D.Multi-Regional Storage

Comment: *

Name: *

Email: *

Verification: *

Your company was recently impacted by a service disruption that caused multiple Dataflow jobs to get stuck, resulting in significant downtime in downstream applications and revenue loss. You were able to resolve the issue by identifying and fixing an error you found in the code. You need to design a solution with minimal management effort to identify when jobs are stuck in the future to ensure that this issue does not occur again. What should you do?

• A.Set up Error Reporting to identify stack traces that indicate slowdowns in Dataflow jobs. Set up alerts based on these log entries.
• B.Use the Personalized Service Health dashboard to identify issues with Dataflow jobs across regions.
• C.Update the Dataflow job configurations to send messages to a Pub/Sub topic when there are delays. Configure a backup Dataflow job to process jobs that are delayed. Use Cloud Tasks to trigger an alert when messages are pushed to the Pub/Sub topic.
• D.Set up Cloud Monitoring alerts on the data freshness metric for the Dataflow jobs to receive a notification when a certain threshold is reached.

Comment: *

Name: *

Email: *

Verification: *

You are deploying an application to a Compute Engine VM in a managed instance group. The application must be running at all times, but only a single instance of the VM should run per GCP project. How should you configure the instance group?

• A.Set autoscaling to On, set the minimum number of instances to 1, and then set the maximum number of instances to 2.
• B.Set autoscaling to Off, set the minimum number of instances to 1, and then set the maximum number of instances to 1.
• C.Set autoscaling to Off, set the minimum number of instances to 1, and then set the maximum number of instances to 2.
• D.Set autoscaling to On, set the minimum number of instances to 1, and then set the maximum number of instances to 1.

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: *