Google Cloud Professional Cloud DevOps Engineer Guide

What does the Google Cloud Professional Cloud DevOps Engineer exam cover?

The Google Cloud Professional Cloud DevOps Engineer exam covers bootstrapping a Google Cloud organization and projects, building and implementing CI/CD pipelines, applying SRE practices including SLOs and error budgets, implementing service monitoring using Cloud Operations Suite, and optimizing service performance. The exam costs $200 USD.

---

The Google Cloud Professional Cloud DevOps Engineer certification validates expertise in implementing DevOps practices and Site Reliability Engineering (SRE) principles on GCP. This certification bridges development and operations by testing CI/CD pipeline design, observability, and reliability engineering.

The certification is unique among GCP professional certifications because it covers both technical implementation (Cloud Build, GKE pipelines) and operational philosophy (SLOs, error budgets, blameless postmortems).

---

Exam Overview

Detail	Information
Certification	Professional Cloud DevOps Engineer
Provider	Google Cloud
Number of Questions	50
Time Limit	2 hours
Passing Score	Not published
Cost	$200 USD
Prerequisites	ACE or PCA recommended
Validity	2 years

The exam covers five domains:

1. Bootstrapping a Google Cloud organization and projects (16%)
2. Building and implementing CI/CD pipelines (17%)
3. Applying SRE practices (26%)
4. Implementing service monitoring (20%)
5. Optimizing service performance (21%)

"This certification is heavily weighted toward SRE concepts — SLOs, error budgets, and the monitoring and alerting practices that operationalize them. Candidates who have read Google's SRE books and worked with Cloud Monitoring and Cloud Logging perform significantly better than those focusing exclusively on CI/CD tooling. The exam tests whether you think like an SRE, not just whether you can configure Cloud Build." -- GCP DevOps Engineer certified professional community

---

CI/CD with Cloud Build

Cloud Build Pipeline

# cloudbuild.yaml
steps:
  # Run unit tests
  - name: 'python:3.11'
    entrypoint: pip
    args: ['install', '-r', 'requirements.txt']
  
  - name: 'python:3.11'
    args: ['python', '-m', 'pytest', 'tests/']

  # Build Docker image
  - name: 'gcr.io/cloud-builders/docker'
    args:
      - build
      - '-t'
      - 'us-central1-docker.pkg.dev/$PROJECT_ID/my-repo/app:$COMMIT_SHA'
      - '.'

  # Push to Artifact Registry
  - name: 'gcr.io/cloud-builders/docker'
    args:
      - push
      - 'us-central1-docker.pkg.dev/$PROJECT_ID/my-repo/app:$COMMIT_SHA'

  # Deploy to Cloud Run
  - name: 'gcr.io/google.com/cloudsdktool/cloud-sdk'
    args:
      - gcloud
      - run
      - deploy
      - my-service
      - '--image=us-central1-docker.pkg.dev/$PROJECT_ID/my-repo/app:$COMMIT_SHA'
      - '--region=us-central1'

images:
  - 'us-central1-docker.pkg.dev/$PROJECT_ID/my-repo/app:$COMMIT_SHA'

Cloud Deploy for Progressive Delivery

Cloud Deploy manages delivery pipelines with promotion gates:

# clouddeploy.yaml
apiVersion: deploy.cloud.google.com/v1
kind: DeliveryPipeline
metadata:
  name: my-pipeline
spec:
  serialPipeline:
    stages:
      - targetId: dev-cluster
        profiles: [dev]
      - targetId: staging-cluster
        profiles: [staging]
        strategy:
          standard:
            verify: true    # Run verification job after deploy
      - targetId: prod-cluster
        profiles: [prod]
        strategy:
          canary:
            canaryDeployment:
              percentages: [10, 25, 50]
              verify: true

---

SRE Practices

Service Level Objectives

SLOs define reliability targets measured by Service Level Indicators (SLIs):

Defining SLOs in Cloud Monitoring:

# SLO configuration using Cloud Monitoring API
slo = {
    "displayName": "Availability SLO - 99.9%",
    "requestBasedSli": {
        "goodTotalRatio": {
            "goodServiceFilter": (
                'metric.type="run.googleapis.com/request_count" '
                'resource.type="cloud_run_revision" '
                'metric.label.response_code_class!="5xx"'
            ),
            "totalServiceFilter": (
                'metric.type="run.googleapis.com/request_count" '
                'resource.type="cloud_run_revision"'
            )
        }
    },
    "goal": 0.999,
    "rollingPeriod": "2592000s"  # 30 days
}

Error Budget Alerting

# Alert when error budget burn rate is too high
alertPolicy:
  displayName: "High Error Budget Burn Rate"
  conditions:
    - displayName: "5% error budget burned in 1 hour"
      conditionThreshold:
        filter: |
          select_slo_burn_rate("projects/PROJECT_ID/services/my-service/serviceLevelObjectives/my-slo", "3600s")
        comparison: COMPARISON_GT
        thresholdValue: 14.4    # Burns through 100% in ~7 hours at this rate
        duration: "0s"
  combiner: OR
  notificationChannels:
    - "projects/PROJECT_ID/notificationChannels/CHANNEL_ID"

---

Cloud Operations Suite

Cloud Monitoring

Key metric types for DevOps:

Metric	Source	Purpose
run.googleapis.com/request_count	Cloud Run	Request volume and error rates
compute.googleapis.com/instance/cpu/utilization	Compute Engine	VM performance
kubernetes.io/container/cpu/request_utilization	GKE	Container resource usage
cloudsql.googleapis.com/database/cpu/utilization	Cloud SQL	Database health
Custom metrics	Your application	Business-level SLIs

Log-Based Metrics

Create metrics from log entries for custom SLI measurement:

# Create a log-based metric counting 5xx errors
gcloud logging metrics create http_5xx_errors \
  --description="Count of 5xx HTTP responses" \
  --log-filter='resource.type="cloud_run_revision" AND httpRequest.status>=500'

---

Frequently Asked Questions

What is the difference between Cloud Build and Cloud Deploy? Cloud Build is a CI system that runs build, test, and packaging steps in containers. Cloud Deploy is a CD system that manages promotion of artifacts across a delivery pipeline (dev → staging → production) with gates, approvals, and progressive delivery strategies like canary releases. Cloud Build produces artifacts; Cloud Deploy delivers them. They are typically used together in a complete CI/CD pipeline.

How much of the PCDE exam focuses on SRE vs. DevOps tooling? The SRE section alone is 26% of the exam and SRE concepts appear throughout the monitoring (20%) and optimization (21%) sections as well. Overall, SRE principles (SLOs, error budgets, reliability engineering) account for roughly 50-60% of the exam's practical questions. Candidates who focus only on Cloud Build and GKE deployment without studying SRE concepts consistently underperform on this exam.

What are the key Cloud Monitoring concepts tested on this exam? SLO creation and configuration using Cloud Monitoring, error budget burn rate alerts (multi-window, multi-burn-rate alerting), log-based metrics for creating custom SLIs from log data, uptime checks for external availability monitoring, dashboard creation for operational visibility, and Managed Service for Prometheus integration. PromQL basics are tested as GKE metrics increasingly use Prometheus.

References

1. Google Cloud. (2025). Professional Cloud DevOps Engineer Certification. https://cloud.google.com/certification/cloud-devops-engineer
2. Google Cloud. (2025). Cloud Build Documentation. https://cloud.google.com/build/docs
3. Google Cloud. (2025). Cloud Deploy Documentation. https://cloud.google.com/deploy/docs
4. Beyer, B., Jones, C., Petoff, J., & Murphy, N. (2016). Site Reliability Engineering. O'Reilly Media.
5. Google Cloud. (2025). Cloud Monitoring SLO Documentation. https://cloud.google.com/monitoring/service-monitoring
6. Google Cloud. (2025). Cloud Operations Suite. https://cloud.google.com/products/operations