Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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:
Which Pub/Sub consumption pattern and configuration should the cloud architect implement?
Pub/Sub push subscriptions deliver messages by having the Pub/Sub service initiate outbound HTTPS POST requests to a publicly accessible webhook or load balancer endpoint.
The subscriber service was a serverless target such as Cloud Run or Cloud Functions that auto-scales based on incoming HTTP requests and handles steady, moderate traffic volumes.
Push subscriptions are ideal for webhook-driven architectures, but they lack the low overhead and client-driven backpressure management required for high-throughput containerized workers.
Eventarc captures events from Google Cloud services and routes them to destinations like Cloud Workflows, which orchestrates multi-step business logic and service integrations using declarative YAML or JSON workflows.
The requirement was to orchestrate long-running, multi-step business workflows across disparate enterprise services (such as approval chains or multi-system database updates) triggered by low-frequency events.
While Eventarc and Workflows provide excellent decoupling for control-plane and integration events, core high-volume data-plane ingestion requires native Pub/Sub streaming subscribers.
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.

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.
Synchronous unary pull uses standard request-response RPC calls (projects.subscriptions.pull) where the client sends a separate request to the Pub/Sub API and waits for a single response containing zero or more messages.
returnImmediately=true causes tight polling loops that burn CPU and frequently return zero messages.returnImmediately degrade efficiency and cause empty responses even when a backlog exists.The application were a batch script or a resource-constrained client that only needs to fetch a fixed number of messages intermittently and exit immediately.
Unary pull APIs are intended for niche use cases with strict synchronous programming requirements rather than low-latency, mission-critical event streaming.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated