Topic 1 Question 109
2 つ選択You have Cloud Functions written in Node.js that pull messages from Cloud Pub/Sub and send the data to BigQuery. You observe that the message processing rate on the Pub/Sub topic is orders of magnitude higher than anticipated, but there is no error logged in Cloud Logging. What are the two most likely causes of this problem?
Publisher throughput quota is too small.
Total outstanding messages exceed the 10-MB maximum.
Error handling in the subscriber code is not handling run-time errors properly.
The subscriber code cannot keep up with the messages.
The subscriber code does not acknowledge the messages that it pulls.
ユーザの投票
コメント(8)
Answer C E By not acknowleding the pulled message, this result in it be putted back in Cloud Pub/Sub, meaning the messages accumulate instead of being consumed and removed from Pub/Sub. The same thing can happen ig the subscriber maintains the lease on the message it receives in case of an error. This reduces the overall rate of processing because messages get stuck on the first subscriber. Also, errors in Cloud Function do not show up in Stackdriver Log Viewer if they are not correctly handled.
👍 9TNT872022/09/13- 正解だ と思う選択肢: CE
C. Error handling in the subscriber code is not handling run-time errors properly. E. The subscriber code does not acknowledge the messages that it pulls.
👍 3AWSandeep2022/09/03 D might also be right? Subscriber might not be provisioned enough
👍 3MounicaN2022/09/11
シャッフルモード