CloudExamCheap

PCDE Practice Exam: Professional Cloud DevOps Engineer

239 questions · 120 min timed mode · Google Cloud · Updated 2026

SRE on GCP: SLOs, error budgets, pipelines, and sleeping through the night.

What you'll be tested on

Sample PCDE questions

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?
  1. Instrument all applications with Stackdriver Profiler.
  2. Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.
  3. Use Stackdriver Debugger to review the execution of logic within each application to instrument all applications.
  4. 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.
Show answerB — Instrument all applications with Stackdriver Trace and review inter-service HTTP requests.
Stackdriver Trace (now Cloud Trace) is designed for distributed tracing: it captures latency data across inter-service HTTP requests, showing which downstream dependency contributes delay, so you can anticipate which dependent applications may cause performance issues. Profiler analyzes CPU and memory usage within a single process, not request flow between services. Debugger inspects live application state and code execution, not inter-service latency. Logging request times manually is possible but adds toil and lacks the automatic span correlation and latency breakdowns that Trace provides, so B is the best answer.
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?
  1. Share the workspace Project ID with the SRE team. Assign the SRE team the Monitoring Viewer IAM role in the workspace project.
  2. Share the workspace Project ID with the SRE team. Assign the SRE team the Dashboard Viewer IAM role in the workspace project.
  3. 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.
  4. 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.
Show answerC — 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.
The chart's Share chart by URL feature generates a link to just that specific chart, which is the narrowest resource you can share. Combining it with the Monitoring Viewer role in the workspace project lets the SRE team view monitoring data without granting editor or admin rights. Sharing only the Project ID (options A and B) does not give the team a direct way to view the chart itself. Dashboard Viewer is not the appropriate predefined role for viewing monitoring charts in this scenario; Monitoring Viewer provides the required view access while following least privilege, so C is correct.
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?
  1. Develop a postmortem that includes the root causes, resolution, lessons learned, and a prioritized list of action items. Share it with the manager only.
  2. 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.
  3. 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.
  4. 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.
Show answerB — 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.
SRE postmortems must be blameless and widely shared. A good postmortem documents root causes, resolution, lessons learned, and a prioritized list of action items, and sharing it on the engineering document portal maximizes organizational learning. Options C and D are wrong because naming responsible individuals and assigning per-person action items violates the blameless postmortem culture, which focuses on system and process failures rather than people. Option A has the right content but shares it only with the manager, limiting the learning benefit. Therefore B best follows SRE principles.

Access plans

AccessPrice
3 months$8.99$3.99
1 year$14.99$8.99
Lifetime$24.99$14.99
Practice PCDE now →
Free preview inside — try 5 questions before you pay anything.

FAQ

How many practice questions are in this PCDE bank?
239 questions covering the current PCDE Professional Cloud DevOps Engineer syllabus, every one with the correct answer and an explanation.
How long is the real PCDE exam?
The official PCDE exam gives you 120 minutes. Our timed exam mode uses the same limit so the pace feels familiar.
What does PCDE access cost?
Plans start at $3.99 for 3 months. One payment, no subscription — and far cheaper than retaking the real exam.