A cloud administrator is planning a new Google Kubernetes Engine (GKE) cluster deployment for a suite of web microservices and wants to reduce node management overhead while optimizing resource utilization. The administrator considers provisioning the cluster in GKE Autopilot mode. Which TWO statements accurately describe the operational characteristics and billing model of GKE Autopilot? (Select TWO options.)
- Google manages node provisioning, scaling, auto-repair, and node security patching automatically.Answer
- Billing is based directly on the CPU, memory, and ephemeral storage resources requested by running Pods rather than provisioned Compute Engine VM capacity.Answer
- CCluster administrators must manually install and configure the Cluster Autoscaler tool to add worker nodes when workloads expand.
- DCustom Linux kernel parameters (sysctls) and custom node operating system packages can be freely modified by cluster operators on underlying nodes.
- ESpot workloads deployed on Autopilot are guaranteed against preemption for stateful databases.
Answer
Google fully manages node provisioning and security, and billing is calculated based on Pod resource requests rather than total node capacity.
GKE Autopilot abstracts away node management by delegating node provisioning, repair, and security patching to Google. Furthermore, its cost model bills based on the Pod's resource requests rather than paying for unutilized node headroom.
Step-by-Step Solution
Key Concept
GKE Autopilot Cluster Architecture and Resource Billing Model