Prepare for Professional Cloud Developer by connecting application requirements to design, build, deployment and integration decisions. Use the current four-area map, solve the Pub/Sub example, and practise the objectives that extend beyond your daily work.
Who is this exam for?
Professional Cloud Developer covers building and configuring scalable, secure applications on Google Cloud.
The role spans cloud-native application design, building and testing, deployment and integration. The current guide also includes AI APIs and AI-assisted development tools; check its specific objectives rather than assuming a familiar service covers the whole role.
There is no prerequisite certification. Google recommends three or more years of industry experience, including one or more years designing and managing Google Cloud solutions. The general certification FAQ requires candidates to be at least 18.
Official documents: Professional Cloud Developer Certification Exam Guide (PDF) — Sections 1-4 with weights and considerations; Professional Cloud Developer Certification | Learn | Google Cloud — Certification overview, exam facts, and preparation steps; Google Cloud Certification FAQs - Cloud Certification Help — Eligibility, validity, results, and score reporting
What are the four current exam areas?
The current guide weights design at approximately 32%, building and testing at 23%, deployment at 24%, and integration at 21%.
Use the map to identify gaps, then consult the official guide for the full objective lists. Study order can reflect your experience; the weights do not require you to study in a fixed sequence.
| Section (weight) | Review priorities from the exam guide |
|---|---|
| 1. Designing highly scalable, secure, and reliable cloud-native applications (~32%) | Choosing a platform (Compute Engine, GKE, Cloud Run); containers on Cloud Run and GKE; geographic distribution, load balancers, session affinity, caching with Memorystore; REST and gRPC APIs with Apigee or Cloud API Gateway; event-driven design with Eventarc and Pub/Sub; data retention policies; IAP, Web Security Scanner, Artifact Analysis, Security Command Center; Secret Manager, Cloud KMS, Workload Identity Federation; service-account IAM roles; service-to-service security; Binary Authorization; storage selection and schemas (AlloyDB, Spanner, Bigtable, Firestore); signed URLs; BigQuery for analytics |
| 2. Building and testing applications (~23%) | Emulating Google Cloud services with the Google Cloud CLI for local development and unit testing; console, Cloud SDK, Cloud Code, Gemini Cloud Assist, Cloud Shell, Cloud Workstations; IDE integrations including AI tooling; Cloud Build and Artifact Registry; build provenance for Binary Authorization; unit tests with AI coding assistants; automated integration tests in Cloud Build |
| 3. Configuring cloud-native applications for deployment (~24%) | Deploying to Cloud Run from source code; invoking services with triggers such as Eventarc and Pub/Sub; configuring event receivers; versioning, exposing, and securing APIs with Apigee; deploying containers to GKE; Kubernetes health checks; Horizontal Pod Autoscaler attributes |
| 4. Integrating applications with Google Cloud services (~21%) | Managing connections to Cloud SQL, Firestore, Cloud Storage; reading and writing across data sources; publishing and consuming messages with Pub/Sub; API calls through Cloud Client Libraries, REST, gRPC, or API Explorer with batching, restricted return data, pagination, caching, and error handling such as exponential backoff; service accounts for API calls; metrics, logs, and traces in Google Cloud Observability; Error Reporting; trace IDs across services; AI-assisted observability |
Official documents: Professional Cloud Developer Certification Exam Guide (PDF) — Sections 1-4 with weights and considerations
Practice choosing a Pub/Sub subscription
Pull delivery is initiated by the subscriber client. Push delivery is initiated by Pub/Sub. Export subscriptions write messages directly to a Google Cloud resource.
Google’s comparison describes pull clients using authorized credentials to call the Pub/Sub API, and push endpoints as publicly accessible HTTPS servers with non-self-signed certificates. Match the mechanism to the actual delivery requirements.
Practice decision
An existing order-processing worker must receive messages directly and run its own validation and database-writing code. It has authorized credentials and can call the Pub/Sub API outbound. Policy forbids a public inbound HTTPS endpoint for this worker. The design permits neither an export destination nor a separate downstream processor. Which subscription type fits: pull, push or export?
Show answer
Choose pull. The authorized worker initiates requests and receives messages for its own processing.
Push requires the inbound endpoint that the scenario forbids. Export writes to a Google Cloud destination, which this design excludes, instead of delivering directly to the worker. This answer concerns the stated subscription mechanism; it does not establish delivery guarantees or imply that export subscriptions never support transformations.
Official documents: Choose a subscription type | Pub/Sub | Google Cloud Documentation — Subscription types and comparison table
Build a study plan around your gaps
Use the current objectives, Google’s Professional Cloud Developer learning path, official samples and service documentation to plan your practice.
If your work centers on one service, map the tasks you already perform to the guide and identify the remaining objectives. A job title or a previous credential does not show which individual objectives you can apply.
Use authorized learning environments for hands-on work and check access and costs first. Official samples help with question format and examples; they do not provide full syllabus coverage or predict a pass.
- Design: explain a platform and storage choice against explicit workload, security and reliability requirements. Verify relevant service behavior in current docs.
- Build and test: review local-development tools, artifact management, build provenance and the listed automated tests; practise applicable tasks with a small application.
- Deploy: trace how an application version reaches its runtime, how it is invoked, and which health or scaling settings the objectives ask you to understand.
- Integrate: practise the listed API, data-connection, messaging and observability tasks. Work the Pub/Sub exercise and explain why each alternative does or does not fit.
- Before booking: revisit weak objectives, review sample-answer explanations and confirm the current guide and appointment requirements.
Official documents: Professional Cloud Developer Certification Exam Guide (PDF) — Sections 1-4 with weights and considerations; Professional Cloud Developer Certification | Learn | Google Cloud — Certification overview, exam facts, and preparation steps; Choose a subscription type | Pub/Sub | Google Cloud Documentation — Subscription types and comparison table
What should you expect on exam day?
The standard Professional Cloud Developer exam lasts two hours and has 50–60 multiple-choice and multiple-select questions. Registration costs USD200, plus applicable tax. The exam is offered in English and Japanese.
Choose a testing center or Pearson OnVUE remote proctoring. Remote exams are closed book and normally permit no breaks. Check the current ID, workspace, system and appointment instructions; arrange any needed accommodation before scheduling.
Your initial pass/fail result is provisional. Google says to allow 7–10 days for official confirmation. It does not report a numerical score; unsuccessful standard-exam candidates receive section-level feedback to help guide further study.
Professional candidates may make up to four attempts within two years. After a first failure, wait at least 14 days; after a second, 60 days; after a third, 365 days. Attempts count across languages and delivery methods, and each registration is paid.
Official documents: Professional Cloud Developer Certification | Learn | Google Cloud — Certification overview, exam facts, and preparation steps; Google Cloud Certification FAQs - Cloud Certification Help — Eligibility, validity, results, and score reporting; Retake Policy - Cloud Certification Help — Associate and Professional attempt limits and waiting periods; Online Proctored Exams - Cloud Certification Help — OnVUE requirements, ID rules, breaks, and delivery switching
How does renewal work?
Professional certification is initially valid for two years. The exam renewal window opens 60 days before your inactive date, and exam renewal adds two years to that date.
The current renewal table does not offer this credential a shorter renewal exam or designated Google Skills continuing-education route. Use the standard exam and check your CM Connect profile for eligibility and dates.
Google permits renewal within 30 days after the inactive date, subject to the applicable exam options. More than 30 days later, recertification requires the standard exam at full list price.
Official documents: Professional Cloud Developer Certification | Learn | Google Cloud — Certification overview, exam facts, and preparation steps; Google Cloud Certification FAQs - Cloud Certification Help — Eligibility, validity, results, and score reporting; Certification Renewal Options - Cloud Certification Help — Renewal windows, renewal by exam, and expiration grace period
Official documents
Facts checked against official Google Cloud pages on 14 September 2026:
- Professional Cloud Developer Certification Exam Guide (PDF)
- Professional Cloud Developer Certification | Learn | Google Cloud
- Google Cloud Certification FAQs - Cloud Certification Help
- Retake Policy - Cloud Certification Help
- Certification Renewal Options - Cloud Certification Help
- Online Proctored Exams - Cloud Certification Help
- Choose a subscription type | Pub/Sub | Google Cloud Documentation