Google Cloud PCDOE Sample Questions with Explanations

These original sample questions are designed to help you check how the exam topics appear in decision-style prompts. They are not taken from the live exam.

Use these sample questions as a guided self-assessment for Google Cloud Professional Cloud DevOps Engineer (PCDOE) topics such as CI/CD, SLOs, error budgets, observability, incident response, release safety, infrastructure automation, and operational improvement.

Where these questions fit in the PCDOE guide

The sample set below is part of the Google Cloud PCDOE guide path:

• Google Cloud certification hub
• PCDOE exam guide
• PCDOE cheat sheet
• PCDOE study plan
• PCDOE FAQ
• PCDOE resources
• PCDOE glossary

PCDOE reliability and delivery sample questions

Work through each prompt before opening the explanation. DevOps questions reward measurable reliability, safe automation, observability, and reversible change.

---

Question 1

Topic: Using an error budget

A service has consumed nearly all of its monthly error budget after several incidents. Product leaders want to continue rapid feature launches. What is the strongest SRE-aligned response?

• A. Pause or slow risky launches and prioritize reliability work until the service is back within the agreed error-budget policy.
• B. Delete the SLO so the service no longer appears unreliable.
• C. Increase the target after the incidents so the dashboard looks better.
• D. Ignore the budget because feature velocity is always more important than reliability.

Best answer: A

Explanation: Error budgets create a negotiated balance between reliability and release speed. When the budget is nearly exhausted, the team should reduce risky change and invest in reliability according to policy.

Why the other choices are weaker:

• B removes the measurement instead of improving service behavior.
• C manipulates targets after the fact.
• D ignores the reliability agreement with users.

What this tests: SLOs, error budgets, release decisions, and reliability governance.

Related topics: SLO; Error budget; SRE; Reliability

---

Question 2

Topic: Choosing a safer rollout

A team is releasing a new version of a high-traffic service. They want to expose a small percentage of users first, monitor key metrics, and roll back quickly if errors increase. Which deployment strategy is the best fit?

• A. Big-bang deployment to all users with no rollback plan.
• B. Canary rollout with automated monitoring and rollback criteria.
• C. Manual SSH changes on each production instance during business hours.
• D. Disable monitoring until after the rollout to avoid noisy alerts.

Best answer: B

Explanation: Canary rollout fits gradual exposure, metric-based validation, and fast rollback. The key is linking rollout progression to observable health signals.

Why the other choices are weaker:

• A maximizes blast radius.
• C is hard to reproduce, audit, and roll back safely.
• D removes the feedback needed for safe deployment.

What this tests: Progressive delivery, canary deployments, monitoring, and rollback design.

Related topics: Canary; Rollback; CI/CD; Release safety

---

Question 3

Topic: Making an alert actionable

An operations team receives hundreds of alerts each week. Many alerts have no owner, no user impact, and no runbook. Engineers are starting to ignore notifications. What should the team do first?

• A. Create more alerts for every metric so nothing is missed.
• B. Turn off all alerting permanently.
• C. Page only on user-impacting symptoms or SLO burn, assign ownership, and attach runbooks or automation for response.
• D. Send every alert to the entire company.

Best answer: C

Explanation: Alerts should be actionable. Tying pages to user impact or SLO burn, assigning owners, and linking runbooks reduces noise and improves response quality.

Why the other choices are weaker:

• A increases alert fatigue.
• B removes detection instead of improving signal quality.
• D diffuses accountability and creates noise.

What this tests: Observability, alert design, SLO-based paging, runbooks, and operational ownership.

Related topics: Alerting; Runbooks; Observability; Toil reduction

---

Question 4

Topic: Reducing infrastructure drift

Several production incidents were traced to manual console changes that were never reviewed or reproduced in lower environments. What should the DevOps engineer recommend?

• A. Continue manual changes but ask engineers to remember them better.
• B. Disable audit logs so manual changes are less distracting.
• C. Use version-controlled infrastructure as code, peer review, automated policy checks, and controlled deployment pipelines.
• D. Give every engineer unrestricted production access to speed fixes.

Best answer: C

Explanation: Infrastructure as code plus review and automated checks reduces drift and makes changes reproducible. Controlled pipelines improve auditability and rollback compared with ad hoc console edits.

Why the other choices are weaker:

• A relies on memory instead of process.
• B removes evidence.
• D increases blast radius and weakens governance.

What this tests: Infrastructure as code, change control, policy checks, auditability, and drift reduction.

Related topics: IaC; Change control; Policy checks; Drift

Independent study note

Tech Exam Lexicon and IT Mastery are independent study tools. They are not affiliated with, endorsed by, or sponsored by Google Cloud or any certification body.