FirstTry

Certification guide

PCDE

Professional Cloud DevOps Engineer: the honest guide

Professional Cloud DevOps Engineer is half delivery pipeline and half site reliability practice. CI/CD and observability are 25 percent each, SRE practice is 18 percent, and bootstrapping a Google Cloud organization is 20 percent.

The SRE half is tested as Google defines it. Service level objectives, error budgets and toil have specific meanings in Google's books, and the exam uses those meanings rather than the looser industry versions.

Who Cloud DevOps Engineer is for

A good fit if

  • You run delivery pipelines or production services on Google Cloud.
  • You work in SRE or platform engineering and the vocabulary is already part of your job.
  • You are moving from a general DevOps role into one where reliability is measured rather than asserted.
  • Your organization needs certified staff for a Google Cloud partner specialization.

Probably not, if

  • You want an introduction to CI/CD. The exam assumes pipelines as background and asks about designing and securing them.
  • Your platform is not Google Cloud. The SRE half transfers; the tooling half does not.
  • You want a development credential. The developer certification covers building applications; this one covers delivering and operating them.

Is Cloud DevOps Engineer worth it?

For a platform or SRE engineer on Google Cloud, this is the best-matched certification available, and unusually its most heavily weighted material is covered by free sources Google itself wrote.

It is cheap to prepare for. Cloud Build and Artifact Registry have free allowances that cover study-scale work, and the SRE books cost nothing.

It is a poor purchase for somebody whose organization does not measure reliability. Half the value is a vocabulary for conversations your workplace may not be having, and a certificate does not start those conversations.

What the exam actually asks you to do

Multiple choice and multiple select, in Google's own words. No labs, no console access, and nothing to configure during the exam.

Item formats

  • Multiple choice
  • Multiple response

Nothing here needs a lab. Reading carefully and eliminating options is the whole skill. Google Cloud, Professional Cloud DevOps Engineer exam details ↗

Domain breakdown and official weightings

From the official Google Cloud exam guides. Building and implementing CI/CD pipelines, including continuous testing is the heaviest domain at 25 percent, followed by Implementing observability practices and troubleshooting issues at 25 percent.

  • Bootstrapping and maintaining a Google Cloud organization20%
  • Building and implementing CI/CD pipelines, including continuous testing25%
  • Applying site reliability engineering practices18%
  • Implementing observability practices and troubleshooting issues25%
  • Optimizing performance and cost12%

Where to focus: CI/CD and observability are 25 percent each, so half the exam sits in two sections that reward having actually built a pipeline and read a trace. Optimizing performance and cost is the smallest at 12 percent and the one most often skipped entirely.

Google Cloud: Google Cloud exam guides ↗

Study plans by experience level

SRE or platform engineer on Google Cloud

5 to 6 weeksat 6 hours

  1. 1Week 1: read the exam guide and mark what your organization does differently from Google's model, because the exam marks Google's.
  2. 2Weeks 2 to 3: CI/CD at 25 percent, including pipeline security and secret handling, which are the parts most teams do least well.
  3. 3Week 4: observability at 25 percent: metrics, logs, traces, dashboards and alerting policy design.
  4. 4Weeks 5 to 6: the organization bootstrapping section and cost optimization, then a full pass through the guide.

DevOps engineer from another platform

8 to 10 weeksat 8 hours

  1. 1Weeks 1 to 2: read Google's SRE material properly. The definitions are the exam's, and approximate versions cost marks.
  2. 2Weeks 3 to 5: Google's delivery tooling: Cloud Build, Artifact Registry, Cloud Deploy and the deployment targets.
  3. 3Weeks 6 to 8: Cloud Observability end to end, including trace and profiler, which have no exact equivalent everywhere.
  4. 4Weeks 9 to 10: resource hierarchy, environment management and infrastructure as code, then the guide.

Developer moving into platform work

10 to 12 weeksat 8 hours

  1. 1Weeks 1 to 3: the operations vocabulary. Availability targets, error budgets, incident response and what a postmortem is for.
  2. 2Weeks 4 to 6: pipelines beyond the build: environments, approvals, progressive delivery and rollback.
  3. 3Weeks 7 to 9: observability, with instrumentation added to something you wrote rather than to a sample.
  4. 4Weeks 10 to 12: organization structure, cost practice and a final pass through the exam guide.

Common mistakes

Using SRE vocabulary loosely
Service level objective, service level agreement and service level indicator are distinct in Google's model, and error budgets have a specific consequence. The exam tests those definitions directly, and industry-approximate usage is the most common source of lost marks.
Studying tools instead of pipeline design
The CI/CD section asks how a pipeline should be structured, secured and promoted across environments. Knowing the syntax of a build configuration does not answer a question about where a secret belongs or which environment gates a release.
Neglecting the observability section
It is 25 percent, equal largest, and it goes beyond dashboards into alert design, distributed tracing and log-based metrics. Engineers who have inherited monitoring rather than designed it usually find this the thinnest area.
Pointing a noisy workload at logging and leaving it
Cloud Observability bills by ingested volume with a monthly free allowance. It is the one meter on this curriculum that moves quietly, and a chatty test workload left running is how it gets exceeded.

What comes after passing

Two years of validity with a 60-day renewal window, the standard Google Professional cycle.

The post-pass discount code applies to a renewal attempt, which is worth diarising alongside the expiry date.

Professional Cloud Architect is the usual neighbour if design is becoming the job, and the security certification if pipeline and supply chain security is.

The durable value is the reliability vocabulary. Error budgets change how a team argues about shipping, and that is useful on any platform and in any tooling.

Costs across the full renewal cycle are on the Cloud DevOps Engineer cost page.

Frequently asked questions

How much of this exam is SRE theory?

Applying site reliability engineering practices is 18 percent directly, and the vocabulary colors the observability and CI/CD sections as well. Google's own SRE books are free online and are the source the exam's definitions come from, which makes them the highest-value preparation available.

Do I need to know Kubernetes?

Enough to deploy and operate workloads on GKE, yes. This is not a Kubernetes administration exam in the way CKA is, and questions center on delivery, environment management and observability rather than on cluster internals.

Can I prepare on the free tier?

Largely. Cloud Build and Artifact Registry carry free allowances that cover study-scale pipelines, and the SRE material costs nothing. Log and metric ingestion is the one place a study project can exceed a free allowance, and only if something noisy is left running.

How long is the certification valid?

Two years, with the renewal window opening 60 days before expiry. The SRE half of the curriculum ages slowly while the tooling half does not, so a renewal is mostly about what changed in the products.

Keep reading

Every guide and cost breakdown, by vendor

Practice Cloud DevOps Engineer for free while you decide

Original questions written from the published objectives, with the concept, the reasoning, and a note on every wrong option. No account needed to start.

Start free Cloud DevOps Engineer questions