Google Cloud · PCD
Google Cloud Certified - Professional Cloud Developer (PCD) Practice Test
Validates expertise in building and deploying scalable, secure, and highly available applications using Google Cloud tools and best practices.
Exam Details
Questions
600
Duration
120 minutes
Passing Score
Not disclosed
Difficulty
ProfessionalLast Updated
Jan 2026
Google Cloud Certified - Professional Cloud Developer (PCD) Practice Exam Preparation
Use this PCD practice exam to prepare for Google Cloud Certified - Professional Cloud Developer (PCD) with realistic questions, detailed explanations, and focused study modes. The practice bank includes 600 questions for Google Cloud PCD, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to patterns in your missed answers. Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
Exam Domain Breakdown
Designing Highly Scalable, Available, and Reliable Cloud-Native Applications25%
Building and Testing Applications20%
Deploying Applications20%
Integrating Google Cloud Services20%
Managing Application Performance15%
Exam Overview
The Google Cloud Certified Professional Cloud Developer (PCD) certification validates a practitioner's ability to design, build, test, deploy, and manage scalable, secure, and highly available cloud-native applications on Google Cloud. The exam covers the full application development lifecycle on Google Cloud, assessing proficiency with compute platforms such as Cloud Run, Google Kubernetes Engine (GKE), App Engine, and Cloud Functions, as well as managed data stores including Cloud SQL, AlloyDB, Spanner, Firestore, Bigtable, and Cloud Storage. Candidates must demonstrate fluency in integrating Google Cloud services—such as Pub/Sub, Eventarc, Cloud Tasks, Cloud Scheduler, API Gateway, and Cloud Endpoints—into event-driven and API-centric architectures.
The certification also tests knowledge of modern DevOps practices, including CI/CD pipeline construction with Cloud Build and Cloud Deploy, container image management via Artifact Registry, supply chain security with Binary Authorization, and application security using IAM, Identity-Aware Proxy, Secret Manager, and Cloud KMS. Observability skills—covering Cloud Monitoring, Cloud Logging, Cloud Trace, and Cloud Profiler—are also assessed, reflecting Google Cloud's emphasis on instrumenting applications to produce actionable metrics, logs, and traces.
Who Should Take This Exam
This certification is designed for software engineers and developers who build and deploy applications on Google Cloud as part of their day-to-day responsibilities. Ideal candidates have hands-on experience with cloud-native patterns such as microservices, containerization, and serverless computing, and are comfortable with at least one general-purpose programming language. The exam is equally relevant to full-stack developers, backend engineers, and DevOps engineers who own the deployment and operational health of cloud-hosted applications.
Professionals transitioning from on-premises or other cloud environments who want to formalize their Google Cloud development skills will also benefit. Google recommends candidates have at least three years of industry experience, including one or more years of designing and managing solutions on Google Cloud.
Prerequisites
Google Cloud does not enforce formal prerequisites for the Professional Cloud Developer exam; any candidate may register directly. However, Google recommends a minimum of three years of industry software development experience, with at least one year spent designing and managing solutions on Google Cloud. Candidates should be comfortable working with cloud-native application architectures, container orchestration, RESTful and gRPC APIs, managed databases, and serverless platforms before attempting the exam.
A strong practical foundation is more valuable than theoretical study alone. Candidates without significant hands-on Google Cloud experience are advised to complete the Professional Cloud Developer learning path on Google Cloud Skills Boost, which includes guided labs covering Cloud Run, GKE, Cloud Build, Cloud Functions, and core data services before sitting for the exam.
Exam Format
The Professional Cloud Developer exam consists of 50–60 multiple-choice and multiple-select questions and must be completed within 120 minutes. The registration fee is $200 USD plus applicable taxes. The exam is available in English and Japanese and can be taken either via online proctoring (remote, from any location with a webcam and stable internet connection) or in person at an authorized Kryterion testing center worldwide.
Google does not publicly disclose a specific passing score for this exam. Scoring uses a compensatory model in which overall performance across all domains determines the outcome, rather than requiring minimum scores in each individual section. The certification is valid for two years, after which candidates must recertify through the renewal process.
Skills Measured
- 1.Domain 1 – Designing Highly Scalable, Available, and Reliable Cloud-Native Applications (~25%): Covers selecting appropriate compute platforms (App Engine, Cloud Run, GKE, Cloud Functions), designing microservices architectures, applying high-availability and disaster recovery patterns, choosing data storage technologies (Cloud SQL, Firestore, Bigtable, Spanner, Cloud Storage), implementing caching with Memorystore, and designing event-driven systems using Pub/Sub and Eventarc.
- 2.Domain 2 – Building and Testing Applications (~20%): Covers creating and managing container images with Cloud Build and Artifact Registry, implementing unit, integration, and end-to-end test strategies, building CI/CD pipelines with Cloud Build and Cloud Deploy, applying software supply chain security controls (Binary Authorization, provenance attestation), and configuring development environments for Google Cloud.
- 3.Domain 3 – Deploying Applications (~20%): Covers deploying workloads to App Engine (Standard and Flexible environments), Cloud Run, GKE, and Cloud Functions; executing deployment strategies including blue-green, canary, and rolling releases; managing traffic splitting and version control; configuring IAM, service accounts, and Secret Manager for secure deployments; and enforcing security and compliance policies during release.
- 4.Domain 4 – Integrating Google Cloud Services (~20%): Covers asynchronous messaging with Pub/Sub, deferred job processing with Cloud Tasks, scheduled execution with Cloud Scheduler, API exposure and management via API Gateway and Cloud Endpoints, service mesh configuration, and application security using Identity-Aware Proxy (IAP) and VPC Service Controls.
- 5.Domain 5 – Managing Application Performance (~15%): Covers creating dashboards and alerts in Cloud Monitoring, analyzing and routing logs with Cloud Logging, implementing distributed tracing with Cloud Trace, profiling application performance using Cloud Profiler, tracking errors with Error Reporting, and defining and measuring SLIs and SLOs for production services.
Study Tips
- Start with the official exam guide (downloadable PDF linked from cloud.google.com/learn/certification/cloud-developer) and map every subtopic to a hands-on lab or Google Cloud documentation page before studying anything else.
- Complete the Professional Cloud Developer learning path on Google Cloud Skills Boost. The path includes Qwiklabs that let you deploy real workloads to Cloud Run, GKE, and App Engine—experience that directly mirrors scenario-based exam questions.
- Practice reading and interpreting code snippets. The exam presents architecture scenarios and code fragments; use the official sample questions to calibrate how deeply the exam tests actual implementation knowledge versus conceptual understanding.
- Build a personal decision framework for compute platform selection: know precisely when to choose Cloud Run versus GKE versus App Engine Standard/Flexible versus Cloud Functions, including the trade-offs in cost, operational overhead, scaling behavior, and concurrency model.
- Focus dedicated study time on CI/CD and supply chain security topics—Cloud Build, Cloud Deploy, Artifact Registry, Binary Authorization, and software provenance—as these reflect recent updates to the exam guide (revised March 2025) and are heavily weighted in the Building and Testing domain.
- Use Google Cloud's official documentation for each managed service (Pub/Sub, Cloud Tasks, Eventarc, Secret Manager, Cloud KMS) rather than relying solely on third-party summaries. The exam tests nuanced configuration details that are only accurately described in official docs.
- Review Cloud Monitoring, Cloud Logging, and Cloud Trace documentation together as a unified observability stack. Practice writing log-based metrics, configuring uptime checks, and interpreting trace waterfall diagrams, as the Managing Application Performance domain tests these skills in integrated scenarios.
Career Benefits
The Professional Cloud Developer certification is recognized by organizations that run production workloads on Google Cloud, making it a strong differentiator for software engineers, DevOps practitioners, and cloud architects operating in GCP environments. Certified professionals typically pursue roles such as Cloud Application Developer, Site Reliability Engineer, Cloud Solutions Engineer, and DevOps Engineer. The certification demonstrates mastery of the full cloud-native development lifecycle—from architecture design through deployment and observability—which aligns with the skillsets most in demand at enterprises undergoing cloud modernization.
Salary data from multiple industry sources places certified Google Cloud Professional Cloud Developer professionals in the $140,000–$180,000 USD range in the United States, varying by role, seniority, and geography. Compared to associate-level Google Cloud certifications, the PCD signals hands-on production experience and is often weighted alongside certifications like the AWS Certified Developer – Associate or Microsoft Azure Developer Associate, though the PCD's scope—covering security, CI/CD pipelines, and multi-service integration in depth—is generally considered broader.
Sample Questions
5 sample questions with answers and explanations. Start a practice session to test yourself across all 600 questions.
Preview — answers shown1. You're implementing blue-green deployments on GKE for a stateless web application. Both blue and green environments must run simultaneously, and traffic should switch instantly from blue to green after validation. Which implementation approach provides the cleanest traffic cutover?
AUse Cloud Deploy with automated promotion between environments and manual approval gates
BCreate two Deployments (blue and green), use a single Service with selector labels, switch traffic by updating the Service selector to match the green Deployment labels
CCreate two separate GKE clusters for blue and green, use Cloud Load Balancing to switch traffic between clusters
DImplement Istio VirtualService with weighted routing, gradually shifting traffic from blue (100%) to green (100%) over 5 minutes
Explanation
The Service selector approach is the cleanest Kubernetes-native blue-green implementation. Both Deployments run simultaneously with different labels (e.g., version: blue and version: green), and switching traffic is instantaneous by updating the Service selector. This requires no external tools and provides atomic cutover. Cloud Deploy is useful for managing deployments but adds complexity for a simple blue-green pattern. Separate clusters introduce significant operational overhead and cost for a stateless application. Istio weighted routing is more appropriate for canary deployments with gradual rollout - blue-green deployments require instant cutover, not gradual traffic shifting.
2. A media streaming company is implementing chaos engineering to test their GKE application's resilience. They want to randomly terminate pods, introduce network latency, and simulate node failures during business hours without affecting production traffic. Which solution meets these requirements?
AImplement Chaos Mesh or Litmus on GKE with experiment definitions that target non-production namespaces, schedule experiments during low-traffic periods, and configure observability dashboards
BUse GKE preemptible nodes for the entire cluster and rely on automatic node replacement to simulate failures
CCreate Cloud Monitoring alerts that automatically delete random pods when error rates are low
DDeploy a canary version of the application with 1% traffic, use kubectl delete pod to manually terminate canary pods, and monitor error rates
Explanation
Chaos engineering frameworks like Chaos Mesh or Litmus provide controlled, reproducible experiments with precise targeting capabilities, safety controls, and integration with observability tools. Targeting non-production namespaces or specific deployments ensures you test resilience without risking customer experience. Manual pod deletion lacks reproducibility, automation, and proper controls. Preemptible nodes introduce random failures but don't provide controlled experiments for network latency, CPU stress, or other failure modes that chaos engineering tests. Alert-based pod deletion is dangerous and unpredictable, lacking the safety mechanisms and experimental rigor that proper chaos engineering tools provide.
3. A development team uses service accounts for Cloud Build to deploy applications to GKE. They need to follow security best practices and avoid using service account keys. How should Cloud Build authenticate to the GKE cluster?
AUse Workload Identity to allow Cloud Build pods to authenticate to GKE
BUse Cloud Build's default service account with IAM permissions to access GKE
CGenerate short-lived credentials using the Service Account Credentials API during builds
DCreate service account keys and store them in Secret Manager for Cloud Build to use
Explanation
Short-lived credentials from the Service Account Credentials API provide time-limited access tokens (default 1 hour) for service account authentication without requiring long-lived keys. Cloud Build can generate these credentials during the build process using gcloud or API calls, eliminating key management risks. This is the recommended secure alternative to service account keys. Using the default service account works if it has proper permissions, but the question emphasizes avoiding keys and following best practices for authentication. Storing keys in Secret Manager improves key security but doesn't eliminate the fundamental risk of long-lived credentials. Keys should be avoided when alternatives exist. Workload Identity is for GKE pods accessing Google Cloud services, not for Cloud Build (which doesn't run in GKE) accessing GKE. Short-lived credentials provide the secure, keyless authentication the question requires.
4. A Cloud Function experiences occasional failures that are difficult to reproduce. You need to capture the complete application state when failures occur without adding extensive logging code. What should you implement?
AEnable Cloud Trace to record all function executions
BEnable Cloud Debugger to set logpoints and snapshots that capture variable state when specific code paths execute
CAdd comprehensive try-catch blocks with detailed logging throughout the code
DConfigure Cloud Error Reporting to capture stack traces
Explanation
Cloud Debugger allows setting logpoints and snapshots that capture complete application state including variable values when specific code locations are reached, without modifying or redeploying code. This provides deep visibility into application behavior during failures. Try-catch blocks with logging require code changes and may not capture all relevant state. Cloud Error Reporting captures stack traces but not variable values or application state. Cloud Trace records timing and request flow but does not capture application state or variable values during failures.
5. A GKE application uses ConfigMaps to store configuration data. The security team requires that sensitive configuration values like API keys must be encrypted at rest and rotated regularly. What should you do?
AUse Cloud KMS to manually encrypt values before storing in ConfigMaps
BStore sensitive values in Secret Manager and reference them from the application, while keeping non-sensitive configuration in ConfigMaps
CConvert ConfigMaps to Secrets, which are automatically encrypted at rest in GKE
DEnable application-layer encryption for ConfigMap values
Explanation
Secret Manager is purpose-built for storing sensitive credentials with encryption at rest, access controls, rotation capabilities, and audit logging. Storing sensitive values in Secret Manager while keeping non-sensitive configuration in ConfigMaps provides appropriate security for each data type. GKE Secrets are base64 encoded, not encrypted, and do not provide rotation capabilities. Application-layer encryption adds complexity and does not provide centralized secret management. Manually encrypting with Cloud KMS before storing in ConfigMaps requires custom key management and does not leverage Secret Manager's built-in features.
More Google Cloud Practice Exams
Google Cloud Certified - Professional Cloud Architect (PCA)
PCA · 1397 questions
Google Cloud Certified - Professional Cloud DevOps Engineer (PCDOps)
PCDOps · 1132 questions
Google Cloud Certified - Professional Machine Learning Engineer (PMLE)
PMLE · 1100 questions
Google Cloud Certified - Associate Data Practitioner (ADP)
ADP · 1089 questions
Google Cloud Certified - Professional Security Operations Engineer (PSOE)
PSOE · 1089 questions
Google Cloud Certified - Professional Cloud Security Engineer (PCSE)
PCSE · 1075 questions
$17.99
One-time access to this exam
Full access to all 600 questions
Or $15/mo for all 253 exams
Detailed explanations
Free preview stays available