Google Cloud Professional Cloud DevOps Engineer
225 practice questions
Last reviewed: April 2026
Personal notes and resource links for your study journey
Filter by Certification
The Google Cloud Professional Cloud DevOps Engineer (PCDOE) validates the ability to apply Google's site-reliability engineering (SRE) principles to production services on Google Cloud. The exam blends classic DevOps content (CI/CD with Cloud Build and Cloud Deploy, GitOps, Artifact Registry, IaC with Terraform) with Google's distinctive SRE framing — SLOs, SLIs, error budgets, toil reduction, postmortem culture. It also covers the full Cloud Operations suite (Logging, Monitoring, Trace, Profiler, Error Reporting), GKE day-two operations, and FinOps. PCDOE is the GCP analog of AWS DevOps Engineer Professional and Azure AZ-400 — closer in spirit to the Google SRE book than to a tooling-focused DevOps cert.
Resource hierarchy, organization policies, baseline IAM, network and security guardrails, IaC with Terraform and Cloud Foundation Toolkit. 20%.
Largest domain at 23%. Cloud Build, Cloud Deploy, Skaffold, Artifact Registry, deployment strategies (blue-green, canary, rolling), GitOps with Config Sync. Heavy on pipeline-design scenarios.
Tied for largest domain at 23%. SLI / SLO / error-budget design, toil identification and reduction, capacity planning, on-call practices, postmortems. Reads directly from the Google SRE book.
Cloud Logging routing and sinks, log-based metrics, Cloud Monitoring dashboards and alerting, Cloud Trace, Cloud Profiler, Error Reporting. 22%.
Smallest domain at 12% but high-density. GKE rightsizing, Compute Engine machine families, FinOps with Active Assist and Recommender, autoscaling tuning.
Services you'll encounter on the exam and why each one matters.
Managed CI service that runs builds, tests, and container images on Google-hosted workers driven by a declarative cloudbuild.yaml.
Why it's on the exam: Domain 2 (CI/CD Pipelines) names Cloud Build as the canonical PCDOE-native build runner — substrate for image bakes, attestation, and pipeline triggers.
Managed continuous-delivery service that promotes container images through ordered GKE / Cloud Run targets with approvals and rollback.
Why it's on the exam: Domain 2 tests progressive-delivery patterns (canary, blue/green) — Cloud Deploy is the AWS-CodeDeploy-equivalent answer on GCP.
Unified registry for Docker, Helm, Maven, npm, Python, Go, and OS packages with VPC-SC isolation and vulnerability scanning.
Why it's on the exam: Domain 2 + Domain 5 emphasize artifact provenance and vulnerability scanning — Artifact Registry is the supply-chain endpoint and image source for Cloud Deploy.
Managed Git hosting integrated with Cloud Build triggers, Cloud Logging, and Cloud Identity IAM for source-control workflows.
Why it's on the exam: Domain 2 expects an integrated source-of-truth for Cloud Build triggers and Cloud Deploy releases — CSR is the AWS-CodeCommit equivalent.
Managed Kubernetes with Standard and Autopilot modes, regional control planes, multi-cluster ingress, and managed node-pool upgrades.
Why it's on the exam: Domain 3 (SRE Practices) and Domain 4 (Observability) hinge on GKE — workload deployment, SLO-aware autoscaling, and rolling upgrades are all GKE-centric.
GitOps configuration controller that syncs declarative cluster state (Kustomize, Helm, Config Sync) and enforces Policy Controller (OPA Gatekeeper) constraints across fleets.
Why it's on the exam: Domain 1 (Bootstrapping a Google Cloud organization) and Domain 3 (SRE Practices) test GitOps and policy-as-code — ACM is the named GCP answer.
Kubernetes add-on that manages GCP resources (BigQuery datasets, Pub/Sub topics, IAM bindings) as CRDs reconciled from cluster manifests.
Why it's on the exam: Domain 1 tests declarative infra in GitOps form — Config Connector lets platform teams ship GCP provisioning alongside workloads under the same kubectl apply.
HashiCorp Terraform with the official google + google-beta providers, plus Cloud Foundation Toolkit modules and the Terraform-validator policy library.
Why it's on the exam: Domain 1 names Terraform as the de-facto IaC tool for landing zones, projects, networks, and IAM — PCDOE expects fluency with module structure and state strategy.
Serverless container runtime (request- or event-driven) with revisioned traffic splitting, sidecars, and managed mTLS via Cloud Service Mesh.
Why it's on the exam: Domain 2 tests progressive delivery for stateless services — Cloud Run revisions + traffic splits are the canonical canary primitive.
Event-driven serverless compute (HTTP and Eventarc triggers) for lightweight glue between Pub/Sub, Cloud Storage, and Firestore.
Why it's on the exam: Domain 4 (Observability) cites Functions as the substrate for incident-response automation and event-driven runbooks.
Serverless orchestration that chains Google Cloud APIs and HTTP endpoints with retries, parallel steps, and structured error handling.
Why it's on the exam: Domain 4 expects automated remediation — Workflows is the AWS-Step-Functions-equivalent for incident-response and multi-service rollback playbooks.
Fully managed task-queue service with rate-limiting, deduplication, and HTTP / App Engine targets for asynchronous, exactly-once work.
Why it's on the exam: Domain 5 (Performance and Cost) tests load-shedding patterns — Cloud Tasks decouples bursty producers from rate-limited consumers and dampens cost spikes.
GKE operating mode where Google manages nodes, autoscaling, and node-pool sizing — billed per-pod with SLA-backed availability.
Why it's on the exam: Domain 5 names Autopilot as the cost/operational-toil trade for teams that want SRE-grade reliability without managing node pools.
Logical grouping of multiple GKE clusters across projects, regions, and on-prem with fleet-wide feature enablement (Config Sync, Policy Controller, Identity).
Why it's on the exam: Domain 1 + Domain 3 test multi-cluster operations — Fleets are the unit of policy and identity propagation for platform teams managing many clusters.
Open-source multi-cloud continuous-delivery platform with native GKE / Cloud Run support, manual-judgment stages, and automated canary analysis.
Why it's on the exam: Domain 2 contrasts Cloud Deploy (managed, opinionated) with Spinnaker (self-hosted, multi-cloud) — knowing when each fits is a recurring PCDOE distinction.
Google Cloud IAM with conditional bindings, plus Workload Identity that federates GKE / external pods to Google service accounts without long-lived keys.
Why it's on the exam: Domain 1 + Domain 3 hinge on keyless authentication — Workload Identity is the canonical way pipelines and pods assume GCP identities under least privilege.
Integrated observability stack — Cloud Logging for log aggregation, Cloud Monitoring for metrics and alerts, Cloud Trace for latency, and Cloud Profiler for continuous CPU/heap sampling.
Why it's on the exam: Domain 4 (Observability and Troubleshooting) is the entire reason this suite exists; PCDOE expects fluent use of MQL, log-based metrics, and uptime checks.
Error Reporting aggregates and groups stack traces from Cloud Logging into actionable issues; Cloud Debugger captures application state from running production code without redeploys.
Why it's on the exam: Domain 4 tests live-incident triage — Error Reporting catches regressions, Debugger inspects state without forcing a rollback.
Native SLO definitions on Service Monitoring with rolling error-budget burn-rate alerts and budget-driven release-velocity policies.
Why it's on the exam: Domain 3 (SRE Practices) is built around SLIs/SLOs/error budgets — PCDOE expects candidates to translate user expectations into burn-rate alerting policy.
$135k–$185k–$280k USD annual
Range reflects US-based SRE and DevOps engineers where GCP is the primary platform. FAANG L5 SRE TC clears $300k+. Pure ops roles trend lower; senior SRE / production-engineer positions at digital-native GCP shops trend higher. The cert is a strong signal but pairs best with demonstrated production on-call experience.
Source: levels.fyi 2025–2026 (Google L4–L5 SRE, FAANG and GCP-shop unicorn senior platform engineers), U.S. BLS OEWS May 2024 (15-1244 network and computer systems administrators, 15-1252 software developers). Figures are approximate; actual compensation depends on role, region, and experience.
PCDOE demand has grown steadily as GCP's SRE-first culture exported to its customers. Heavy demand at digital-native GCP shops (Spotify, Snap, PayPal, several major retailers, gaming studios) where the SRE model is already adopted, and at Google Cloud partners building managed-services practices. The cert pairs naturally with Kubernetes CKA / CKAD and Terraform Associate to form a strong cloud-native SRE profile. Holders consistently report strong recruiter response on SRE and senior-platform-engineer roles. PCDOE also signals fluency in the Google SRE book, which is itself a hiring signal at companies that have adopted the SRE model.
There are no formal prerequisites. Google recommends three or more years of industry experience and one or more years designing and managing solutions on Google Cloud. In practice, PCDOE is not a credible first GCP cert — successful candidates have shipped production systems and held on-call rotations.
The Associate Cloud Engineer (ACE) is the most common stepping stone but is not strictly required if you already manage AWS or Azure production environments. Reading the Google SRE book ("Site Reliability Engineering") and the SRE Workbook is effectively part of preparation — many exam questions paraphrase passages directly. Comfort with Kubernetes (Deployments, Services, HPA, PodDisruptionBudgets), Terraform, and Cloud Build pipelines is required. The official DevOps Engineer Learning Path on Google Cloud Skills Boost (around 40–60 hours) covers the curriculum.
PCDOE is rated professional and is moderately hard — the SRE-specific content (SLOs, error budgets, toil) trips up traditional ops-focused candidates more than experienced site-reliability engineers. Plan on 80–130 hours of study over 8–12 weeks if PCDOE is your first GCP professional cert, or 40–70 hours over 4–6 weeks if you already hold ACE plus on-call SRE experience. The exam is 50–60 multiple-choice / multiple-select questions in 120 minutes, delivered through Pearson VUE (Google migrated from Kryterion / Webassessor in early 2026).
The most common stumbling block is the SRE-philosophy questions — Google's expected answer often hinges on subtle distinctions (when to spend error budget vs. when to freeze deploys, when toil reduction is worth automating vs. accepting). The second stumbling block is GKE production patterns, especially node-pool design, PodDisruptionBudgets, and Workload Identity. Google does not publish numeric scores — only pass/fail. The credential is valid for two years and recertification requires re-passing the current exam.
Current exam guide refreshed in late 2023 to add Cloud Deploy, Config Sync / GitOps coverage, and updated GKE Autopilot scenarios. Expanded SRE-philosophy domain weighting.
Major refresh that introduced Cloud Build as the primary CI surface and aligned the SLO / error-budget content with the SRE Workbook.
PCDOE (Google Cloud Professional Cloud DevOps Engineer) is a a challenging, scenario-heavy exam that requires deep hands-on experience and the ability to make architectural trade-off decisions Professional-level exam. Most candidates need 150–300 hours of study spread over 3–6 months for professional and expert-level exams. These exams typically expect prior associate-level proficiency. Most candidates who score consistently above the passing threshold on practice exams pass on their first attempt.
Most candidates need 150–300 hours of study spread over 3–6 months for professional and expert-level exams. These exams typically expect prior associate-level proficiency. Time-to-pass varies widely by prior experience. Engineers with hands-on production experience in the underlying technology typically need less; candidates new to the platform should plan toward the upper end of that range.
PCDOE is a recognized credential in the GCP ecosystem and signals validated knowledge to employers, recruiters, and clients. Whether it is worth the time and fee for you depends on your role and goals — it tends to pay off most for cloud engineers, architects, and consultants who work with GCP day-to-day or want to move into roles that do.
The passing score for PCDOE is Not published. The exam contains 50 questions and lasts 2 hr.
The PCDOE exam fee is $200 USD. Fees are set by GCP and may vary by region; always confirm the current price on the official GCP certification page before booking.
Google Cloud Professional certifications are valid for 2 years. Recertify by re-passing the current version of the exam.
Yes. You can take the exam online (proctored via the provider's secure browser, available 24/7 in most regions) or at an in-person Pearson VUE test center during business hours. Both formats use the same questions, time limit, and passing score.
CertLabPro provides 15 study modes across the practice question bank for PCDOE. The exam-simulation mode mirrors the real exam: 50 questions in 2 hr, with the same passing threshold of Not published. Browse mode lets you read every Q&A statically.