An enterprise logistics organization is designing the architecture on Google Cloud for two new distinct internal applications. The first application is an event-driven stateless HTTP webhook service that receives unpredictable bursty traffic and must scale to zero instances during quiet hours to minimize idle costs. The second application is a legacy backend routing daemon that requires custom OS kernel network parameters (sysctl tuning) and raw non-HTTP TCP protocol bindings. Which TWO compute architecture options should you select to meet these technical requirements while minimizing operational overhead? (Select TWO)
- Deploy the stateless event-driven HTTP webhook service to fully managed Cloud Run.Cevap
- Deploy the legacy backend routing daemon requiring kernel sysctl tuning to Compute Engine Virtual Machines.Cevap
- CDeploy the stateless event-driven HTTP webhook service onto a dedicated Google Kubernetes Engine (GKE) Standard cluster.
- DDeploy the legacy backend routing daemon to Cloud Run by packaging the custom sysctl kernel modules inside the container image.
- EPurchase 3-year Committed Use Discounts (CUDs) for the peak resource requirements of the stateless HTTP webhook service.
Cevap
Select Cloud Run for the stateless HTTP webhook service and Compute Engine VMs for the legacy backend routing daemon.
Cloud Run provides serverless stateless container execution with scale-to-zero functionality, perfectly matching the HTTP webhook workload while minimizing operational overhead. Compute Engine provides root-level OS access and kernel customizability needed for sysctl tuning and custom network protocols.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Compute Platforms based on statefulness, OS control, scaling characteristics, and operational overhead.