You recently developed an application that monitors a large number of stock prices. You need to configure Pub/Sub to receive a high volume messages and update the current stock price in a single…

Question

Options

• ACreate a pull subscription with exactly-once delivery enabled.
• BCreate a push subscription with both ordering and exactly-once delivery turned off.
• CCreate a push subscription with exactly-once delivery enabled.
• DCreate a pull subscription with both ordering and exactly-once delivery turned off.

• A
  16% (6)
• B
  8% (3)
• C
  71% (27)
• D
  5% (2)

Explanation

A push subscription with exactly-once delivery is appropriate here. Push mode has Pub/Sub proactively deliver messages to your endpoint as they arrive, giving the in-memory database near-real-time updates with minimal latency. Exactly-once delivery ensures each stock price update is applied exactly one time - critical for an in-memory store where duplicate writes could corrupt the current price or trigger erroneous trades. Pull subscriptions (A, D) require the consumer to request messages, introducing polling delays that are unsuitable for high-frequency stock updates. Option B turns off exactly-once delivery, risking duplicate price writes. Option D also disables ordering and exactly-once, meaning an older price could overwrite a newer one and duplicates could occur.

No community discussion yet for this question.