Question 1

You are developing an event-driven application. You have created a topic to receive messages sent to Pub/Sub. You want those messages to be processed in real time. You need the application to be independent from any other system and only incur compute costs when new messages arrive. You want to configure the simplest and most efficient architecture What should you do?

ADeploy your code on Cloud Functions. Use a Pub/Sub trigger to invoke the Cloud Function. Use the Pub/Sub API to create a pull subscription to the Pub/Sub topic and read messages from it.

BDeploy your code on Cloud Functions. Use a Pub/Sub trigger to handle new messages in the topic.

CDeploy the application on Google Kubernetes Engine. Use the Pub/Sub API to create a pull subscription to the Pub/Sub topic and read messages from it

DDeploy the application on Compute Engine. Use a Pub/Sub push subscription to process new messages in the topic.

Answer : B

https://cloud.google.com/functions/docs/calling/pubsub

Question 2

You recently developed an application that monitors a large number of stock prices. You need to configure Pub/Sub to receive a high volume messages and update the current stock price in a single large in-memory database The downstream service needs only the most up-to-date prices in the in-memory database to perform stock trading transactions Each message contains three pieces of information

* Stock symbol

* Stock price

* Timestamp for the update

How should you set up your Pub/Sub subscription?

ACreate a pull subscription with both ordering and exactly-once delivery turned off

BCreate a pull subscription with exactly-once delivery enabled

CCreate a push subscription with exactly-once delivery enabled

DCreate a push subscription with both ordering and exactly-once delivery turned off

Answer : C

Question 3

You are a developer at a large corporation You manage three Google Kubernetes Engine clusters. Your team's developers need to switch from one cluster to another regularly without losing access to their preferred development tools. You want to configure access to these clusters using the fewest number of steps while following Google-recommended best practices. What should you do?

AAsk the developers to use Cloud Shell and run gcloud container clusters get-credentials to switch to another cluster.

BAsk the developers to open three terminals on their workstation and use kubecrt1 config to configure access to each cluster.

CAsk the developers to install the gcloud CLI on their workstation and run gcloud container clusters get-credentials to switch to another cluster

DIn a configuration file, define the clusters users, and contexts Email the file to the developers and ask them to use kubect1 config to add cluster, user and context details.

Answer : D

https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

Question 4

You are a developer at a financial institution You use Cloud Shell to interact with Google Cloud services. User data is currently stored on an ephemeral disk however a recently passed regulation mandates that you can no longer store sensitive information on an ephemeral disk. You need to implement a new storage solution for your user data You want to minimize code changes Where should you store your user data'?

AStore user data on a Cloud Shell home disk and log in at least every 120 days to prevent its deletion

BStore user data on a persistent disk in a Compute Engine instance

CStore user data m BigQuery tables

DStore user data in a Cloud Storage bucket

Answer : B

Question 5

You are a developer at a social media company The company runs their social media website on-premises and uses MySQL as a backend to store user profiles and user posts. Your company plans to migrate to Google Cloud, and your team will migrate user profile information to Firestore. You are tasked with designing the Firestore collections. What should you do?

ACreate one root collection for user profiles, and store each user's post as a nested list in the user profile document.

BCreate one root collection for user profiles, and create one root collection for user posts.

CCreate one root collection for user profiles, and create one subcollection for each user's posts.

DCreate one root collection for user posts, and create one subcollection for each user's profile