Answer-first summary for fast verification
Answer: Turn off Pub/Sub message batching.
The correct answer is option C: 'Turn off Pub/Sub message batching.' When message batching is used, messages are queued in memory until the batch is filled, which adds latency for individual messages. Turning off batching ensures that messages are sent as soon as they are published, thus reducing latency. This is supported by Google's documentation on Pub/Sub publishing best practices and by user feedback indicating that turning off batching minimizes latency issues.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Refer to the EHR Healthcare case study. As a developer on the EHR customer portal team, your team has recently migrated the customer portal application to Google Cloud. Consequently, the load on the application servers has increased, leading to many timeout errors being logged by the application. You had recently integrated Pub/Sub into the application architecture. However, the application is not logging any Pub/Sub publishing errors. You aim to improve the publishing latency. Given this context, what should you do?
A
Increase the Pub/Sub Total Timeout retry value.
B
Move from a Pub/Sub subscriber pull model to a push model.
C
Turn off Pub/Sub message batching.
D
Create a backup Pub/Sub message queue.