Google PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Exam
Professional Cloud DevOps Engineer (Page 3 )

Updated On: 12-Feb-2026

Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe incidents from happening in the future.
What should you do?

  1. Identify engineers responsible for the incident and escalate to their senior management.
  2. Ensure that test cases that catch errors of this type are run successfully before new software releases.
  3. Follow up with the employees who reviewed the changes and prescribe practices they should follow in the future.
  4. Design a policy that will require on-call teams to immediately call engineers and management to discuss a plan of action if an incident occurs.

Answer(s): B

Explanation:

The best way to prevent severe incidents from happening in the future is to ensure that test cases that catch errors of this type are run successfully before new software releases. This is aligned with the Site Reliability Engineering principle of testing for reliability.



Your team is designing a new application for deployment both inside and outside Google Cloud Platform (GCP). You need to collect detailed metrics such as system resource utilization. You want to use centralized GCP services while minimizing the amount of work required to set up this collection system.
What should you do?

  1. Import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis.
  2. Import the Stackdriver Debugger package, and configure the application to emit debug messages with timing information.
  3. Instrument the code using a timing library, and publish the metrics via a health check endpoint that is scraped by Stackdriver.
  4. Install an Application Performance Monitoring (APM) tool in both locations, and configure an export to a central data storage location for analysis.

Answer(s): A

Explanation:

The easiest way to collect detailed metrics such as system resource utilization is to import the Stackdriver Profiler package, and configure it to relay function timing data to Stackdriver for further analysis. This way, you can use centralized GCP services without modifying your code or setting up additional tools.



Your application images are built and pushed to Google Container Registry (GCR). You want to build an automated pipeline that deploys the application when the image is updated while minimizing the development effort.
What should you do?

  1. Use Cloud Build to trigger a Spinnaker pipeline.
  2. Use Cloud Pub/Sub to trigger a Spinnaker pipeline.
  3. Use a custom builder in Cloud Build to trigger a Jenkins pipeline.
  4. Use Cloud Pub/Sub to trigger a custom deployment service running in Google Kubernetes Engine (GKE).

Answer(s): B

Explanation:

https://cloud.google.com/architecture/continuous-delivery-toolchain-spinnaker-cloud https://spinnaker.io/guides/user/pipeline/triggers/pubsub/ The most efficient way to build an automated pipeline that deploys the application when the image is updated is to use Cloud Pub/Sub to trigger a Spinnaker pipeline. This way, you can leverage the built-in integration between GCR and Cloud Pub/Sub, and use Spinnaker as a continuous delivery platform for deploying your application .



You support a high-traffic web application that runs on Google Cloud Platform (GCP). You need to measure application reliability from a user perspective without making any engineering changes to it.
What should you do?
Choose 2 answers

  1. Review current application metrics and add new ones as needed.
  2. Modify the code to capture additional information for user interaction.
  3. Analyze the web proxy logs only and capture response time of each request.
  4. Create new synthetic clients to simulate a user journey using the application.
  5. Use current and historic Request Logs to trace customer interaction with the application.

Answer(s): D,E

Explanation:

The most effective ways to measure application reliability from a user perspective without making any engineering changes are to create new synthetic clients to simulate a user journey using the application, and to use current and historic Request Logs to trace customer interaction with the application. These methods can help you monitor the availability, latency, and errors of your application from an end-user perspective .



You support an application deployed on Compute Engine. The application connects to a Cloud SQL instance to store and retrieve dat

  1. After an update to the application, users report errors showing database timeout messages. The number of concurrent active users remained stable. You need to find the most probable cause of the database timeout.
    What should you do?
  2. Check the serial port logs of the Compute Engine instance.
  3. Use Stackdriver Profiler to visualize the resources utilization throughout the application.
  4. Determine whether there is an increased number of connections to the Cloud SQL instance.
  5. Use Cloud Security Scanner to see whether your Cloud SQL is under a Distributed Denial of Service (DDoS) attack.

Answer(s): C

Explanation:

The most probable cause of the database timeout is an increased number of connections to the Cloud SQL instance. This could happen if the application does not close connections properly or if it creates too many connections at once. You can check the number of connections to the Cloud SQL instance using Cloud Monitoring or Cloud SQL Admin API .






Post your Comments and Discuss Google PROFESSIONAL-CLOUD-DEVOPS-ENGINEER exam prep with other Community members:

Join the PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Discussion