[2024-Feb-New]Braindump2go Professional-Cloud-Developer PDF Dumps(102-268)

Braindump2go Guarantee All Exams 100% Pass
messages in the topic.
B. Deploy 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.
C. Deploy 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.
D. Deploy your code on Cloud Functions. Use a Pub/Sub trigger to handle new messages in the
topic.
One Time!
Answer: D
Explanation:
https://cloud.google.com/functions/docs/calling/pubsub
We selected D based on our experience with Cloud Functions and the material at the URL above.
Since messages can be obtained from Cloud Functions arguments, we are not aware of the description of Subscription.
QUESTION 267
You have an application running on Google Kubernetes Engine (GKE). The application is currently using a logging
library and is outputting to standard output. You need to export the logs to Cloud Logging, and you need the logs to
include metadata about each request. You want to use the simplest method to accomplish this. What should you do?
A. Change your application's logging library to the Cloud Logging library, and configure your
application to export logs to Cloud Logging.
B. Update your application to output logs in JSON format, and add the necessary metadata to the
JSON.
C. Update your application to output logs in CSV format, and add the necessary metadata to the
CSV.
D. Install the Fluent Bit agent on each of your GKE nodes, and have the agent export all logs from
/var/log.
Answer: B
Explanation:
By default, GKE clusters are natively integrated with Cloud Logging (and Monitoring). When you create a GKE cluster,
both Monitoring and Cloud Logging are enabled by default.
GKE deploys a per-node logging agent that reads container logs, adds helpful metadata, and then sends the logs to the
logs router, which sends the logs to Cloud Logging and any of the Logging sink destinations that you have configured.
Cloud Logging stores logs for the duration that you specify or 30 days by default. Because Cloud Logging automatically
collects standard output and error logs for containerized processes, you can start viewing your logs as soon as your
application is deployed.
https://cloud.google.com/blog/products/management-tools/using-logging-your-apps-running-kubernetes-engine
QUESTION 268
You are working on a new application that is deployed on Cloud Run and uses Cloud Functions. Each time new
features are added, new Cloud Functions and Cloud Run services are deployed. You use ENV variables to keep track
of the services and enable interservice communication, but the maintenance of the ENV variables has become difficult.
You want to implement dynamic discovery in a scalable way. What should you do?
A. Configure your microservices to use the Cloud Run Admin and Cloud Functions APIs to query for
deployed Cloud Run services and Cloud Functions in the Google Cloud project.
B. Create a Service Directory namespace. Use API calls to register the services during deployment,
and query during runtime.
C. Rename the Cloud Functions and Cloud Run services endpoint is using a well-documented
naming convention.
D. Deploy Hashicorp Consul on a single Compute Engine instance. Register the services with
Consul during deployment, and query during runtime.
Professional-Cloud-Developer Exam Dumps Professional-Cloud-Developer Exam Questions
Professional-Cloud-Developer PDF Dumps Professional-Cloud-Developer VCE Dumps
https://www.braindump2go.com/professional-cloud-developer.html