Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is migrating multiple backend workloads to Google Cloud and must map each workload to the optimal compute service based on operational overhead, scaling characteristics, and architectural dependencies:
Which compute mapping should you recommend?
This option deploys the containerized web API onto Compute Engine Managed Instance Groups (MIGs), processes file uploads via Cloud Run functions, and hosts the multi-tenant application on Cloud Run.
Workload 1 required direct physical hardware or sole-tenant VM isolation with custom kernel configurations, and Workload 3 had no dependencies on Kubernetes orchestration tooling or RBAC.
This architecture correctly maps each application archetype to its optimal Google Cloud runtime: Cloud Run for managed containerized request serving, Cloud Run functions for lightweight event-driven executions, and Google Kubernetes Engine (GKE) for complex container orchestration.
Choosing Cloud Run and Cloud Run functions eliminates cluster maintenance and operational overhead for standard HTTP endpoints and event handlers, while reserving GKE for workloads that have explicit dependencies on Kubernetes ecosystem APIs and RBAC multi-tenancy.

This option places the high-traffic containerized web API on Cloud Run functions, handles Cloud Storage upload events using Google Kubernetes Engine (GKE), and hosts the complex Kubernetes application on Cloud Run.
Workload 1 was a simple isolated function snippet, Workload 2 required continuous local high-performance storage and specialized daemon pods, and Workload 3 was a basic request-driven microservice without Kubernetes API dependencies.
This option deploys the stateless HTTP API on a Google Kubernetes Engine (GKE) cluster, executes event-driven file tasks on Cloud Run, and runs the complex Kubernetes-dependent service on Compute Engine Managed Instance Groups (MIGs).
Workload 1 required custom kernel extensions or specific network protocols unsupported by serverless platforms, and Workload 3 consisted of legacy monolithic applications distributed across traditional virtual machines.
Attempting to deploy Kubernetes-dependent workloads that rely on CRDs onto Compute Engine MIGs requires building and managing an entire self-hosted Kubernetes cluster from scratch on VMs, adding extreme operational burden.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated