A financial analytics company is migrating two backend processing workloads to Google Cloud serverless platforms to eliminate server management overhead:
1. Workload 1: A real-time market data streaming microservice packaged as a custom container image that requires persistent WebSocket connections and needs to process up to 80 concurrent client requests per container instance.
2. Workload 2: A lightweight audit logging script that must execute automatically whenever a new transaction report file is uploaded to a Cloud Storage bucket.
Which TWO architectural choices should the cloud engineering team select to satisfy these workload requirements efficiently? (Select TWO answers.)
- Deploy Workload 1 to Cloud Run, because it supports custom container images, persistent WebSockets, and configurable request concurrency per instance.Cevap
- Deploy Workload 2 to Cloud Functions (2nd gen) configured with an Eventarc Cloud Storage trigger to automatically execute code upon file creation.Cevap
- CDeploy Workload 1 to Cloud Functions (1st gen), because it natively supports custom multi-container deployments and high request concurrency per instance.
- DDeploy Workload 2 to Compute Engine Spot VMs with an unmanaged instance group to poll the Cloud Storage bucket for uploaded reports.
Cevap
The correct architectural choices are deploying Workload 1 to Cloud Run (supporting custom containers, WebSockets, and concurrency) and deploying Workload 2 to Cloud Functions 2nd gen (handling event-driven Cloud Storage triggers directly).
Cloud Run is optimal for Workload 1 because it natively runs custom container images, supports persistent connections like WebSockets, and handles multiple concurrent requests per instance. Cloud Functions (2nd gen) is optimal for Workload 2 because it offers direct integration with Cloud Storage bucket events via Eventarc to execute lightweight code snippets serverlessly.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless compute paradigms: Cloud Run for containerized HTTP/WebSocket microservices requiring concurrency vs Cloud Functions for event-driven snippet execution.