Google Cloud Certified — Professional Cloud Developer (PCD) Practice Exams
About the GCP PCD exam
Exam at a glance
Google Cloud's developer Professional certification.
Who PCD targets
PCD validates that you can build production cloud-native applications on Google Cloud. The exam targets application developers who design, build, deploy, and integrate apps end-to-end — not platform operators (that's PCDoE) and not pure architects (that's PCA). Heavy focus on Cloud Run, GKE, Cloud Functions, App Engine, Cloud SQL, Spanner, Firestore, and Pub/Sub.
Domain weighting
- Designing highly scalable, available, and reliable cloud-native applications: ≈25%
- Building and testing applications: ≈20%
- Deploying applications: ≈20%
- Integrating Google Cloud services: ≈20%
- Managing application performance monitoring: ≈15%
Prerequisites
None formally. Google recommends 3+ years of professional development experience including 1+ years building on Google Cloud. Passing the Associate Cloud Engineer (ACE) first is a useful but optional foundation — many candidates go straight to PCD if they already have GCP hands-on time.
Why take this certification
- Developer credential, not architect. PCD is the only Google Cloud Professional cert focused squarely on writing application code on GCP — design, build, deploy, integrate, observe. If you ship Cloud Run services, GKE workloads, or Cloud Functions for a living, it's the credential that mirrors your job.
- Pairs naturally with PCDoE. PCD covers the application; PCDoE covers the CI/CD, SLOs, and operations around it. Holding both signals full-stack platform-engineering range and is a common combination on senior cloud-developer postings.
- Hands-on focus. Like all Google Cloud Professional exams, PCD is scenario-driven. You'll be asked to pick the right deployment pattern, the right Pub/Sub delivery semantics, the right Cloud SQL connection strategy — concepts that map directly to production code.
- 3-year validity. Google Cloud certs hold for three years. Plan recertification ahead of the 60-day renewal window; there is no continuing-education path.
What you'll learn in the PCD exam
PCD validates that you can build production cloud-native applications on Google Cloud — choosing the right runtime, wiring services together, deploying safely, and observing what you shipped. Most questions are scenario-driven: a workload with constraints (latency, cost, ordering, security) and four or five plausible implementation choices.
Serverless runtimes
- Cloud Run services — request-driven HTTPS, concurrency tuning, min/max instances, CPU allocation, traffic splitting.
- Cloud Run jobs — finite batch workloads, task parallelism, retries.
- Cloud Functions Gen2 (built on Cloud Run) — HTTP and event triggers, Eventarc integration.
- App Engine Standard vs Flexible — when each still fits and when Cloud Run is the better default.
Containers and GKE
- GKE Autopilot vs Standard — node-management trade-offs, when each is the right answer.
- Workload Identity — bind Kubernetes service accounts to Google service accounts; no JSON keys in pods.
- Cloud Build for container CI — multi-step builds, Artifact Registry pushes, signed provenance.
App deployment patterns
- Blue/green deploys via Cloud Run revisions.
- Canary rollouts using Cloud Run traffic splitting (percent-based routing across revisions).
- Rolling updates on GKE Deployments — surge and unavailable budgets.
- A/B testing via tagged Cloud Run revisions and weighted traffic.
Cloud Storage
- Signed URLs for time-bounded direct uploads/downloads.
- Resumable uploads for large objects.
- IAM vs ACLs (IAM is the modern default), uniform bucket-level access.
Databases
- Cloud SQL connection patterns — Cloud SQL Auth Proxy, connection pooling, IAM database authentication.
- Cloud Spanner client libraries — single-region vs multi-region, schema design for hotspots.
- Firestore SDK — document modeling, real-time listeners, security rules.
- Memorystore (Redis/Memcached) for caching hot paths.
Messaging and eventing
- Pub/Sub at-least-once delivery semantics and how to design idempotent consumers.
- Ordering keys for in-order delivery within a key.
- Dead-letter topics for poison messages.
- Message filtering on subscription attributes.
- Eventarc for fully-managed event routing across Google Cloud sources.
Authentication and identity
- Firebase Authentication and Identity Platform for end-user sign-in.
- Identity-Aware Proxy (IAP) for application-layer auth on internal apps.
- IAM service accounts for application identity inside Google Cloud.
- Workload Identity Federation for non-GCP workloads (GitHub Actions, AWS, on-prem) calling Google Cloud APIs without service-account keys.
Observability
- Cloud Logging — structured JSON logs, log-based metrics, exclusion filters.
- Cloud Trace — distributed tracing across Cloud Run, GKE, Cloud Functions.
- Cloud Profiler — continuous production CPU/heap profiling.
- Cloud Monitoring — SLOs and SLIs, alerting policies, uptime checks.
- Cloud Debugger replacement options now that the legacy product is sunset.
How the practice exams help
Each free question and every premium exam mirrors Google's scenario-style format — long stem with explicit constraints, four to five plausible options, single or multiple correct. Detailed explanations cover not just why the right answer is right but why the distractors fail the constraints, so you learn the trade-offs rather than memorizing answers.
How to prepare for the PCD exam
A successful PCD preparation plan combines theory, hands-on coding on real Google Cloud services, and timed practice. Working developers with GCP exposure typically need 10–14 weeks at 10–15 hours per week.
- Walk the official exam guide (1 week). Download the PCD exam guide (PDF) and the cert overview. Map every objective to a service you've actually used; flag the ones you haven't.
- Follow the Cloud Skills Boost learning path (4–5 weeks). The Professional Cloud Developer learning path bundles labs across Cloud Run, GKE, Cloud SQL, Pub/Sub, and observability. Do the labs; don't just watch the videos.
- Build a representative sample app (3–4 weeks). Spin up a small free-tier project: a Cloud Run service backed by Cloud SQL, with Pub/Sub for async work and Cloud Logging + Cloud Trace wired in. Then redeploy the same app to GKE Autopilot to feel the trade-offs. Add a canary rollout with traffic splitting. This single exercise touches roughly 60% of the exam's surface area.
- Practice exams (2–3 weeks). Take timed practice tests to surface weak domains. Detailed explanations on every option help you learn the why behind each correct answer. Aim for consistent 80%+ scores before scheduling.
Recommended timeline
10–14 weeks of focused study (10–15 hours per week) for developers with some Google Cloud experience. Developers brand-new to GCP should pass ACE first (adds another 4–6 weeks of foundational work).
Official resources
Start with the official PCD certification page, the PCD exam guide (PDF), the Professional Cloud Developer learning path on Cloud Skills Boost, and Google's free sample questions.
Frequently asked questions
Are these actual exam questions?
No. All Nex Arc GCP PCD practice questions are original content based on the provider's published exam blueprint, official documentation, and real-world scenarios across every topic the exam covers. We do not offer brain dumps, leaked questions, or actual exam content. Using or distributing real exam questions violates certification provider agreements and can result in certification revocation.
How many questions are in the GCP Professional Cloud Developer exam?
The GCP Professional Cloud Developer exam consists of 50–60 multiple-choice and multiple-select questions that you need to complete in 2 hours. Questions are scenario-driven, often presenting a workload with constraints (latency, cost, reliability) and asking you to choose the architecture or implementation that best fits.
What's the PCD passing score?
Google does not publicly disclose the passing score for any Professional certification, including the Professional Cloud Developer. Candidates receive a pass/fail result with no numerical score. Industry consensus places the threshold somewhere around 70%, but the exam uses a scaled scoring model and the cut score may vary between exam forms. Focus on consistently scoring 80%+ on quality practice exams before attempting.
How do I access the full PCD practice exam?
Click on the Buy Now button in the sidebar to purchase the complete GCP Professional Cloud Developer course. After payment, you'll have instant access to 12 practice exams with detailed explanations and lifetime access.
What are the prerequisites for the PCD exam?
There are no formal prerequisites. Google recommends 3+ years of industry development experience, including 1+ years designing and managing solutions using Google Cloud, but you can sit the exam at any time. Most successful candidates have hands-on experience with at least one of Cloud Run, GKE, Cloud Functions, or App Engine, plus working familiarity with a managed Google Cloud database (Cloud SQL, Spanner, or Firestore) and Pub/Sub messaging. Passing the Associate Cloud Engineer (ACE) first is a useful but optional foundation.
How long is the PCD certification valid?
Google Cloud certifications are valid for three years from the date you pass the exam. Recertification is by re-examination only — there is no continuing-education or credits-based renewal path. Google opens a renewal window beginning roughly 60 days before your certification expires, during which you can retake the current version of the exam at the standard $200 USD fee. Plan ahead: if you miss the renewal window, your certification lapses and is removed from the public Credly registry until you re-pass.
What's the exam cost and can I retake it if I fail?
The GCP Professional Cloud Developer exam costs $200 USD (plus applicable taxes). The exam is delivered through Kryterion either online-proctored from home or onsite at a Webassessor testing center, in English or Japanese. If you fail, Google's retake policy is tiered: 14 days before a second attempt, 60 days before a third, and 365 days before a fourth. Each attempt requires a new $200 payment. Practice thoroughly to minimize retake costs and waiting periods.
What Google Cloud services are most heavily tested on PCD?
Based on the five exam domains, the most frequently tested services are: Cloud Run (services, jobs, traffic splitting, concurrency), Google Kubernetes Engine (Autopilot vs Standard, Workload Identity), Cloud Functions Gen2, App Engine Standard vs Flexible, Cloud SQL (Auth Proxy, connection pooling), Cloud Spanner, Firestore, Pub/Sub (ordering keys, dead letter, filtering, Eventarc), Cloud Storage (signed URLs, resumable uploads, IAM), Cloud Build, Artifact Registry, Cloud Logging / Cloud Trace / Cloud Profiler / Cloud Monitoring, IAM service accounts, Identity Platform and Identity-Aware Proxy. Cloud Run and GKE alone appear in roughly 40% of questions.
How does PCD differ from the Professional Cloud DevOps Engineer (PCDoE)?
PCD and PCDoE are sibling Professional credentials that pair naturally for full-stack platform engineering, but they test different roles. PCD targets application developers — you design, build, deploy, and integrate cloud-native applications using Cloud Run, GKE, Cloud Functions, Cloud SQL, Spanner, Firestore, and Pub/Sub. PCDoE targets DevOps engineers and SREs — you build CI/CD pipelines, define and operate SLOs/SLIs, manage incident response, and operate the platform on which apps run. PCD = build apps. PCDoE = run the platform. Many practitioners hold both.
Can I retake the PCD exam if I fail?
Yes. Google allows retakes on a tiered waiting schedule: 14 days after a first failure, 60 days after a second, and 365 days after a third. You pay the full $200 USD exam fee for each attempt. Take time between attempts to remediate weak domains — repeating the exam without targeted study rarely changes the outcome.