Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is deploying general-purpose containerized microservices to Google Kubernetes Engine (GKE). The platform engineering team has limited operational capacity and wants to eliminate the administrative overhead of managing underlying node pools, planning virtual machine capacity, and manually configuring Pod bin-packing.
They require an operational model where GKE automatically provisions and manages compute infrastructure according to Pod resource requests while enforcing security best practices by default.
Which GKE mode of operation should the organization deploy?
App Engine flexible environment is a Platform-as-a-Service (PaaS) offering that runs containerized applications inside managed virtual machines on Compute Engine, automatically handling health checks, autoscaling, and load balancing.
kubectl, Helm, or Custom Resource Definitions), making it incompatible with GKE microservice architectures.App Engine flexible is best suited for development teams deploying monolithic web applications or simple microservices who want basic PaaS deployment without interacting with Kubernetes APIs or cluster architectures.
While App Engine flex abstracts VM maintenance, GKE Autopilot delivers the full power and standard APIs of Kubernetes while handling node infrastructure, bin-packing, and security automatically.
GKE Standard mode is a cluster management model where Google manages the Kubernetes control plane while the customer maintains direct administrative control and responsibility over worker nodes, node pools, and custom cluster configurations.
Standard mode is ideal when workloads require deep infrastructure customization, such as running privileged system containers, using unsupported third-party kernel extensions, or retaining strict control over exact VM placement.
While Standard mode offers complete flexibility, it introduces substantial operational burden. For a team seeking hands-off infrastructure management with automatic security baselines, Autopilot is the recommended Google Cloud approach.
Managed Instance Groups (MIGs) are collections of homogeneous Compute Engine virtual machines created from a common instance template. MIGs provide automated scaling, health checking, auto-healing, and multi-zone distribution for VM-based workloads.
Compute Engine MIGs are suitable for traditional monolithic applications, stateful legacy software that cannot be containerized, or custom distributed compute clusters that do not use Kubernetes as an orchestrator.
MIGs require significantly more infrastructure engineering than both GKE Standard and Autopilot modes, making them inappropriate for teams wanting managed, serverless Kubernetes operations.
GKE Autopilot is a fully managed mode of operation in Google Kubernetes Engine where Google manages the entire underlying cluster infrastructure, including node provisioning, scaling, maintenance, and security hardening. In Autopilot mode, users focus entirely on designing and deploying their containerized applications without needing to manage virtual machines or node pools directly.
Compared to Standard mode, Autopilot removes the complexity of managing node pools and configuring node autoscaling. It provides a true serverless Kubernetes operational experience, ensuring high availability and cost optimization without requiring dedicated infrastructure administrators.
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