- Exam Snapshot: Format, Fee, and Logistics
- Domain Breakdown at a Glance
- Domain 1: Bootstrapping the Organization
- Domain 2: CI/CD Pipelines
- Domain 3: SRE Practices
- Domain 4: Observability and Troubleshooting
- Domain 5: Performance and Cost
- Question Style and Format Cues
- Last-Week Review Schedule
- Who Hires CDE-Certified Engineers
- Renewal and Credential Lifecycle
- FAQ
- Exam has 50-60 questions in 2 hours, registered through Pearson for $200 plus tax.
- CI/CD Pipelines and Observability each account for roughly 25% of the exam - study these first.
- No prerequisites are enforced, but Google recommends 3+ years of experience with 1+ year on Google Cloud.
- Certification is valid for 2 years; renewal window opens 60 days before expiration and requires retaking the standard exam.
Exam Snapshot: Format, Fee, and Logistics
Before you memorize a single Cloud Build YAML flag, lock in the mechanics of the test itself. The Professional Cloud DevOps Engineer (CDE) exam is administered by Google Cloud through Pearson, and you can sit for it either online-proctored from home or onsite at a testing center. Registration costs $200 plus applicable tax, and that fee covers a single attempt - retakes require paying again.
The exam itself is tightly timed: 50-60 multiple-choice and multiple-select questions in 2 hours. That works out to roughly two minutes per question if you use the full window, though scenario-based items with multi-paragraph setups will eat more of your clock than straightforward recall questions. For a deeper walkthrough of scoring mechanics, see the CDE Passing Score guide, and if you're still mapping out your timeline, the CDE Exam Dates article covers scheduling windows and deadlines.
Domain Breakdown at a Glance
The CDE exam is organized into five domains, and the official weightings are approximate - Google is explicit that they're guidelines, not hard quotas. Still, they tell you exactly where to invest your study hours.
| Domain | Weight | Core Focus |
|---|---|---|
| 1. Bootstrapping and maintaining a Google Cloud organization | 20% | Org structure, IAM, resource hierarchy, policy |
| 2. Building and implementing CI/CD pipelines | 25% | App, infrastructure, and ML pipeline automation and testing |
| 3. Applying site reliability engineering practices | 18% | SLIs/SLOs, error budgets, incident response |
| 4. Implementing observability and troubleshooting | 25% | Logging, monitoring, tracing, root-cause analysis |
| 5. Optimizing performance and cost | 12% | Right-sizing, autoscaling, cost visibility |
Notice that Domains 2 and 4 are tied as the largest sections at roughly 25% each - together they represent half the exam. If you only have time to deep-dive two areas, make it these. For the full context behind each weighting and how Google frames the domain language, read the CDE Exam Domains Guide.
Domain 1: Bootstrapping and Maintaining a Google Cloud Organization
Domain 1 - 20% of the Exam
This domain tests whether you can stand up a Google Cloud organization correctly from day one and keep it governable as it scales.
- Resource hierarchy: organization, folders, projects, and how policies inherit downward
- IAM roles vs. custom roles, and least-privilege patterns for service accounts
- Organization policy constraints and how they differ from IAM permissions
- Infrastructure as Code patterns (Terraform, Config Connector) for repeatable environment setup
- Billing structure, folders-per-team patterns, and shared VPC design
Expect questions that describe a multi-team company and ask which resource hierarchy or IAM binding satisfies a stated constraint - these are rarely pure definition questions.
Domain 2: Building and Implementing CI/CD Pipelines
Domain 2 - 25% of the Exam (Tied Largest)
This is the single biggest content area, covering CI/CD for application code, infrastructure, and machine learning workloads - a broader scope than many candidates expect.
- Cloud Build, Cloud Deploy, and Artifact Registry pipeline stages
- Continuous testing strategies: unit, integration, canary, and progressive delivery
- Pipeline patterns for Terraform and other infrastructure automation
- ML-specific pipeline concerns: model versioning, retraining triggers, validation gates
- Rollback strategy design and blue/green vs. canary tradeoffs
Key Takeaway
Don't just memorize Cloud Build syntax - be ready to reason about *why* a given pipeline design includes a specific testing or approval gate. Questions test judgment, not just tool names.
Domain 3: Applying Site Reliability Engineering Practices
Domain 3 - 18% of the Exam
This domain draws directly from SRE fundamentals and expects fluency in the vocabulary and math behind reliability targets.
- Defining and measuring SLIs, setting realistic SLOs
- Error budgets and how they drive release velocity decisions
- Postmortem culture, blameless retrospectives, and incident severity classification
- Toil reduction and automation as an SRE responsibility
- On-call rotation design and escalation policies
If this domain feels abstract compared to the tool-heavy sections, that's normal - SRE questions tend to be conceptual and scenario-driven rather than "which command" style.
Domain 4: Implementing Observability Practices and Troubleshooting Issues
Domain 4 - 25% of the Exam (Tied Largest)
Tied with Domain 2 for the largest share, this section validates your ability to detect, diagnose, and resolve production issues using Google Cloud's operations suite.
- Cloud Monitoring: custom metrics, dashboards, alerting policies, and notification channels
- Cloud Logging: log-based metrics, log routing/sinks, and exclusion filters
- Cloud Trace and Cloud Profiler for latency and performance debugging
- Structuring logs and metrics for multi-service, distributed architectures
- Reading symptoms in a scenario and identifying the most likely root cause
Because Domains 2 and 4 combine for half the exam, candidates who underestimate observability often stumble even if their pipeline knowledge is solid. Troubleshooting scenarios frequently combine a monitoring alert, a log snippet, and a service dependency graph in a single question stem.
Domain 5: Optimizing Performance and Cost
Domain 5 - 12% of the Exam
The smallest domain by weight, but its concepts frequently resurface as secondary considerations inside Domain 1, 2, and 4 scenarios.
- Autoscaling policies for GKE, Compute Engine, and Cloud Run
- Right-sizing recommendations and committed use discounts
- Cost allocation via labels, billing exports, and budget alerts
- Balancing latency/performance requirements against spend constraints
Question Style and Format Cues
The CDE exam mixes multiple-choice (single answer) and multiple-select (choose two or more) items. A few patterns worth internalizing:
- Long scenario stems (2-4 sentences of company context) precede the actual question - read the last sentence first to know what's being asked, then work backward through the scenario.
- Distractors are often technically valid solutions that violate a stated constraint (cost, compliance, minimal downtime) buried in the scenario text.
- Multiple-select questions typically specify "choose two" or "choose three" - miscounting your selections is an easy, avoidable point loss.
- Several questions blend two domains at once - for example, a CI/CD pipeline question that also tests IAM permissions from Domain 1.
For a more exhaustive look at difficulty and how the question style compares to other Google Cloud certifications, see How Hard Is the CDE Exam? and the data-driven CDE Pass Rate analysis.
Last-Week Review Schedule
If you're using this cheat sheet in the final stretch before test day, sequence your remaining review around the weighting rather than reviewing domains in numerical order.
Domain 2 + Domain 4 (50% combined)
- Re-run CI/CD scenario questions covering app, infra, and ML pipelines
- Review Cloud Monitoring alerting policies and log-based metrics
Domain 1
- Drill resource hierarchy and IAM inheritance edge cases
- Revisit org policy constraints vs. IAM bindings
Domain 3
- Recalculate SLO/error budget examples until the math is automatic
- Review incident response and postmortem terminology
Domain 5 + Full Review
- Skim autoscaling and cost allocation concepts
- Take a full timed practice run and review misses
This sequencing isn't generic spaced repetition for its own sake - it's weighted deliberately so your final, most-retained review sits on the two domains worth the most points. For a full multi-week plan rather than just the final stretch, the CDE Study Guide walks through pacing from week one.
Who Hires CDE-Certified Engineers
The role title varies by company, but CDE-aligned job postings consistently ask for hands-on ownership across the software delivery lifecycle rather than a narrow specialty. Typical hiring patterns include:
- Platform and DevOps teams building internal CI/CD tooling on Google Cloud
- SRE teams responsible for SLOs, on-call rotations, and incident response
- Cloud infrastructure teams managing multi-project GCP organizations
- MLOps-adjacent teams that need pipeline automation for model deployment
Because the certification spans governance, delivery, reliability, and cost, it tends to appeal to hiring managers looking for a generalist who can move between infrastructure and application concerns. If you're evaluating whether this cert translates into better job prospects or compensation, the CDE Salary Guide and ROI analysis go deeper on that question, and CDE Jobs outlines common role titles and responsibilities.
Renewal and Credential Lifecycle
Once earned, the Professional Cloud DevOps Engineer certification is valid for 2 years. The renewal window opens 60 days before expiration, and as of now, renewal requires retaking the standard exam rather than a shortened recertification version. That means the fee structure and content scope for renewal mirror the original exam - budget for the same $200 plus tax registration and treat it as a full re-study cycle, not a formality.
Because Google Cloud services and best practices evolve quickly, this renewal cadence also functions as a built-in refresher - expect newer service features and updated tooling patterns to show up when you retest. For a complete cost breakdown including exam fees, prep materials, and renewal costs over time, see the CDE Certification Cost breakdown.
Key Takeaway
Mark your calendar 60 days before your certification's 2-year expiration date - that's when the renewal window opens and you should start re-registering for the standard exam.
Quick Terminology Clarifications
If you're new to the certification landscape and still orienting yourself around the acronym itself, a few companion resources clarify the basics before you dive into domain content: What Is CDE?, CDE Meaning, What Does CDE Stand For?, and What Is CDE Certification? all cover foundational definitions. For structured coursework beyond self-study, CDE Training outlines available options.
This cheat sheet is intentionally dense - bookmark it alongside the main practice test hub and use timed practice exams from CDE Exam Prep to validate that you can actually apply these facts under the 2-hour clock, not just recognize them on a page.
Frequently Asked Questions
The exam contains 50-60 multiple-choice and multiple-select questions, and you have 2 hours to complete it.
CI/CD Pipelines (Domain 2) and Observability and Troubleshooting (Domain 4) are tied as the largest sections at approximately 25% each, together making up half the exam.
No prerequisites are enforced. Google recommends 3+ years of industry experience, including 1+ year designing and managing production systems on Google Cloud, but anyone can register.
Registration costs $200 plus applicable tax. Google Cloud administers the exam through Pearson, available as online-proctored or onsite testing.
The certification is valid for 2 years. The renewal window opens 60 days before expiration, and renewal currently requires retaking the standard exam rather than a separate recertification exam.