PROFESSIONAL-CLOUD-DEVELOPER Question #111: Real Exam Question with Answer & Explanation

Question

You need to redesign the ingestion of audit events from your authentication service to allow it to handle a large increase in traffic. Currently, the audit service and the authentication system run in the same Compute Engine virtual machine. You plan to use the following Google Cloud tools in the new architecture: - Multiple Compute Engine machines, each running an instance of the authentication service - Multiple Compute Engine machines, each running an instance of the audit service - Pub/Sub to send the events from the authentication services. How should you set up the topics and subscriptions to ensure that the system can handle a large volume of messages and can scale efficiently?

Options

• ACreate one Pub/Sub topic. Create one pull subscription to allow the audit services to share the
• BCreate one Pub/Sub topic. Create one pull subscription per audit service instance to allow the
• CCreate one Pub/Sub topic. Create one push subscription with the endpoint pointing to a load
• DCreate one Pub/Sub topic per authentication service. Create one pull subscription per topic to be
• ECreate one Pub/Sub topic per authentication service. Create one push subscription per topic, with

Explanation

https://cloud.google.com/pubsub/docs/subscriber Multiple subscribers can make pull calls to the same "shared" subscription. Each subscriber will receive a subset of the messages.

No community discussion yet for this question.