Cloud Developer Tests Managed Runtimes, Event Wiring and Credential Hygiene — Not Framework Syntax
For developers building cloud-native apps, using the April 2026 guide that adds AI coding assistants and MCP servers. The shift: reach for Cloud Run, client libraries and short-lived identities before custom code or standing keys.
Check Your Readiness →Most candidates understand Google Cloud Certified Professional Cloud Developer concepts — and still fail. This exam tests how you apply knowledge under pressure.
Code-adjacent scenarios with one or two hard constraints: bursty traffic, regulated data, a fragile partner API or a latency limit. Several answers work in principle; the scored one is the most managed option with the least custom code. Generative AI tooling appears inside sections rather than as its own.
Publish each job to Pub/Sub with a push subscription
Cloud Tasks dispatches to one target with explicit per-queue rate limits, retries and scheduled delivery. Pub/Sub fans events out to many independent subscribers, Cloud Scheduler runs timed jobs, and Workflows handles multi-step branching.
Cloud SQL behind a Cloud Run API
Firestore is a serverless document database with offline support and real-time sync to clients. Spanner suits global relational transactions, Bigtable suits time-series key lookups, and Cloud SQL or AlloyDB suit regional relational workloads.
Retry each failed call every second until it succeeds
Use the client library's pagination and field masks, then retry only transient 429 and 503 errors with exponential backoff and jitter, or queue calls through Cloud Tasks. Tight synchronised retries amplify overload.
Enable Artifact Analysis scanning and consider it enforced
Have Cloud Build generate SLSA provenance and enforce a Binary Authorization policy at deploy time. Scanning lists known CVEs but proves nothing about which builder or source produced the image, and it never blocks a deployment.
Opening the service to allUsers exposes it to the internet. Grant the Cloud Run Invoker role to the trigger's or push subscription's service account, and authenticate Pub/Sub push with an OIDC token from that account.
Liveness failure restarts the container, readiness failure removes the Pod from Service endpoints without restart, and a startup probe holds both until boot finishes. Cache warm-up errors during rolling updates call for a readiness probe.
Scaled-out instances exhaust database connection limits. Use the Cloud SQL language connectors or Auth Proxy for IAM-authorised, encrypted connections and a pool sized to instance limits, never authorised networks with changing serverless egress IPs.
A crash after an early ack loses the message. Ack after success, extend deadlines for long work, make handlers idempotent because delivery is at-least-once, and route poison messages to a dead-letter topic after maximum attempts.
Shared state makes runs flaky, slow and billable. gcloud emulators cover Pub/Sub, Firestore, Datastore, Bigtable and Spanner via emulator host variables with no code change; integration tests run as Cloud Build steps before push.
Strengthen weak areas with exam-style practice questions and detailed explanations.
Simulate the real exam experience and assess your readiness under timed conditions.
Review key concepts, objectives, and exam topics in one place.
Get personalized explanations, learning recommendations, and instant answers.
Follow a structured learning path designed to help you prepare efficiently.
Check whether your Cloud Run, Pub/Sub and credential choices match what the Cloud Developer exam rewards.