Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail company is migrating a containerized, tightly coupled microservices platform to Google Cloud. The team needs to minimize underlying node and infrastructure management while meeting the following technical requirements:
Which Google Cloud deployment approach should the team choose?
GKE Autopilot is a managed Kubernetes mode of operation in which Google handles underlying cluster infrastructure—including node provisioning, scaling, OS patching, and default security posture—while exposing the full Kubernetes API surface. Unlike serverless platforms that abstract away container orchestration, GKE Autopilot preserves standard Kubernetes primitives without requiring manual node pool administration.
While Cloud Run offers simpler scale-to-zero operations, it cannot run Helm charts, enforce Kubernetes Network Policies, or natively handle raw TCP/UDP microservices with persistent local block storage. GKE Autopilot delivers the required Kubernetes portability and granular control while minimizing infrastructure management.
Cloud Run is a fully managed serverless platform designed to run stateless containers directly on Google infrastructure without cluster management. It excels at event-driven and request-driven workloads, offering rapid autoscaling and scale-to-zero billing based on active request processing.
The workload consisted of stateless web APIs, microservices communicating over HTTP or gRPC, or event-driven handlers with variable traffic that benefit from scale-to-zero cost optimization and zero Kubernetes dependencies.
Compute Engine is Google Cloud's Infrastructure as a Service (IaaS) platform providing customizable virtual machines (VMs). A managed instance group (MIG) manages a pool of identical VMs created from an instance template, offering autoscaling, autohealing, and regional distribution.
The application required custom OS kernels, legacy monolithic VM software, Windows or Linux licensing customization, or direct VM-level administrative control rather than container orchestration.
A hybrid deployment uses Cloud Run for stateless, event-driven, or HTTP-based services while reserving GKE for stateful or complex microservices. When services are loosely coupled, this pattern combines serverless cost efficiency with Kubernetes control.
The architecture consisted of loosely coupled components—such as an internet-facing stateless frontend or periodic batch jobs on Cloud Run alongside an independent stateful backend on GKE.
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