An online retail organization is designing a serverless backend infrastructure on Google Cloud to handle two distinct operational workloads:
1. Workload A: A high-throughput API gateway service packaged as a custom Docker container image that must handle up to 80 concurrent HTTP requests per instance to optimize resource utilization.
2. Workload B: A lightweight event processor executing a single JavaScript file whenever a new PDF invoice is generated and saved to a Cloud Storage bucket.
Which two architectural decisions should the cloud engineer select to meet these requirements with minimal operational overhead? (Select TWO)
- Deploy Workload A to Cloud Run and configure container concurrency to allow multiple requests per instance.Cevap
- Deploy Workload B as a Cloud Function configured with a Cloud Storage event trigger.Cevap
- CDeploy Workload A to Cloud Functions to leverage native container image multi-concurrency.
- DDeploy both Workload A and Workload B onto a managed Compute Engine instance group to avoid serverless cold starts.
Cevap
Deploy Workload A to Cloud Run with multi-request concurrency configured, and deploy Workload B to Cloud Functions triggered directly by Cloud Storage events.
Cloud Run is the optimal platform for Workload A because it allows deploying custom Docker containers with configured concurrency to process up to 80 requests simultaneously per container instance. Cloud Functions is the optimal choice for Workload B because it natively integrates with Cloud Storage events to execute lightweight code snippets without needing container maintenance.
Adım Adım Çözüm
Anahtar Kavram
Differentiating serverless compute platforms (Cloud Run vs. Cloud Functions) based on containerization, concurrency capabilities, and event trigger mechanisms.