An organization is planning to deploy a stateless HTTP microservice to Google Cloud. The application requires a custom system library compiled into a custom Linux container image and must handle up to 80 concurrent HTTP requests per container instance to optimize resource utilization and reduce cost during peak load. Which Google Cloud serverless compute option should you select to fulfill these architectural requirements?
- Deploy the custom container image to Cloud Run and configure the concurrency setting to 80.Answer
- BDeploy the workload as a 1st gen Cloud Functions HTTP trigger, specifying a custom container image in the deployment configuration.
- CDeploy the workload to Compute Engine using a Managed Instance Group composed exclusively of Spot VMs behind a Load Balancer.
- DDeploy the code to App Engine Flexible environment and hardcode the container port to listen on port 80 instead of reading environment variables.
Answer
Deploying the custom container image to Cloud Run while configuring maximum concurrency to 80 meets all requirements for custom binary container support and concurrent request handling.
Cloud Run is designed to execute stateless container images invoked via HTTP requests. It allows developers to deploy arbitrary container images containing custom system dependencies and supports serving multiple concurrent requests (up to 1000 per instance, default 80) on a single container instance.
Step-by-Step Solution
Key Concept
Cloud Run Concurrency and Custom Container Support
Estimated Time:1m 30s