The answer is a managed instance group with autoscaling based on CPU utilization, as this directly enables cost-effective scaling for Compute Engine traffic spikes. For a stateless web app, this approach dynamically adjusts the number of VM instances in real-time according to CPU load, ensuring you provision only the compute resources needed during demand surges and scale down when traffic subsides, eliminating wasted spend on idle capacity. On the Google Professional Cloud Developer exam, this scenario tests your understanding of stateless architecture patterns and autoscaling policies, often appearing as a trap where candidates mistakenly choose preemptible VMs or regional load balancing without considering the stateless requirement. The key insight is that CPU-based autoscaling in MIGs perfectly aligns with the ephemeral nature of stateless apps, allowing instances to be terminated without data loss. Memory tip: think “Stateless + Spikes = CPU Autoscale” to avoid over-provisioning costs.
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 startup is deploying a stateless web app on Compute Engine. They expect traffic spikes. What is the most cost-effective way to handle scaling?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use managed instance groups with autoscaling based on CPU utilization.
Managed instance groups (MIGs) with autoscaling based on CPU utilization are the most cost-effective solution for a stateless web app with traffic spikes because they automatically add or remove VM instances in response to real-time CPU load, ensuring you only pay for the compute resources you actually use. This approach directly matches the stateless nature of the app, allowing instances to be created and destroyed without data loss, and avoids over-provisioning or under-utilizing resources.
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.
✗
Use App Engine Standard.
Why it's wrong here
App Engine Standard is serverless but may not be as cost-effective if the app is already on Compute Engine.
✗
Use a single large VM with more cores.
Why it's wrong here
Single VM is not horizontally scalable and can be a single point of failure.
✓
Use managed instance groups with autoscaling based on CPU utilization.
Why this is correct
MIG with autoscaling scales horizontally and cost-effectively.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use Cloud Functions.
Why it's wrong here
Cloud Functions is event-driven, not ideal for a web app with traffic spikes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that serverless options like App Engine or Cloud Functions are always the most cost-effective for any web app, but the trap here is that for a stateless web app with traffic spikes, managed instance groups with autoscaling provide finer control over scaling behavior and can be more cost-effective than paying for always-on App Engine instances or the per-invocation cost of Cloud Functions for sustained HTTP traffic.
Detailed technical explanation
How to think about this question
Under the hood, MIGs with autoscaling use the Compute Engine autoscaler, which polls the selected metric (e.g., CPU utilization) every 60 seconds and applies a formula to calculate the desired number of instances based on target utilization (e.g., 60%). The autoscaler supports multiple signal types (e.g., HTTP load balancing utilization, Stackdriver metrics) and can scale down gracefully with a cooldown period (default 60 seconds) to avoid thrashing. In real-world scenarios, combining MIGs with a global HTTP(S) load balancer and preemptible VMs for burst capacity can further reduce costs while maintaining availability.
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: Use managed instance groups with autoscaling based on CPU utilization. — Managed instance groups (MIGs) with autoscaling based on CPU utilization are the most cost-effective solution for a stateless web app with traffic spikes because they automatically add or remove VM instances in response to real-time CPU load, ensuring you only pay for the compute resources you actually use. This approach directly matches the stateless nature of the app, allowing instances to be created and destroyed without data loss, and avoids over-provisioning or under-utilizing resources.
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.