An enterprise organization is planning to migrate a stateless HTTP web application to Google Cloud. The application is packaged as a custom Docker container image containing specialized binary dependencies, but it does not require low-level Linux kernel modifications or persistent disk storage. Traffic to the application is highly sporadic with unpredictable volume spikes, and the team requires the solution to scale down to zero instances during idle periods to eliminate unnecessary compute costs. The operations team has strictly mandated that infrastructure and server management overhead must be kept to an absolute minimum. Which GCP compute option should you recommend?
- Deploy the application container directly to Cloud Run.Cevap
- BDeploy the application container as a Deployment workload in a Google Kubernetes Engine (GKE) Autopilot cluster.
- CDeploy the container across a Managed Instance Group (MIG) using Compute Engine Spot VMs with an autoscaling policy.
- DRefactor the application code into a single Cloud Functions (1st gen) instance.
Cevap
Deploy the application container directly to Cloud Run.
Deploying directly to Cloud Run is correct because Cloud Run is a fully managed serverless execution environment designed specifically for stateless HTTP container workloads. It natively accepts custom Docker images, automatically scales to zero when idle to eliminate cost, and requires zero node or cluster management overhead.
Adım Adım Çözüm
Anahtar Kavram
Selecting and planning GCP compute options based on operational overhead, containerization, and scaling requirements.
Tahmini Süre:2m 0s