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 organization is evaluating Google Cloud compute options for two distinct application workloads:
Which compute platform design meets these requirements while optimizing administrative overhead and infrastructure control?
Workload 1 was a simple event listener and Workload 2 was a lightweight background trigger requiring no custom OS or container orchestration.
When custom node OS images or specific host-level modifications are needed, GKE Standard or Compute Engine must be selected over Autopilot and serverless products.
GKE Standard provides a fully customizable Kubernetes environment where users manage node pools, machine types, scaling parameters, and cluster configuration.
While GKE Standard successfully meets the complex infrastructure control requirements of Workload 2, deploying Workload 1 on GKE Standard introduces unnecessary operational complexity and administrative overhead for a simple, event-driven HTTP service that explicitly requires zero server maintenance.
Workload 1 had strict requirements to share cluster networking, service meshes, or persistent storage with Workload 2 inside the same Kubernetes boundary.
A core architectural principle on Google Cloud is mapping workloads to the highest level of managed abstraction that still satisfies technical requirements to minimize operational overhead.
Cloud Run is a fully managed, serverless platform that runs stateless container images directly on Google Cloud's infrastructure without exposing virtual machines or cluster management interfaces.
Cloud Run abstracts away all node-level and cluster-level infrastructure. Consequently, it does not support:
Both workloads were standard stateless HTTP/gRPC services that did not require underlying OS customization or Kubernetes-native network segmentation.
Attempting to treat Cloud Run as a direct replacement for Kubernetes cluster management overlooks the fundamental trade-off: serverless simplicity sacrifices low-level kernel and cluster orchestration control.
This architecture pairs Cloud Run—a fully managed serverless container execution environment—with Google Kubernetes Engine (GKE) Standard, a managed Kubernetes platform providing deep infrastructure control.
Roles and RoleBindings) to enforce fine-grained permissions across namespaces.Using Cloud Run for simple HTTP services removes cluster maintenance overhead (such as control plane version management and node pool sizing), while deploying GKE Standard for the complex pipeline provides the required host-level flexibility and internal Kubernetes access control mechanisms that serverless abstractions do not support.
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 Validated