Answer-first summary for fast verification
Answer: Create one Pub/Sub topic. Create one pull subscription to allow the audit services to share the messages.
To efficiently handle a large volume of messages and ensure scalability, the best approach is to use a single Pub/Sub topic for all authentication services to publish audit events. This centralizes the event stream. For the audit services, a single pull subscription is recommended. This setup allows multiple audit service instances to share the message processing load, as each message is delivered to only one instance, enabling horizontal scaling. This method is efficient and scalable, making it the optimal choice for high-throughput scenarios.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
How should you configure Pub/Sub topics and subscriptions to efficiently handle a high volume of audit events in a scalable architecture where:
(Ensure the solution supports large-scale message throughput and optimal scaling.)
A
Create one Pub/Sub topic. Create one pull subscription to allow the audit services to share the messages.
B
Create one Pub/Sub topic. Create one pull subscription per audit service instance to allow the services to share the messages.
C
Create one Pub/Sub topic. Create one push subscription with the endpoint pointing to a load balancer in front of the audit services.
D
Create one Pub/Sub topic per authentication service. Create one pull subscription per topic to be used by one audit service.
E
Create one Pub/Sub topic per authentication service. Create one push subscription per topic, with the endpoint pointing to one audit service.
No comments yet.