PROFESSIONAL-CLOUD-DEVELOPER · Question #243
Your team is writing a backend application to implement the business logic for an interactive voice response (IVR) system that will support a payroll application. The IVR system has the following tech
The correct answer is D. Cloud Run. Cloud Run is the best fit for this workload. It natively supports gRPC (including bidirectional streaming), allows request timeouts up to 60 minutes (covering the maximum 30-minute call duration), auto-scales to zero during off-hours (reducing costs for business-hours-only traffi
Question
Your team is writing a backend application to implement the business logic for an interactive voice response (IVR) system that will support a payroll application. The IVR system has the following technical characteristics:
- Each customer phone call is associated with a unique IVR session.
- The IVR system creates a separate persistent gRPC connection to the
backend for each session.
- If the connection is interrupted, the IVR system establishes a new
connection, causing a slight latency for that call. You need to determine which compute environment should be used to deploy the backend application. Using current call data, you determine that:
- Call duration ranges from 1 to 30 minutes.
- Calls are typically made during business hours.
- There are significant spikes of calls around certain known dates
(e.g., pay days), or when large payroll changes occur. You want to minimize cost, effort, and operational overhead. Where should you deploy the backend application?
Options
- ACompute Engine
- BGoogle Kubernetes Engine cluster in Standard mode
- CCloud Functions
- DCloud Run
How the community answered
(28 responses)- A4% (1)
- B4% (1)
- C11% (3)
- D82% (23)
Explanation
Cloud Run is the best fit for this workload. It natively supports gRPC (including bidirectional streaming), allows request timeouts up to 60 minutes (covering the maximum 30-minute call duration), auto-scales to zero during off-hours (reducing costs for business-hours-only traffic), and scales rapidly to handle call spikes. Option A (Compute Engine) requires manual or policy-based scaling and is harder to manage for variable traffic. Option B (GKE Standard) can handle gRPC and long sessions but adds significant cluster management overhead and doesn't scale to zero by default. Option C (Cloud Functions) is not designed for persistent, long-lived connections - it has short execution timeouts by default and does not support stateful gRPC sessions the way Cloud Run does.
Topics
Community Discussion
No community discussion yet for this question.