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 organization is designing a cloud compute architecture for a new customer webhook processing service on Google Cloud. The architecture must satisfy several key workload requirements:
Which compute service should you select to meet these requirements?
Compute Engine is Google Cloud's Infrastructure as a Service (IaaS) offering that allows users to deploy and manage virtual machines. Regional Managed Instance Groups (MIGs) manage collections of identical VMs across multiple zones within a single region, providing features like autoscaling, autohealing, and regional redundancy.
The workload required deep operating system configuration, custom kernel extensions, legacy non-containerized enterprise software, or sustained predictable usage where full VM-level isolation and licensing controls were necessary.
App Engine standard generation 1 is a legacy Platform as a Service (PaaS) environment designed for hosting web applications using restrictive, sandboxed runtime environments (historically limited to Java 8 and Python 2.7) with built-in API frameworks.
You were maintaining an existing legacy application codebase specifically built around App Engine generation 1 APIs and Java 8/Python 2.7 frameworks.
Cloud Run is a fully managed serverless container platform in Google Cloud that enables developers to run stateless, containerized applications directly on top of Google's scalable infrastructure without managing virtual machines or cluster control planes.
Compared to IaaS virtual machines or Kubernetes cluster orchestration, Cloud Run provides the ideal balance of container flexibility and serverless operational simplicity, directly matching the intermittent, event-driven scaling profile while minimizing administrative effort.
Google Kubernetes Engine (GKE) Standard is a managed container orchestration platform that provides automated deployment, scaling, and operational management of containerized workloads using open-source Kubernetes.
The architecture required complex multi-tier container orchestration, custom Kubernetes APIs/CRDs, advanced networking topologies across many microservices, or specific third-party Kubernetes ecosystem tooling like Helm charts with fine-grained RBAC.
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