# Google Professional Cloud DevOps Engineer (GPCDE) practice exams

> Google Professional Cloud DevOps Engineer practice exams: 240 questions in 5 timed tests, every answer explained.

Page: https://devopscodelab.com/exams/google-professional-cloud-devops-engineer/

240 questions in 5 timed practice tests. Each test has about 50 questions and a 120-minute limit. The pass mark is 70%. Results are split across the 5 exam domains.

## Exam at a glance

| Setting | Value |
| --- | --- |
| Practice tests | 5 |
| Questions in total | 240 |
| Questions per test | About 50 |
| Time limit per test | 120 minutes |
| Pass mark | 70% |
| Question types | Single answer and multiple answer (23 multiple-answer questions) |
| Level | Professional |
| Category | DevOps & Cloud Native |

These are the settings of our practice tests. Check the official Google Cloud exam page for the current format before you book.

## Domains and weights

| Domain | Weight | Questions in our bank |
| --- | --- | --- |
| Establishing and bootstrapping foundational infrastructure and organizational governance | 18% | 43 |
| Building, implementing, and maintaining CI/CD pipelines for application, infrastructure, and ML workloads | 30% | 72 |
| Applying site reliability engineering practices | 18% | 43 |
| Implementing observability practices and troubleshooting issues | 22% | 53 |
| Optimizing performance and cost | 12% | 29 |

## Price and access

- GPCDE practice exams: $14.99 for 12 months of access.
- Free mini exam: 15 questions with explanations (free account): https://devopscodelab.com/app/exams/google-professional-cloud-devops-engineer/mini/
- All-Access subscription includes every exam: https://devopscodelab.com/pricing/
- 10 free questions with answers: https://devopscodelab.com/exams/google-professional-cloud-devops-engineer/free-practice-questions/

## Sample questions

### Question 1 of 3

A company runs production GKE Standard clusters and must stay on supported versions with minimal disruption. Upgrades must not occur during the Black Friday week, and node upgrades should never take more than one node out of service at a time per pool. What should you configure?

- A. Pin the control plane version with a no-channel configuration and recreate each cluster from scratch with Terraform when a version reaches end of support
- B. Enroll the clusters in the Rapid release channel so upgrades happen early in the year, well before Black Friday, and rely on default upgrade settings
- C. Enroll the clusters in the Stable release channel with maintenance windows, a Black Friday maintenance exclusion, and surge upgrades with maxUnavailable 0
- D. Disable auto-upgrade on all clusters and node pools and upgrade manually once a year after the holiday season using blue-green node pool upgrades

**Answer:** C

**Explanation:** A release channel keeps versions supported, maintenance windows and exclusions control when automatic upgrades happen, and surge settings such as maxSurge 1 with maxUnavailable 0 avoid taking existing nodes out of service before replacements are ready. Disabling auto-upgrade and upgrading yearly risks running unsupported versions. The Rapid channel gets the newest versions with the most change and offers no protection for the holiday week. Recreating clusters at end of support is disruptive and operationally heavy.

### Question 2 of 3

Your organization requires that no Compute Engine VM in any project receives an external IP address, except in a single project that hosts bastion hosts for a legacy vendor. You want the control to be enforced automatically for new projects. What should you do?

- A. Remove the roles/compute.instanceAdmin.v1 role from all developers at the organization level and grant it only to the bastion team on the bastion project
- B. Create a hierarchical firewall policy at the organization node that denies all ingress from 0.0.0.0/0 and add a higher-priority allow rule scoped to the bastion project's VPC
- C. Write a Cloud Asset Inventory feed that publishes VM creation events to Pub/Sub and a Cloud Run function that deletes any external IP assigned outside the bastion project
- D. Enforce the compute.vmExternalIpAccess constraint at the organization node to deny all, and override it on the bastion project to allow only the bastion VMs

**Answer:** D

**Explanation:** The compute.vmExternalIpAccess organization policy constraint prevents external IPs from being assigned and is inherited by every new project, and a project-level policy can allow the specific bastion instances. A hierarchical firewall rule blocks traffic but does not stop external IP assignment. Removing an admin role stops all VM management rather than external IPs specifically. An Asset Inventory feed with a cleanup function is reactive and leaves a window where external IPs exist.

### Question 3 of 3

Developers complain that Cloud Build runs for a large Java monorepo take 25 minutes because Maven downloads dependencies on every build. You want to reduce build time without changing the build tool. What should you do?

- A. Increase the Cloud Build machine type to E2_HIGHCPU_32 so that dependency downloads run with more parallel network threads and compilation also finishes faster
- B. Use an Artifact Registry Maven remote repository as a caching proxy for Maven Central and point the build's settings.xml at it
- C. Split the build into one Cloud Build trigger per Maven module so that each trigger runs in parallel on its own worker
- D. Move the build to a private pool in the same region as the repository so network latency to Maven Central decreases

**Answer:** B

**Explanation:** An Artifact Registry remote repository caches upstream Maven artifacts close to the build workers, so repeated dependency fetches are fast and also more resilient to upstream outages. A larger machine helps CPU-bound compilation, not repeated downloads from the internet. A private pool changes the network location but still fetches everything from Maven Central each run. Splitting triggers per module adds orchestration overhead and each trigger still downloads its dependencies.


## Study plans

### Two weeks

1. Day 1: take practice test 1 in exam mode to get a baseline.
2. Days 2 to 5: domain mode on Building, implementing, and maintaining CI/CD pipelines for application, infrastructure, and ML workloads and Implementing observability practices and troubleshooting issues, the two most heavily weighted domains.
3. Day 6: practice test 2 in exam mode, then the mistakes quiz.
4. Days 7 to 12: practice tests 3 to 5, one every other day, each followed by its mistakes quiz.
5. Days 13 and 14: final mode. Book the exam when your readiness stays above the pass mark.

### Four weeks

1. Week 1: one practice test in practice mode, reading every explanation. Note your two lowest domains.
2. Week 2: domain mode on those two domains, then a second practice test in exam mode.
3. Week 3: practice tests 3 and 4 in exam mode, with the mistakes and flagged quizzes after each.
4. Week 4: practice test 5 and final mode until your readiness holds above the pass mark.

## Questions about the GPCDE practice exams

**Are these real GPCDE exam questions?**

No. We write every question ourselves and map it to the published GPCDE exam objectives. We do not use leaked or recalled questions.

**Do the time limit and pass mark match the official exam?**

They match the settings of our practice tests. Exam providers change their format from time to time, so check the official exam page before you book.

**Can I try it before I pay?**

Yes. The free mini exam has 15 questions with full explanations and needs no account.

**How long do I keep access?**

A single-exam purchase gives you 12 months of access. All-Access includes this exam for as long as your subscription runs.

**What happens after I finish a test?**

You get a score, a pass or fail against the pass mark, a score per domain and every answer with its explanation.

Last updated November 2026.

DevOpsCode Lab is not affiliated with Google Cloud. GPCDE and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
