Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
A company has developed a custom containerized API packaged as a standard OCI container image. The workload exhibits highly sporadic and unpredictable traffic patterns throughout the day, often experiencing several consecutive hours of zero incoming traffic.
The architecture team has established the following operational and economic requirements:
Which architecture should the cloud architect recommend?
Refactor the service logic into Cloud Run functions triggered by HTTP requests with minimum instances set to zero
Deploy the container to a Google Kubernetes Engine (GKE) Autopilot cluster and configure the Horizontal Pod Autoscaler (HPA) to scale deployment replicas to zero
Deploy the container using Compute Engine managed instance groups (MIGs) with schedule-based autoscaling
Deploy the container to Cloud Run with CPU allocated only during request processing and enable Startup CPU Boost
Refactor the service logic into Cloud Run functions triggered by HTTP requests with minimum instances set to zero
Deploy the container to a Google Kubernetes Engine (GKE) Autopilot cluster and configure the Horizontal Pod Autoscaler (HPA) to scale deployment replicas to zero
Deploy the container using Compute Engine managed instance groups (MIGs) with schedule-based autoscaling
Deploy the container to Cloud Run with CPU allocated only during request processing and enable Startup CPU Boost
Cloud Run is a fully managed serverless compute platform that runs stateless OCI containers directly on Google Cloud infrastructure. It provides native scale-to-zero capabilities, automatically terminating container instances when there are no inbound HTTP requests and dynamically instantiating new instances as demand arrives.
cpuIdle: true) ensures that billable vCPU seconds are tracked exclusively while handling active requests rather than charging for idle container background time.This approach delivers the exact balance between scale-to-zero cost efficiency, fast startup performance, and full container portability without the management overhead of underlying cluster nodes or virtual machines.