Why start with the exam itself
Before we touch a single gcloud command, it helps to know what you're up against. It's like reading the runbook before you go on call. This exam doesn't check whether you can recite flags from memory. It checks whether you can read a short scenario about a team on Google Cloud and pick the option a Google engineer would recommend. This level covers three things: where the official facts are kept, how the exam's five sections map onto this course, and a repeatable way to answer "best answer" questions.
Before we go further: this course is independent of Google. Google has not endorsed it, and nobody can promise you a pass. The syllabus we follow is Google's own document, the Professional Cloud DevOps Engineer exam guide. It's free on Google Cloud's certification page, and we don't reproduce it here. Download your own copy and keep it open.
Walkthrough 1: Find the official sources
The exam page for Professional Cloud DevOps Engineer is at cloud.google.com/learn/certification/cloud-devops-engineer. It links to the exam guide PDF, a learning path and sample questions.
# Get the official exam guide (Google's document, so always take it from Google)
curl -LO https://services.google.com/fh/files/misc/professional_cloud_devops_engineer_exam_guide_english.pdf
# Re-download it before you book: Google revises the guide, and new items
# (Gemini Cloud Assist, Parameter Manager and Dynamic Workload Scheduler are recent ones) can appear
At the time of writing, the exam page lists these details:
| Detail | Listed value (check it yourself) |
|---|---|
| Length | 2 hours |
| Format | 50–60 multiple choice and multiple select questions |
| Fee | $200 (plus tax where applicable) |
| Languages | English, Japanese |
| Delivery | Online-proctored (remote) or onsite-proctored at a testing center |
| Prerequisites | None (3+ years in industry recommended, including 1+ year designing and managing production systems on Google Cloud) |
Gotcha: treat that table as a snapshot only. Prices, languages, question counts and renewal rules change. On the day you book, the official exam page is the authority, not this course and not a blog post. Read the renewal and retake rules in Google's exam terms there too.
Walkthrough 2: The five sections and how this course splits them
The guide breaks the exam into five weighted sections. Plan your study time the same way you'd plan capacity: put the most effort where the most load is.
Section Weight Levels (approx.)
1 Bootstrapping and maintaining a Google Cloud organization ~20% ~10
2 Building and implementing CI/CD pipelines (incl. testing, ~25% ~13
for application, infrastructure and ML workloads)
3 Applying site reliability engineering practices ~18% ~9
4 Implementing observability practices and troubleshooting ~25% ~13
5 Optimizing performance and cost ~12% ~6
----- -----
100% 51 content levels + this one = 52
Sections 2 and 4 together make up about half the exam. If your weak spots are pipelines (Cloud Build, Cloud Deploy, Artifact Registry) or observability (Cloud Logging, Cloud Monitoring, tracing), fix those first. Section 5 is the smallest, but don't skip it: every question is still worth a point. We follow the guide's numbered items (1.1, 1.2 and so on) in order. Level 2 starts with item 1.1, resource hierarchy design.
Walkthrough 3: A method for "best answer" questions
Most questions describe a company, a constraint and four options that could all work. Your job is to pick the one that best meets the stated requirement. Here's a four-step method:
- Find the requirement words. Look for phrases like most secure, least operational overhead, lowest cost, minimize downtime or following Google-recommended practices. These words decide the question.
- Note the hard constraints. Examples: "must stay in the EU", "no code changes", "already uses Terraform".
- Rule out the distractors. Cross off options that break a constraint, solve a different problem, or rely on manual or self-managed work when a managed service exists.
- Pick the Google-recommended option that meets the requirement words, even if another option would also technically work.
Here's a worked example:
Scenario: A team runs builds on a self-hosted Jenkins VM. They want CI for
container images with the LEAST OPERATIONAL OVERHEAD.
A) Add more Jenkins agents on Compute Engine -> still self-managed: ruled out
B) Use Cloud Build, pushing images to Artifact Registry -> managed, native: BEST
C) Write a cron script on a VM that runs docker build -> more toil: ruled out
D) Run Jenkins on GKE with autoscaling -> works, but you still operate Jenkins
Swap the requirement word and the answer can change. If the scenario said "must reuse existing Jenkins pipelines with no rewrite", D becomes much stronger. The same applies to security. When an option says "download a service account key and store it in the CI tool" and another uses a keyless approach such as Workload Identity Federation, the keyless option is almost always the "most secure" answer.
Trade-off to keep in mind: in real life, the cheapest choice and the least-effort choice are often different. The exam knows this. Questions are hard because "lowest cost" might point to Spot VMs while "highest availability" points elsewhere. Answer the question that was asked, not the one you'd prefer.
Best practice: for multiple-select questions, the question tells you how many to choose. Check every option on its own against the requirement. Don't pick two because they "go together".
What the exam asks about this
Nothing in this level is scored directly. No question will ask what the exam costs. But the method in Walkthrough 3 comes up in every scored question. Practise it in every quiz from here on: underline the requirement words, cross off distractors, then choose.
Key takeaways
- The exam guide is Google's own free document on its certification page. This course follows it but doesn't reproduce it.
- Check the current length, format, fee, languages and delivery options on Google's official exam page before you book.
- This course is independent of Google, not endorsed by it, and can't guarantee a pass.
- The weights are ~20%, ~25%, ~18%, ~25% and ~12%. CI/CD and observability together are about half the exam.
- On every scenario question: find the requirement words, note the constraints, rule out the distractors, then pick the Google-recommended managed option.