Your team is developing a backend application for an interactive voice response (IVR) system that handles payroll-related calls. The IVR system has these technical requirements:

Each customer call is tied to a unique IVR session.

A persistent gRPC connection is maintained between the IVR system and the backend for each session.

If the connection drops, the IVR system reconnects, introducing minor latency for that call.

Based on current call data:

Calls last between 1 and 30 minutes.

Call volume is highest during business hours.

Significant spikes occur around predictable events (e.g., paydays or major payroll changes).

The goal is to minimize cost, effort, and operational overhead. Which compute environment should host the backend application?

Exam-Like

Explanation:

Given the requirements for handling persistent gRPC connections, automatic scaling during traffic spikes, and minimizing operational overhead and costs, Cloud Run (D) is the most suitable option. It supports HTTP/2/gRPC, scales automatically, and allows for long-lived connections with a timeout of up to 60 minutes, which fits within the call duration range of 1 to 30 minutes. Additionally, Cloud Run abstracts away infrastructure management, reducing operational overhead. Compute Engine (A) and Google Kubernetes Engine (B) would require manual scaling and management, increasing operational overhead. Cloud Functions (C) is not suitable due to its execution time limit of 9 minutes and its event-driven nature, which is not ideal for long sessions.

Powered ByGPT-5

Google Professional Cloud Developer

Get started today

Google Professional Cloud Developer

Get started today