Topic 1 Question 38
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?
Retry messages until they are acknowledged.
Implement flow control on the subscribers.
Forward unacknowledged messages to a dead-letter topic.
Seek back to the last acknowledged message.
ユーザの投票
コメント(2)
- 正解だと思う選択肢: B
The best solution is B. Implement flow control on the subscribers. Flow control directly addresses the issue of subscribers being overwhelmed during activity spikes by regulating the rate of message delivery, preventing them from being overloaded and ensuring messages are acknowledged within the deadline. Option A (Retry) worsens overload. Option C (Dead-letter topic) is for handling failed messages, not overload, and risks data loss in this scenario. Option D (Seek back) is for reprocessing and would exacerbate the overload issue. Therefore, Option B is the correct and most effective approach to handle activity spikes and ensure continuous message processing.
👍 1n21837128472025/02/27 - 正解だと思う選択肢: B
Flow control helps with spikes.
👍 1n21837128472025/03/08
シャッフルモード