A global retail company is architecting an event-driven transaction processing system on Google Cloud to handle millions of checkout events per minute during seasonal flash sales. The event processing workload runs on Google Kubernetes Engine (GKE) worker pods. The architecture must meet the following requirements: Deliver maximum throughput and lowest end-to-end delivery latency for high-volume message streams Prevent subscriber worker pods from exhausting memory and crashing during sudden traffic bursts Dynamically regulate the rate of delivered messages by bounding outstanding unacknowledged messages per worker Which Pub/Sub consumption pattern and configuration should the cloud architect implement?

Configure a Pub/Sub pull subscription using the high-level client library with StreamingPull and subscriber flow control limits enabled: ### What StreamingPull with Flow Control is **Pub/Sub StreamingPull** is a bidirectional streaming RPC mechanism implemented by Google Cloud high-level client libraries. It establishes a persistent, open gRPC connection between the subscriber client and Pub/Sub servers, allowing messages to be streamed immediately to the subscriber as soon as they are published. **Subscriber flow control** is a client-side setting that limits the maximum number of outstanding unacknowledged messages or total message bytes held in memory simultaneously. ### How it meets the requirements - **Maximum throughput and lowest latency**: **StreamingPull** avoids the overhead of repeated HTTP/unary RPC roundtrips by keeping persistent streams open, achieving high-throughput and sub-second delivery latencies. - **Burst protection and resource safety**: **Subscriber flow control** enforces upper bounds on outstanding messages, preventing workers from fetching more data than their CPU and memory buffers can process during sudden spikes. - **Dynamic regulation**: The high-level client library pauses pulling additional messages when configured flow control limits are reached and resumes automatically as existing messages are acknowledged. ### Key advantages and capabilities - **Bidirectional communication**: Utilizes efficient gRPC streams to deliver messages and send acknowledgments back over the same channel. - **Automated lease management**: High-level client libraries automatically extend message acknowledgment deadlines while processing is ongoing. - **Client-side concurrency**: Enables fine-grained tuning of parallel processing threads alongside memory protection. - **Integrated autoscaling signals**: Can be paired with Horizontal Pod Autoscaler (HPA) using undelivered message metrics. ### Why this is optimal Compared to push subscriptions or unary pull loops, **StreamingPull** via high-level client libraries provides optimal performance for heavy enterprise workloads, ensuring resilient backpressure handling and avoiding worker crashes under high load.

StudyCerts

Pubsub Streamingpull Flow Control Gke | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Pubsub Streamingpull Flow Control Gke

Section: Supporting the application design

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

A global retail company is architecting an event-driven transaction processing system on Google Cloud to handle millions of checkout events per minute during seasonal flash sales. The event processing workload runs on Google Kubernetes Engine (GKE) worker pods.

The architecture must meet the following requirements:

Deliver maximum throughput and lowest end-to-end delivery latency for high-volume message streams
Prevent subscriber worker pods from exhausting memory and crashing during sudden traffic bursts
Dynamically regulate the rate of delivered messages by bounding outstanding unacknowledged messages per worker

Which Pub/Sub consumption pattern and configuration should the cloud architect implement?

Configure a Pub/Sub pull subscription using the high-level client library with StreamingPull and subscriber flow control limits enabled

Configure a Pub/Sub push subscription targeting an HTTPS endpoint exposed by an ingress load balancer in GKE

Configure a Pub/Sub pull subscription using the unary Pull API in a synchronous loop with the returnImmediately parameter enabled

Configure an Eventarc trigger routed to a Cloud Workflows destination that pulls Pub/Sub messages sequentially using scheduled sleep steps

Professional Cloud Architect

Pubsub Streamingpull Flow Control Gke

Related questions