Google CloudOctober 14, 202614 min read

Am I Ready for GCP Cloud DevOps Engineer? Checklist (2026)

Tick what you can do today, without notes. The board scores you against the Google Cloud outline and says GO, HOLD or NO-GO before you spend US$200 + tax on a booking.

  • 50-60Questions
  • 2 hoursTime
  • Not publishedPass mark
  • US$200 + taxFee
  • Pearson VUEDelivery
GCP Cloud DevOps Engineer exam readiness checklist - go / no-go board

The Professional Cloud DevOps Engineer exam is for the people who build delivery pipelines and keep production services healthy on Google Cloud: platform engineers, SREs and DevOps leads. Google recommends three or more years of industry experience, including at least one year designing and managing production systems on Google Cloud. The current exam guide is broad, running from organisation setup and infrastructure as code through CI/CD, SRE practice and observability to cost, and it now names AI assistants such as Gemini Cloud Assist alongside the usual tools.

Ready means you can pick the Google-recommended option under time pressure: the keyless way to authenticate a pipeline, the rollout that limits blast radius, the alert that fires on error-budget burn rather than raw CPU. Google publishes no pass mark, so the checklist below is weighted by the exam guide's section percentages. Tick only what you have done or could do now without notes.

How to use this checklist

Tick only what you can do today, without notes. Each tick is weighted by its domain's share of the official outline, so the score follows the exam, not the number of boxes. A heavy domain (15%+ of the weight) at NO-GO holds the verdict even when the total looks fine. Your ticks are saved in this browser only.

GO · 85%+Book the exam. Use the countdown below to finish.
HOLD · 60-84%Close. Spend one or two weeks on the amber domains, then re-check.
NO-GO · under 60%Not yet. Booking now mostly buys a retake.

The GCP Cloud DevOps Engineer readiness checklist

22 items across 5 domains, each one a thing the exam expects you to do rather than recognise.

01Bootstrapping and maintaining a Google Cloud organization~20%
02Building and implementing CI/CD pipelines, including continuous testing, for application, infrastructure, and ML workloads~25%
03Applying site reliability engineering practices~18%
04Implementing observability practices and troubleshooting issues~25%
05Optimizing performance and cost~12%

Your go / no-go board

One lamp per domain, one verdict overall. Amber and red rows are your study plan for the next week or two.

GCP DevOps Engineer readiness
0%
NO-GO
Tick the items you can do today. The board updates as you go.
0NO-GO60 HOLD85 GO100
Bootstrapping and maintaining a Google Cloud…~20%0/5NO-GO
Building and implementing CI/CD pipelines…~25%0/5NO-GO
Applying site reliability engineering…~18%0/4NO-GO
Implementing observability practices and…~25%0/5NO-GO
Optimizing performance and cost~12%0/3NO-GO
Rule of thumb, not an official score. Confirm with a timed practice test.

Check your ticks under exam conditions

A tick is a claim; a timed set of questions is the evidence. ExamCert AI has 500+ exam-style GCP Cloud DevOps Engineer questions with an explanation for every option. Do a mixed set and see whether the domains you ticked hold up.

Practise on ExamCert AIFree GCP Cloud DevOps Engineer practice test

Red flags: don't book yet if...

Any one of these on the GCP Cloud DevOps Engineer is a better predictor of a fail than a low tick count.

NO-GO IF

You have never defined an SLO or watched an error budget burn

SRE practice is about 18% of the exam on its own, and SLO-based alerting reappears in the observability section. The questions follow Google's SRE model, not general DevOps habits.

Fix:Set an availability SLO on a small Cloud Run or GKE service, add a burn-rate alert, then break the service and watch the budget move.

NO-GO IF

Cloud Deploy and Binary Authorization are names to you, not tools

Pipeline questions ask where each step belongs: build, scan, attest, promote, approve. That ordering is hard to guess if you have not wired it up.

Fix:Build one pipeline end to end in a sandbox: Cloud Build to Artifact Registry to Cloud Deploy, with an approval gate and a Binary Authorization policy.

NO-GO IF

Your first instinct is to download a service account key

The exam favours keyless options such as attached service accounts, Workload Identity Federation and Secret Manager. Exported keys are a classic wrong answer.

Fix:For every pipeline and workload in your notes, write down how it authenticates without a key file, and why that option is safer.

NO-GO IF

Your observability experience stops at default dashboards

Observability and troubleshooting are about 25% of the exam: query filters, log sinks, log-based metrics, traces and alert policies, not just reading a chart.

Fix:Practise writing Logging query language filters, build a log-based metric and alert from scratch, and route a log sink to BigQuery.

NO-GO IF

You have not run production systems on Google Cloud

Google recommends at least one year designing and managing production systems on Google Cloud. Scenarios assume you know what breaks in real deployments.

Fix:If you are short of that, add lab weeks that simulate production: rollouts that fail, quota limits, noisy logs and an incident you have to roll back.

The numbers that say you're ready

Rules of thumb, not official thresholds: Google Cloud does not publish a readiness score. Hit all four before you pay for a booking.

Timed practice score80%+ on two unseen full-length sets

A rule of thumb, not an official threshold. Google publishes no pass mark, so a clear margin on questions you have not seen is the safest proxy.

Pace60 questions in about 100 minutes

Rule of thumb: two hours for up to 60 questions is two minutes each. Finishing early leaves time for long pipeline and incident scenarios you flagged.

Error budget maths99.9% over 30 days is about 43 minutes, done in your head

Rule of thumb: if converting an SLO into allowed downtime or failed requests takes you more than a few seconds, SRE questions will eat your time.

End-to-end buildOne pipeline plus one SLO alert built by you

Rule of thumb: building a pipeline and an SLO alert yourself covers the two largest sections in practice, not just in theory.

Booking and ID checklist

The logistics that trip people up are specific to the GCP Cloud DevOps Engineer and its delivery provider. Work through them in order.

STEP 014-6 weeks out

Create or update your CM Connect profile

Register from the exam page, which takes you to CM Connect (Certmetrics). Your legal first and last name must match your government photo ID and be in Romanized characters, or Pearson cannot schedule you.

STEP 024-6 weeks out

Choose test centre or online

Under Schedule/Launch an Exam, pick a Pearson VUE test centre or OnVUE online proctoring, then English or Japanese. CM Connect signs you into Pearson automatically; no separate Pearson account is needed.

STEP 034-6 weeks out

Pay the US$200 fee

Pay by card, voucher or coupon code at checkout; tax is added where applicable. The price is the same for test centre and online delivery.

STEP 043-5 weeks out

Request accommodations before scheduling

Accommodations are requested in CM Connect and must be approved before you can schedule. Google allows 5-7 business days for review, and arranging them can take up to 30 days for a test centre.

STEP 0524+ h before

Run the OnVUE system test

For online exams, Google asks you to run Pearson's system test and download the OnVUE application at least 24 hours ahead, on the same computer and network you will use.

STEP 0624+ h before

Reschedule or cancel in time

Changes made 24 hours or more before the start are free. Inside 24 hours a late fee applies, and a voucher can only be reused if you cancel before that window.

STEP 07Exam day

Bring the right ID and arrive on time

Test centre: arrive 15 minutes early with two IDs, one a government-issued photo ID. Online: launch from 10 minutes before to 20 minutes after the start time, or the fee is forfeited.

Exam-week countdown: T-7 to T-0

T-77 days out

Sit a full timed practice set in two hours. Re-tick this checklist and give the week to whichever of pipelines or observability is weaker, since together they are about half the exam.

T-33 days out

Online: rerun the OnVUE system test on your exam computer and network. Test centre: confirm the address and travel time. Decide now if you need to move the date; free changes end 24 hours before.

T-1Day before

Light review only: deployment strategies, keyless authentication options and SLO and error-budget maths. Check that your CM Connect name matches your ID, and clear the room if testing online.

T-0Exam day

Eat and use the bathroom first, because no breaks are allowed. Online, launch from 10 minutes before your slot; at a test centre, arrive 15 minutes early with both IDs.

Test-day rules

✓ Allowed / expected

  • A government-issued photo ID whose name matches CM Connect exactly, plus a second signed ID at a test centre
  • Only your computer on the desk for an online exam, in a quiet, well-lit room you can show in a room scan
  • Approved accommodations, such as an authorised break, arranged in CM Connect before you schedule
  • Switching between online and test centre delivery if you cancel 24 or more hours ahead and rebook

✕ Not allowed

  • Breaks of any kind: taking one cancels the session and Google rejects the result
  • Scratch paper, pens, notes, phones, smart watches, external monitors, food or drink in an online session
  • Reading questions aloud, talking to anyone, or leaving the camera's view
  • Other people in the room, or photographing the provisional result before closing the secure browser

After you pass

Provisional result, then confirmation

A provisional pass or fail appears on screen when you submit and later in CM Connect. Google reviews the exam record against its terms and confirms the official result within 7-10 days.

Certificate and badge

Once the result is verified, Google issues a digital certificate and badge. Badges sit in the Google Cloud credential wallet run by Credly, which emails you instructions to claim yours.

Renewal every two years

Professional certifications last two years. Renewal opens 60 days before your inactive date and, for this certification, means passing the exam again; a 50% renewal discount code is waiting in CM Connect.

The GCP Cloud DevOps Engineer at a glance

ItemDetail
Questions50-60 multiple choice and multiple select questions
Time2 hours (the appointment adds about 15 minutes for check-in and agreements)
Passing scoreNot published; results are pass/fail only
FeeUS$200 plus tax where applicable
DeliveryPearson VUE test centre or Pearson OnVUE online proctoring, booked through CM Connect; English or Japanese
RetakesAfter a fail, wait 14 days; after a second fail, 60 days; after a third, 365 days. Maximum 4 attempts in 2 years
ResultsProvisional pass/fail on screen when you submit; Google confirms the official result in 7-10 days
Validity and renewal2 years; renew by passing the exam again, from 60 days before the inactive date (adds 2 years)

Turn the amber rows green

Work GCP Cloud DevOps Engineer questions by domain, starting with whatever the board marked HOLD or NO-GO, then tick again.

Practise on ExamCert AIFree GCP Cloud DevOps Engineer practice test

FAQ

What is the passing score for the Professional Cloud DevOps Engineer exam?

Google does not publish one. Results are pass or fail only, and you pass on your total across the whole exam rather than section by section. If you fail, CM Connect shows a breakdown by section with each section's approximate share of the exam, which is the best guide to what to fix before you retake after the 14-day wait.

How is the exam weighted?

The exam guide gives approximate weights: bootstrapping and maintaining an organisation about 20%, CI/CD pipelines about 25%, SRE practices about 18%, observability and troubleshooting about 25%, and performance and cost about 12%. Pipelines and observability together make up roughly half the exam, so weakness in either is a reason to wait. The guide now also covers ML pipelines and Gemini assistants.

How deep does my Kubernetes knowledge need to be?

You need working GKE knowledge rather than administrator depth: managing clusters across environments with fleets, autoscaling, rollout strategies, deploying through Cloud Deploy and collecting metrics with Managed Service for Prometheus. The exam is multiple choice, so you will not type kubectl commands, but scenarios assume you know how a GKE workload is deployed, scaled, observed and rolled back.

Can I take the exam online, and who runs it?

Yes. Google Cloud exams moved to Pearson in March 2026. You can test online through Pearson's OnVUE service or at a Pearson VUE test centre, at the same price. Online sessions need a private, clear room, a webcam room scan and no breaks. You register and launch through CM Connect, which passes you to Pearson without a separate account.

How do I renew the certification?

It is valid for two years. Renewal opens 60 days before your inactive date and, for this certification, means passing the exam again; Google offers continuing-education renewal for only a few other certifications so far. A pass adds two years. You get a 50% renewal discount code in CM Connect when you first certify, and you can still renew up to 30 days after the inactive date.

Sources

Figures on this page come from Google Cloud and the other primary sources below:

Checked October 14, 2026. Fees, outlines and eligibility rules change — confirm with Google Cloud before you book.