ASSOCIATE-DATA-PRACTITIONER practice question 15 of 25

Your organization sends IoT event data to a Pub/Sub topic. Subscriber applications read and perform transformations on the messages before storing…

Full set: 106 questions
Your organization sends IoT event data to a Pub/Sub topic. Subscriber applications read and perform transformations on the messages before storing them in the data warehouse. During particularly busy times when more data is being written to the topic, you notice that the subscriber applications are not acknowledging messages within the deadline. You need to modify your pipeline to handle these activity spikes and continue to process the messages. What should you do?
Answer options
A: Retry messages until they are acknowledged.
B: Implement flow control on the subscribers Correct answer
C: Forward unacknowledged messages to a dead-letter topic.
D: Seek back to the last acknowledged message.
Correct Answer:
B. Implement flow control on the subscribers
Explanation

The subscriber applications are overwhelmed by the volume of messages during peak times, causing them to miss acknowledgment deadlines. Implementing flow control on the subscribers allows them to limit the rate and number of messages they pull from the topic at any given time. This prevents the subscribers from being overloaded, enabling them to process and acknowledge messages within the deadline, thus resolving the issue of repeated message deliveries and ensuring the pipeline remains stable during activity spikes.

Why Incorrect

A. Retrying is the default Pub/Sub behavior for unacknowledged messages; it is the source of the problem, not the solution.
C. A dead-letter topic is for messages that fail processing repeatedly, not for managing high throughput. This would cause data loss.
D. Seeking is used to replay messages from a specific point in time and does not address the subscriber's inability to handle the current load.

References

1. Google Cloud Documentation, "Pub/Sub - Receiving messages using Pull," Section: Flow control. "To avoid being overwhelmed by messages, the subscriber can configure flow control settings. Flow control lets you set limits on the number of messages and the total megabytes of data that are buffered in memory."

2. Google Cloud Documentation, "Pub/Sub - Subscriber push and pull," Section: Pull subscriber flow control. "Flow control can prevent the subscriber from being overwhelmed with more messages than it can process."

Scroll to Top