Summer Certification Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = getmirror

Home
Google
Cloud Developer
Professional-Cloud-Developer
Google Certified Professional - Cloud Developer Questions and Answers

Pass the Google Cloud Developer Professional-Cloud-Developer Questions and answers with ExamsMirror

Practice at least 50% of the questions to maximize your chances of passing.

Exam Professional-Cloud-Developer Premium Access

View all detail and faqs for the Professional-Cloud-Developer exam

Go to Exam

702 Students Passed

84% Average Score

95% Same Questions

Viewing page 2 out of 6 pages

Viewing questions 11-20 out of questions

Questions # 11:

Your company’s corporate policy states that there must be a copyright comment at the very beginning of all source files. You want to write a custom step in Cloud Build that is triggered by each source commit. You need the trigger to validate that the source contains a copyright and add one for subsequent steps if not there. What should you do?

Options:

Build a new Docker container that examines the files in /workspace and then checks and adds a copyright for each source file. Changed files are explicitly committed back to the source repository.

Build a new Docker container that examines the files in /workspace and then checks and adds a copyright for each source file. Changed files do not need to be committed back to the source repository.

Build a new Docker container that examines the files in a Cloud Storage bucket and then checks and adds a copyright for each source file. Changed files are written back to the Cloud Storage bucket.

Build a new Docker container that examines the files in a Cloud Storage bucket and then checks and adds a copyright for each source file. Changed files are explicitly committed back to the source repository.

Answer

Explanation

https://cloud.google.com/build/docs/configuring-builds/pass-data-between-steps#passing_data_using_workspaces

To pass data between build steps, store the assets produced by the build step in /workspace and these assets will be available to any subsequent build steps.

Questions # 12:

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?

Options:

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

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

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

In 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

Explanation

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

Questions # 13:

You are a developer working with the CI/CD team to troubleshoot a new feature that your team introduced. The CI/CD team used HashiCorp Packer to create a new Compute Engine image from your development branch. The image was successfully built, but is not booting up. You need to investigate the issue with the CI/CD team. What should you do?

Options:

Create a new feature branch, and ask the build team to rebuild the image.

Shut down the deployed virtual machine, export the disk, and then mount the disk locally to access the boot logs.

Install Packer locally, build the Compute Engine image locally, and then run it in your personal Google Cloud project.

Check Compute Engine OS logs using the serial port, and check the Cloud Logging logs to confirm access to the serial port.

Answer

Explanation

https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-using-serial-console

Questions # 14:

Your team is developing an ecommerce platform for your company. Users will log in to the website and add items to their shopping cart. Users will be automatically logged out after 30 minutes of inactivity. When users log back in, their shopping cart should be saved. How should you store users’ session and shopping cart information while following Google-recommended best practices?

Options:

Store the session information in Pub/Sub, and store the shopping cart information in Cloud SQL.

Store the shopping cart information in a file on Cloud Storage where the filename is the SESSION ID.

Store the session and shopping cart information in a MySQL database running on multiple Compute Engine instances.

Store the session information in Memorystore for Redis or Memorystore for Memcached, and store the shopping cart information in Firestore.

Answer

Questions # 15:

You are developing a new public-facing application that needs to retrieve specific properties in the metadata of users’ objects in their respective Cloud Storage buckets. Due to privacy and data residency requirements, you must retrieve only the metadata and not the object data. You want to maximize the performance of the retrieval process. How should you retrieve the metadata?

Options:

Use the patch method.

Use the compose method.

Use the copy method.

Use the fields request parameter.

Answer

Explanation

https://cloud.google.com/storage/docs/json_api/v1/objects/get

Questions # 16:

You are developing an online gaming platform as a microservices application on Google Kubernetes Engine (GKE). Users on social media are complaining about long loading times for certain URL requests to the application. You need to investigate performance bottlenecks in the application and identify. which HTTP requests have a significantly high latency span in user requests What should you do?

Options:

Instrument your microservices by installing the OpenTelemetry tracing package Update your application code to send traces to Trace for inspection and analysis Create an analysis report on Trace to analyze user requests

Configure GKE workload metrics using kubect1 Select all Pods to send their metrics to Cloud Monitoring. Create a custom dashboard of application metrics in Cloud Monitoring to determine performance bottlenecks of your GKE cluster

Install tcpdump on your GKE nodes. Run tcpdump to capture network traffic over an extended period of time to collect data Analyze the data files using Wireshark to determine the cause of high latency

Update your microservices to log HTTP request methods and URL paths to STDOUT Use the logs router to send container logs to Cloud Logging Create filters in Cloud Logging to evaluate the latency of user requests across different methods and URL paths.

Answer

Questions # 17:

Your service adds text to images that it reads from Cloud Storage. During busy times of the year, requests to

Cloud Storage fail with an HTTP 429 "Too Many Requests" status code.

How should you handle this error?

Options:

Add a cache-control header to the objects.

Request a quota increase from the GCP Console.

Retry the request with a truncated exponential backoff strategy.

Change the storage class of the Cloud Storage bucket to Multi-regional.

Answer

Explanation

[Reference: https://developers.google.com/gmail/api/v1/reference/quota]

Questions # 18:

You are creating and running containers across different projects in Google Cloud. The application you are developing needs to access Google Cloud services from within Google Kubernetes Engine (GKE).

What should you do?