1
Single choice~90s
To let a web tier scale horizontally and tolerate instance loss behind a load balancer, where should session state be kept?
Professional Cloud Developer
GCP_PCDReady to test yourself?
A timed, blueprint-proportional exam drawn fresh from this bank — with a per-domain score report.
🔓 Free preview: showing 10 of 50 questions. Unlock the full bank — every question, explanation, and reference.
Unlock all 50 questions →10 questions across 5 topics. Choose an answer for each question, then check it to see the correct answer and explanation.
Filter by topic
10 questions in Designing highly scalable, available, and reliable cloud-native applications
DESIGN_APPS
Designing highly scalable, available, and reliable cloud-native applications
10 questions in topicTwelve-factor and microservice design, statelessness, resilience patterns, and choosing runtimes.
2
Single choice~110s
Because Pub/Sub delivers at-least-once, an order processor may receive the same message twice. How should it be designed for correct results?
3
Single choice~90s
A client calls a dependency that occasionally returns transient errors. Which retry strategy avoids overwhelming the recovering service?
4
Single choice~90s
A downstream service is failing repeatedly and slowing every caller. Which pattern lets callers fail fast and gives the dependency time to recover?
5
Single choice~70s
GKE must avoid sending traffic to a Pod that is running but not yet ready to serve. Which probe should the developer implement?
6
Single choice~90s
On scale-in, Cloud Run/GKE sends SIGTERM before stopping an instance. What should a well-behaved app do?
7
Single choice~90s
Per twelve-factor principles, where should configuration such as database URLs and API keys come from?
8
Single choice~110s
A long-running, stateful stream processor must maintain in-memory state for minutes and coordinate partitions. Which runtime fits BEST?
9
Single choice~90s
A stateless HTTP API has spiky traffic, must cost nothing when idle, and needs no cluster management. Which runtime fits BEST?
10
Single choice~100s
A read-heavy API repeatedly fetches the same records, adding latency and load; reads tolerate a few seconds of staleness. Which pattern helps MOST?