Your team is using App Engine to write every Cloud Pub/Sub message to both a Cloud Storage object and a BigQuery table. You want to achieve the greatest resource efficiency. Which architecture…

The correct answer is D. D. The most resource-efficient architecture uses a single App Engine service with one Pub/Sub push subscription. When a message arrives, the push endpoint triggers one App Engine instance that writes to both Cloud Storage and BigQuery in the same request handler - no redundant…

Data Processing and Integration

Question

Your team is using App Engine to write every Cloud Pub/Sub message to both a Cloud Storage object and a BigQuery table. You want to achieve the greatest resource efficiency. Which architecture should you implement?

Exhibit

Options

How the community answered

(40 responses)

A
15% (6)
B
8% (3)
C
3% (1)
D
75% (30)

Explanation

The most resource-efficient architecture uses a single App Engine service with one Pub/Sub push subscription. When a message arrives, the push endpoint triggers one App Engine instance that writes to both Cloud Storage and BigQuery in the same request handler - no redundant instances, no duplicate subscriptions, and no intermediate processing steps. Less efficient alternatives (options A, B, C) likely involve multiple subscriptions, separate services for each destination, or pull-based polling that wastes resources when there are no messages. A single push-triggered handler that fans out to both sinks minimizes compute overhead.

Topics

#Serverless Architecture#Data Ingestion#Resource Optimization#Messaging Services

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice