Google Cloud · 2026 Edition
A complete preparation guide written by Google Cloud-certified engineers. Covers the exam format,all 6 blueprint domains, a week-by-week study plan, and proven tips for passing first time.
3–5 months
Prep time
Advanced
Difficulty
60
Exam questions
720/1000
Pass mark
Exam code
PCDOE
Full name
Google Professional Cloud DevOps Engineer
Vendor
Google Cloud
Duration
120 minutes
Questions
60 items
Passing score
720/1000 (scaled)
Domains covered
6 blueprint domains
Recommended experience
3+ years of industry experience including 1+ year as a Cloud DevOps Engineer or SRE
Typical prep time
3–5 months
The Professional Cloud DevOps Engineer certification validates the ability to apply SRE principles, build and manage CI/CD pipelines, and implement observability on Google Cloud. It is the credential expected for platform engineering and SRE roles at GCP-heavy organisations.
Job roles this opens
Domain percentage weights are not currently available for this exam. The checklist below is still useful for planning your study.
Weeks 1–3
SRE Principles: SLIs, SLOs, error budgets, toil reduction, capacity planning
Tip: Error budgets are central to the DevOps Engineer exam. Know that an error budget = 1 - SLO (e.g. 99.9% SLO gives 0.1% error budget). When the error budget is exhausted, teams pause feature releases and focus on reliability. This decision framework is tested in scenario questions.
Weeks 4–6
CI/CD Pipelines: Cloud Build, Cloud Deploy, Artifact Registry, Skaffold
Tip: Google Cloud Deploy is the managed continuous delivery service. Know how it defines delivery pipelines with stages (dev → staging → prod), how it promotes releases between stages, how approval gates work for production promotion, and how rollback is triggered automatically when a deployment fails a canary analysis.
Weeks 7–9
Service Monitoring and Observability: Cloud Monitoring, Cloud Logging, Cloud Trace, Cloud Profiler
Tip: Cloud Monitoring uptime checks, alerting policies, and custom metrics are tested. Know the difference between a Metric Threshold alert (fires when a metric exceeds a value) and a Metric Absence alert (fires when a metric stops reporting — often indicates a service has crashed).
Weeks 10–13
Optimising Service Performance: bottleneck analysis, caching, traffic management, GKE optimisation
Tip: Cloud Profiler continuously profiles CPU and memory usage of production applications with minimal overhead. Know that it provides flame graphs showing where execution time is spent, and that it can identify specific functions consuming disproportionate resources without requiring code changes.
Cloud Build triggers are the CI entry point: know how to trigger builds on push to a branch, on pull request creation, and on tag creation. Cloud Build substitution variables (like $BRANCH_NAME, $COMMIT_SHA) are used to parameterise build steps.
Binary authorisation enforces that only trusted container images are deployed to GKE or Cloud Run. Know how it uses attestation (cryptographic proof that an image passed a policy check like a vulnerability scan) to control what can be deployed in production.
GKE release channels (Rapid, Regular, Stable) control when a cluster receives new Kubernetes versions. Know that Rapid gets new features first but least tested; Stable gets fully validated versions. The DevOps Engineer exam tests scenarios about upgrade risk management.
Toil is a key SRE concept: manual, repetitive, automatable work that grows with service traffic. The DevOps Engineer exam tests scenarios where you are asked how to reduce toil — the answer is always automation (Runbooks converted to Cloud Functions, Error Budget Policies, automated remediation via Pub/Sub and Cloud Functions).
Canary deployments on Cloud Deploy use Skaffold profiles and Cloud Run traffic splitting or GKE traffic routing to gradually shift traffic. Know how a canary analysis (using Cloud Monitoring metrics) automatically promotes or rolls back a canary based on success criteria.
Apply everything in this guide with adaptive practice questions, detailed answer explanations, and domain analytics.
Deep-dive explanations of the key topics tested on PCDOE — with exam key points and common misconceptions.