Skip to content

Latest commit

 

History

History
253 lines (193 loc) · 12.1 KB

File metadata and controls

253 lines (193 loc) · 12.1 KB

🚀 Professional Cloud DevOps Engineer Exam Study Guide

Master DevOps practices and Site Reliability Engineering (SRE) on Google Cloud Platform.

This comprehensive guide prepares you for the Google Cloud Certified: Professional Cloud DevOps Engineer exam by covering CI/CD implementation, SRE principles, service monitoring, incident management, and service optimization.

Target Audience: DevOps engineers and SREs who implement processes and tools to manage, monitor, and operate reliable services on GCP.


📚 Table of Contents


🧭 Skills & Weights

Exam domains and their approximate weight:

  • Bootstrapping a Google Cloud Organization (~12%)
  • Building and Implementing CI/CD Pipelines (~20%)
  • Applying Site Reliability Engineering Principles (~18%)
  • Implementing Service Monitoring (~15%)
  • Optimizing Service Performance (~15%)
  • Managing Incidents (~20%)

Source: Google Cloud - Professional Cloud DevOps Engineer Exam Guide (skills measured as of 2026).


🧾 Exam Details

  • Duration: 2 hours
  • Format: 50-60 multiple choice and multiple select questions
  • Cost: $200 USD
  • Languages: English, Japanese, Spanish, Portuguese
  • Validity: 2 years
  • Prerequisites: Recommended 3+ years of industry experience, including 1+ year designing and managing GCP solutions
  • Exam Registration: Webassessor

🧩 Core Topics & Links

Deep dive into each exam domain with key concepts and resources.

1. Bootstrapping a Google Cloud Organization (~12%)

Key concepts:

  • Resource hierarchy: Organizations, folders, projects, resource management
  • IAM and security: Service accounts, workload identity, least privilege principles
  • Infrastructure as Code: Terraform, Cloud Deployment Manager, Config Connector
  • Billing and cost management: Budgets, alerts, cost allocation
  • Organizational policies: Constraints, policy inheritance

Resources:


2. Building and Implementing CI/CD Pipelines (~20%)

Key concepts:

  • Cloud Build: Build configurations, triggers, custom build steps
  • Cloud Deploy: Delivery pipelines, deployment strategies (canary, blue-green)
  • Artifact Registry: Container and package management
  • Source repositories: Cloud Source Repositories, GitHub, Bitbucket integration
  • Deployment strategies: Rolling updates, canary deployments, blue-green deployments
  • Testing: Unit tests, integration tests, smoke tests
  • Security scanning: Container vulnerability scanning, binary authorization

Resources:


3. Applying Site Reliability Engineering Principles (~18%)

Key concepts:

  • SLIs, SLOs, and SLAs: Defining and measuring service level indicators, objectives, and agreements
  • Error budgets: Calculating and managing error budgets
  • Toil reduction: Automating manual tasks, identifying toil
  • Capacity planning: Demand forecasting, resource provisioning
  • Blameless postmortems: Incident analysis, continuous improvement
  • Release engineering: Version control, rollback strategies

Resources:


4. Implementing Service Monitoring (~15%)

Key concepts:

  • Cloud Monitoring: Metrics, dashboards, uptime checks
  • Cloud Logging: Log-based metrics, log sinks, log analysis
  • Alerting: Alert policies, notification channels, alert strategies
  • APM and profiling: Cloud Trace, Cloud Profiler, Error Reporting
  • Custom metrics: Creating and exporting custom metrics
  • Monitoring best practices: Golden signals (latency, traffic, errors, saturation)

Resources:


5. Optimizing Service Performance (~15%)

Key concepts:

  • Performance tuning: Database optimization, caching strategies, CDN configuration
  • Auto-scaling: Horizontal and vertical scaling, autoscaling policies
  • Load balancing: Global and regional load balancers, backend service optimization
  • Resource optimization: Rightsizing, committed use discounts, preemptible VMs
  • Network optimization: CDN, Cloud Interconnect, Premium vs Standard network tiers
  • Cost optimization: Budget alerts, recommendations, cost analysis

Resources:


6. Managing Incidents (~20%)

Key concepts:

  • Incident response: On-call practices, escalation procedures, incident roles
  • Troubleshooting: Log analysis, distributed tracing, network troubleshooting
  • Communication: Status updates, stakeholder communication
  • Post-incident activities: Postmortems, action items, continuous improvement
  • Change management: Change windows, rollback procedures
  • Disaster recovery: Backup strategies, failover testing, RTO/RPO

Resources:


📚 Study Resources

🔗 Official Google Cloud Resources

📖 SRE Books

🧪 Hands-On Labs


🧠 Tips & Study Strategy

Preparation approach:

  1. Read the SRE books – Google's SRE books are essential reading for this exam
  2. Master SLIs/SLOs/SLAs – Understand how to define, measure, and manage service levels
  3. Hands-on CI/CD practice – Build real pipelines with Cloud Build and Cloud Deploy
  4. Learn monitoring tools deeply – Cloud Monitoring, Cloud Logging, Cloud Trace
  5. Practice incident management – Understand the full incident lifecycle
  6. Understand DevOps culture – Not just tools, but principles and practices
  7. Study error budgets – Know how to calculate and use them for decision-making
  8. Practice with real scenarios – Deploy applications, set up monitoring, respond to incidents

Common pitfalls to avoid:

  • ❌ Not reading the SRE books (they're free and heavily referenced)
  • ❌ Focusing only on GCP tools without understanding SRE principles
  • ❌ Not practicing with Cloud Build and Cloud Deploy
  • ❌ Overlooking the importance of communication in incident management
  • ❌ Not understanding the relationship between error budgets and release velocity

Study timeline:

  • DevOps experience + GCP knowledge: 6-8 weeks with 10-15 hours/week
  • Strong GCP but new to DevOps: 8-10 weeks with 15-20 hours/week
  • New to both: 12-16 weeks with 20+ hours/week

Key topics to master:

  • CI/CD: Cloud Build, Cloud Deploy, deployment strategies
  • SRE: SLIs, SLOs, SLAs, error budgets, toil reduction
  • Monitoring: Cloud Monitoring, Cloud Logging, alerting strategies
  • Incident Management: On-call practices, troubleshooting, postmortems
  • Optimization: Performance tuning, cost optimization, auto-scaling

Back to Student Resources