Professional Cloud DevOps Engineer

Here you have the best Google Professional Cloud DevOps Engineer practice exam questions

You have 201 total questions to study from
Each page has 5 questions, making a total of 41 pages
You can navigate through the pages using the buttons at the bottom
This questions were last updated on November 5, 2025
This site is not affiliated with or endorsed by Google.

Question 1 of 201

You support a Node.js application running on Google Kubernetes Engine (GKE) in production. The application makes several HTTP requests to dependent applications. You want to anticipate which dependent applications might cause performance issues. What should you do?

Instrument all applications with Stackdriver Profiler.

Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.

Use Stackdriver Debugger to review the execution of logic within each application to instrument all applications.

Modify the Node.js application to log HTTP request and response times to dependent applications. Use Stackdriver Logging to find dependent applications that are performing poorly.

Correct Answer: B

To anticipate which dependent applications might cause performance issues in a Node.js application running on Google Kubernetes Engine (GKE) and making several HTTP requests, the best approach is to instrument all applications with Stackdriver Trace and review inter-service HTTP requests. Stackdriver Trace allows you to track the time taken by each service and identify bottlenecks, providing the most direct insight into performance issues related to HTTP requests among dependent applications.

Question 2 of 201

You created a Stackdriver chart for CPU utilization in a dashboard within your workspace project. You want to share the chart with your Site Reliability Engineering
(SRE) team only. You want to ensure you follow the principle of least privilege. What should you do?

Share the workspace Project ID with the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

Share the workspace Project ID with the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

Click ג€Share chart by URLג€ and provide the URL to the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.

Click ג€Share chart by URLג€ and provide the URL to the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.

Correct Answer: C

To grant the Site Reliability Engineering (SRE) team the least privilege necessary to view the specific Stackdriver chart for CPU utilization, you should use the 'Share chart by URL' feature and provide the URL to the SRE team. Additionally, assigning the SRE team the Monitoring Viewer IAM role in the workspace project will give them read-only access to the chart's data without granting them unnecessary permissions. This ensures they can view the chart without making configurations or accessing other data unrelated to their role.

Question 3 of 201

Your organization wants to implement Site Reliability Engineering (SRE) culture and principles. Recently, a service that you support had a limited outage. A manager on another team asks you to provide a formal explanation of what happened so they can action remediations. What should you do?

Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it with the manager only.

Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it on the engineering organization's document portal.

Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each person. Share it with the manager only.

Develop a postmortem that includes the root causes, resolution, lessons learned, the list of people responsible, and a list of action items for each person. Share it on the engineering organization's document portal.

Correct Answer: B

In Site Reliability Engineering (SRE) practices, transparency and shared learning are key components. Developing a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items, and then sharing it on the engineering organization's document portal ensures that the information is accessible to the broader team. This approach promotes a culture of continuous improvement and helps prevent similar issues in the future. By making postmortems widely available, organizations can learn from past incidents and improve their reliability practices as a whole.

Question 4 of 201

You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into production. This application is written by a third party and cannot be modified or reconfigured. The application writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver Logging. What should you do?

Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.

Deploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Stackdriver Logging.

Install Kubernetes on Google Compute Engine (GCE) and redeploy your applications. Then customize the built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver Logging.

Write a script to tail the log file within the pod and write entries to standard output. Run the script as a sidecar container with the application's pod. Configure a shared volume between the containers to allow the script to have read access to /var/log in the application container.

Correct Answer: B

To send log entries from the application to Stackdriver Logging, deploying a Fluentd daemonset to GKE is the appropriate solution. Fluentd is a highly customizable logging agent that can be configured to collect logs from specific files within your application's pods, including logs not written to standard output (stdout) or standard error (stderr). In this case, you can create a customized input configuration for Fluentd to tail the /var/log/app_messages.log file and an output configuration to forward these logs to Stackdriver Logging. This approach allows you to handle the log files without modifying the application, which is a necessary constraint.

Question 5 of 201

You are running an application in a virtual machine (VM) using a custom Debian image. The image has the Stackdriver Logging agent installed. The VM has the cloud-platform scope. The application is logging information via syslog. You want to use Stackdriver Logging in the Google Cloud Platform Console to visualize the logs. You notice that syslog is not showing up in the "All logs" dropdown list of the Logs Viewer. What is the first thing you should do?

Look for the agent's test log entry in the Logs Viewer.

Install the most recent version of the Stackdriver agent.

Verify the VM service account access scope includes the monitoring.write scope.

SSH to the VM and execute the following commands on your VM: ps ax | grep fluentd.

Correct Answer: D

You should SSH to the VM and execute the commands to check if the agent is running. The first step in troubleshooting why the syslog is not appearing in the Logs Viewer is to confirm that the Stackdriver Logging agent (fluentd) is operational. If the agent isn’t running, it won’t be able to collect and send logs to Stackdriver. Therefore, confirming the agent’s status should be the initial action to take.