An online gaming company is designing its Google Cloud compute architecture for two core backend services with distinct requirements:
1. Service A: A stateless containerized microservice that handles incoming REST API player requests, experiences unpredictable traffic spikes, and requires zero cluster node administration with the ability to scale to zero instances.
2. Service B: A legacy physics engine that requires custom Linux kernel patches and direct root access to the host virtual machine operating system.
Which TWO compute strategies should the cloud engineer choose to meet these requirements with optimal operational efficiency? (Select TWO)
- Deploy Service A on Cloud Run to leverage fully managed serverless container execution with automatic scaling to zero.Cevap
- Deploy Service B on Compute Engine Virtual Machines to support direct access to the host OS and custom kernel module installations.Cevap
- CDeploy Service A on Cloud Functions to host the full multi-container REST API application framework.
- DDeploy Service B on Google Kubernetes Engine (GKE) Autopilot clusters to automate custom Linux kernel configuration on underlying nodes.
- EDeploy Service B on Spot Compute Engine Virtual Machines to permanently retain custom kernel settings while guaranteeing fault tolerance.
Cevap
Deploy Service A on Cloud Run and deploy Service B on Compute Engine Virtual Machines.
Cloud Run provides serverless container management for stateless HTTP services with zero node overhead and scale-to-zero capabilities. Compute Engine virtual machines provide Infrastructure-as-a-Service access, allowing arbitrary OS-level customization and custom Linux kernel patches.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Compute Services Based on Workload Constraints and OS Requirements