The answer is to use a Pub/Sub topic as a buffer and autoscale consumer pods based on Pub/Sub subscription backlog. This pattern is correct because Pub/Sub acts as a durable, scalable buffer that decouples data producers from consumers, allowing the streaming application on GKE to absorb sudden traffic spikes without dropping data. The key technical concept is that by monitoring the subscription backlog (the number of unacknowledged messages), you can trigger Horizontal Pod Autoscaling to dynamically spin up more consumer pods exactly when demand surges, ensuring throughput scales with load. On the Google Professional Data Engineer exam, this question tests your understanding of decoupling patterns for streaming workloads, a common scenario where candidates mistakenly choose static overprovisioning or database-based buffering. A frequent trap is assuming Cloud SQL can handle high-throughput buffering, but it lacks Pub/Sub’s native autoscaling and durability guarantees. Memory tip: think “Backlog = Burst” — when the backlog grows, pods must burst to match it.
PDE Ensuring solution quality Practice Question
This PDE practice question tests your understanding of ensuring solution quality. Compare every option against the stated constraints before choosing — the best answer satisfies all requirements, not just the most obvious one. 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 is deploying a large-scale streaming application on Google Kubernetes Engine. They need to ensure the application can handle sudden traffic spikes without dropping data. Which architectural pattern is most appropriate?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a Pub/Sub topic as a buffer and autoscale consumer pods based on Pub/Sub subscription backlog.
Option A is correct because using a Pub/Sub buffer decouples producers from consumers, allowing autoscaling of consumers to handle spikes. Option B is wasteful and not dynamically scalable. Option C uses Cloud SQL, which is not designed for high-throughput buffering. Option D only addresses retries, not overall throughput capacity.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Implement custom retry logic with exponential backoff in the application.
Why it's wrong here
Retry logic only handles transient failures; it does not provide capacity to absorb traffic spikes.
✗
Use Cloud SQL as a temporary buffer and process from there.
Why it's wrong here
Cloud SQL is not designed for high-throughput streaming buffering and can become a bottleneck.
✗
Pre-provision 3x the expected peak capacity to handle spikes.
Why it's wrong here
Pre-provisioning is wasteful and does not dynamically adapt; it can lead to unused resources.
✓
Use a Pub/Sub topic as a buffer and autoscale consumer pods based on Pub/Sub subscription backlog.
Why this is correct
Pub/Sub provides a highly scalable buffer; autoscaling consumers based on backlog ensures capacity matches demand.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related PDE NAT questions on configuration and troubleshooting.
Ensuring solution quality — This question tests Ensuring solution quality — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use a Pub/Sub topic as a buffer and autoscale consumer pods based on Pub/Sub subscription backlog. — Option A is correct because using a Pub/Sub buffer decouples producers from consumers, allowing autoscaling of consumers to handle spikes. Option B is wasteful and not dynamically scalable. Option C uses Cloud SQL, which is not designed for high-throughput buffering. Option D only addresses retries, not overall throughput capacity.
What should I do if I get this PDE question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related PDE NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 PDE 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 PDE 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.