Exam Professional Cloud Developer topic 1 question 318 discussion

Ticket reservations need to be processed immediately, so synchronous processing is appropriate rather than asynchronous processing (A, B, C). By adopting an architecture that accepts HTTP POST requests directly (D), can provide customers with real-time seat confirmation.

The question is about *immediate* confirmation and async processing is not the best candidate here (even in practice makes more sense) B. Pub/Sub/Eventarc/GKE: Pub/Sub is an asynchronous messaging system. Eventarc further adds a layer of event routing. This introduces more latency than a direct request. D. HTTP POST/Application Load Balancer/Compute Engine: This is the most direct and suitable approach for immediate confirmation. The HTTP POST request is sent to the backend service (Compute Engine instances), which processes the reservation synchronously and immediately returns a confirmation to the user. The Application Load Balancer ensures high availability and distributes the load.

Asynchronous Processing: By using Pub/Sub, you can publish the seat reservation message immediately, allowing for quick acknowledgment to the customer without waiting for the backend processing to complete. This ensures that users receive confirmation right away, improving the user experience. Eventarc Integration: Eventarc can be configured to route events from Pub/Sub to your backend service running on GKE. This allows for flexibility and scalability, as your service can automatically handle incoming requests based on events published to the topic.