Professional Cloud DevOps Engineer: delivery and reliability
Prepare for Professional Cloud DevOps Engineer with eight lessons, 50 questions, and eight cases on pipelines, SRE, observability, identity, and costs.
Objectives and progression
Eight lessons with guided application, 50 questions, and eight original cases. Internal assessment of 32 decisions in 60 minutes. Fictional banking operations examples connect platform, change, observability, and business outcomes. Initial coverage without executable labs or exhaustive treatment of ML pipelines, fleets, and every product objective. Current Google-linked guide inspected 2026-09-30; edition date not stated. Five approximate weights: 20/25/18/25/12. Exam of 50–60 items in 120 minutes, in English and Japanese. A public numerical passing threshold is unconfirmed.
Audience: DevOps, SRE, platform engineers, and APS professionals responsible for Google Cloud changes and operations.
Prerequisites: Linux, networking, IAM, container, and pipeline experience. No formal certification prerequisite; practical Google Cloud experience recommended.
370 estimated study minutes
- Bound projects, networking, and observability by responsibilities and classification.
- Connect IaC code, plan, execution, and observed state.
- Promote evaluated artifacts with explicit configuration and decisions.
- Limit credentials and connect build evidence with admission.
- Use user outcomes to decide mitigation, change, and capacity.
- Distinguish emission, processing, routing, and storage.
- Interpret scope, cardinality, intervals, and missing data.
- Compare cost per outcome and protect critical periods.
Modules
- Organization, identity, and visibility
- Infrastructure, revisions, and environments
- Pipelines, promotion, and recovery
- Identities, secrets, and supply chain
- SRE, error budgets, and incidents
- Logs: collection and routing
- Metrics, traces, and populations
- Performance, FinOps, and deadlines
Continue learning
- Professional Cloud Developer
- Professional Cloud Architect
- CI/CD
- Monitoring and Observability
- Production Support L3
References and version
Current linked guide; edition date unconfirmed (2026-09-30 inspection)
- Google Cloud certification FAQs · 2026-09-30
- Well-Architected Framework · 2026-09-30
- Resource hierarchy · 2026-09-30
- IAM overview · 2026-09-30
- Workload Identity Federation · 2026-09-30
- Binary Authorization overview · 2026-09-30
- Cloud Deploy canary strategy · 2026-09-30
- Secret Manager best practices · 2026-09-30
- Cloud Build provenance · 2026-09-30
- Artifact Registry image names · 2026-09-30
- Cloud Build default service account changes · 2026-09-30
- Gemini Code Assist Standard and Enterprise · 2026-09-30
- Cloud Run service autoscaling · 2026-09-30
- GKE Horizontal Pod Autoscaler · 2026-09-30
- Kubernetes probes · 2026-09-30
- Cloud SQL connection management · 2026-09-30
- Spot VMs · 2026-09-30
- Cloud Billing budgets · 2026-09-30
- Service level objectives · 2026-09-30
- Disaster recovery planning · 2026-09-30
- Shared VPC · 2026-09-30
- Professional Cloud DevOps Engineer certification · 2026-09-30
- Professional Cloud DevOps Engineer exam guide · 2026-09-30
- Cloud Logging routing and sinks · 2026-09-30
- Logs-based metrics · 2026-09-30
- Monitoring multiple projects · 2026-09-30
- Alerting on SLOs · 2026-09-30
- Infrastructure Manager overview · 2026-09-30
- Ops Agent configuration · 2026-09-30
- Structure of time series · 2026-09-30
- Cloud Deploy release promotion · 2026-09-30
- DORA software delivery performance metrics · 2026-09-30
- Eliminating toil · 2026-09-30
- Traces and spans · 2026-09-30
What you will explore
0 / 8Organization, identity, and visibility
Bound projects, networking, and observability by responsibilities and classification.
Infrastructure, revisions, and environments
Connect IaC code, plan, execution, and observed state.
Pipelines, promotion, and recovery
Promote evaluated artifacts with explicit configuration and decisions.
Identities, secrets, and supply chain
Limit credentials and connect build evidence with admission.
SRE, error budgets, and incidents
Use user outcomes to decide mitigation, change, and capacity.
Logs: collection and routing
Distinguish emission, processing, routing, and storage.
Metrics, traces, and populations
Interpret scope, cardinality, intervals, and missing data.
Performance, FinOps, and deadlines
Compare cost per outcome and protect critical periods.