Topic 4 Question 5
For this question, refer to the EHR Healthcare case study. You are a developer on the EHR customer portal team. Your team recently migrated the customer portal application to Google Cloud. The load has increased on the application servers, and now the application is logging many timeout errors. You recently incorporated Pub/Sub into the application architecture, and the application is not logging any Pub/Sub publishing errors. You want to improve publishing latency. What should you do?
Increase the Pub/Sub Total Timeout retry value.
Move from a Pub/Sub subscriber pull model to a push model.
Turn off Pub/Sub message batching.
Create a backup Pub/Sub message queue.
ユーザの投票
コメント(17)
Answer : C (https://cloud.google.com/pubsub/docs/publisher?hl=en#batching) Cost of Batching is latency for individual messages,. To minimize latency batching should be turned off
👍 24raf21212021/08/23C - The cost of batching is latency for individual messages, which are queued in memory until their corresponding batch is filled and ready to be sent over the network. To minimize latency, batching should be turned off. https://cloud.google.com/pubsub/docs/publisher?hl=en#batching
A incorrect. Application timeout because of publisher latency, nothing to do with timeout retry with publish request. D does not make sense at all. B is about receiver, not publisher.
👍 8gingerbeer2021/10/02It's not about Latency so C is wrong, it's talking about timeout, I guess increasing the total timeout retry value will help hence answer is A
Total timeout: the amount of time after a client library stops retrying publish requests.
👍 4BrijMohan082021/09/28
シャッフルモード