The answer is Cloud Run, the most cost-effective and operationally simple choice for a stateless web application with unpredictable traffic spikes. This is because Cloud Run automatically scales from zero to thousands of containers based on incoming request load, and you only pay for the resources consumed during request processing, billed in 100-millisecond increments. On the Google Professional Cloud Developer exam, this scenario tests your understanding of serverless compute trade-offs: Cloud Functions suffers from cold-start latency for web apps, while GKE requires cluster management overhead. A common trap is choosing App Engine, but Cloud Run offers greater flexibility with any containerized language or framework. Remember the mnemonic “Zero to Scale, Pay per Request” to instantly recall that Cloud Run’s idle scaling and granular billing make it ideal for unpredictable, stateless HTTP workloads.
PCD Practice Question: Designing highly scalable, available, and reliable cloud-native applications
This PCD practice question tests your understanding of designing highly scalable, available, and reliable cloud-native applications. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A company wants to deploy a stateless web application that needs to handle unpredictable traffic spikes with minimal operational overhead. Which Google Cloud compute service is most cost-effective and operationally simple?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Cloud Run
Cloud Run is the most cost-effective and operationally simple choice for a stateless web application with unpredictable traffic spikes because it automatically scales from zero to thousands of containers based on request load, charges only for resources used during request processing (down to 100ms increments), and eliminates infrastructure management. It supports any language or framework via container images, making it ideal for stateless HTTP workloads without the cold-start latency concerns of Cloud Functions or the cluster management overhead of GKE.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
App Engine Standard
Why it's wrong here
Managed but limited to specific runtimes and scaling settings.
✗
Cloud Functions
Why it's wrong here
Best for event-driven workloads, not continuous web serving.
✓
Cloud Run
Why this is correct
Fully managed, autoscaling to zero, per-request pricing, ideal for stateless web apps.
Related concept
Read the scenario before looking for a memorised answer.
✗
Google Kubernetes Engine (GKE)
Why it's wrong here
Good for containers but adds cluster management overhead.
✗
Compute Engine with Managed Instance Group
Why it's wrong here
Requires manual scaling configuration and infrastructure management.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose App Engine Standard (A) thinking it is the only serverless option for web apps, but Cloud Run offers greater flexibility with containerized workloads and more granular scaling to zero, making it more cost-effective for unpredictable traffic patterns.
Detailed technical explanation
How to think about this question
Cloud Run runs on Knative, an open-source platform built on Kubernetes, but abstracts away the cluster entirely — it uses a request-driven autoscaler that can scale from 0 to N instances based on concurrent request count, with each container instance handling multiple requests concurrently via HTTP/2 multiplexing. A subtle behavior is that Cloud Run's 'CPU always allocated' vs 'CPU only during request' billing model allows cost optimization for background processing, but for stateless web apps the default 'CPU only during request' model ensures you never pay for idle CPU, making it ideal for unpredictable spikes where traffic can drop to zero.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Designing highly scalable, available, and reliable cloud-native applications — This question tests Designing highly scalable, available, and reliable cloud-native applications — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Cloud Run — Cloud Run is the most cost-effective and operationally simple choice for a stateless web application with unpredictable traffic spikes because it automatically scales from zero to thousands of containers based on request load, charges only for resources used during request processing (down to 100ms increments), and eliminates infrastructure management. It supports any language or framework via container images, making it ideal for stateless HTTP workloads without the cold-start latency concerns of Cloud Functions or the cluster management overhead of GKE.
What should I do if I get this PCD question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PCD practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCD exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.