An enterprise is planning to migrate a fleet of standard web services and background processing microservices to Google Kubernetes Engine (GKE). The platform architecture must satisfy the following technical and operational criteria: Provide high availability for the Kubernetes API control plane during maintenance and single-zone infrastructure disruptions Eliminate the operational overhead of configuring node pools, OS patching, scaling parameters, and bin-packing Optimize cloud spend by billing compute based on container resource requests rather than paying for unused worker node VM capacity Which GKE cluster configuration should you recommend?

Deploy a regional GKE Autopilot cluster: What GKE Autopilot Regional Mode is GKE Autopilot is a fully managed mode of operation in Google Kubernetes Engine where Google provisions, configures, and manages the entire underlying cluster infrastructure, including node scaling, OS maintenance, security hardening, and Pod bin-packing. All Autopilot clusters are inherently regional clusters, distributing control plane replicas and worker nodes across multiple compute zones within a region. How it meets the requirements High Availability & Zero Control Plane Maintenance Downtime: Because Autopilot clusters are regional, multiple control plane replicas run in different zones. During control plane updates or single-zone outages, remaining replicas ensure continuous availability of the Kubernetes API. Minimal Operational Overhead: GKE manages node provisioning, security patching, auto-upgrades, and Pod scheduling automatically, removing the administrative burden of node pool sizing and maintenance. Optimized Billing Model: Autopilot charges strictly for the CPU, memory, and ephemeral storage resources requested by running Pods, preventing charges for unused or idle node VM capacity. Key advantages Pre-configured Hardening: Enforces Kubernetes Pod Security Standards and Google security best practices out of the box. Automated Node Lifecycle: Fully eliminates manual node pool creation, node resizing, and OS image updates. Pod-level SLA: Offers financial Service Level Agreements at both the control plane and Pod level. Automatic Dynamic Provisioning: Automatically provisions and scales machine resources based directly on workload specifications. Why this is optimal A regional Autopilot cluster completely aligns with the organization's goals by offering multi-zone resilience and a consumption-based pricing model while shifting Day-2 infrastructure operations entirely to Google Cloud.

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Intermediate

Prepare and test your skills

Gke Autopilot Regional Ha Operational Overhead

Section: Container orchestration

...

Explanations

...

View source documentation

Keep the momentum going with these hand-picked practice scenarios

IntermediateProfessional Cloud Architect

An e-commerce company runs an order processing application on Google Kubernetes Engine (GKE). The application experiences sudden, sharp traffic surges during flash sales and low activity overnight. The engineering team has identified the following requirements: The application must automatically scale the number of Pod replicas out and in based on incoming traffic volume to preserve responsiveness. Container CPU and memory resource requests must be continually right-sized over time to prevent over-allocation and optimize costs. The underlying VM node capacity must scale dynamically without manual intervention whenever new Pods cannot be scheduled due to insufficient compute resources. Autoscaling components must not compete or create scaling race conditions with one another. Which autoscaling architecture should you implement to satisfy these requirements?

Container orchestration

IntermediateProfessional Cloud Architect

An enterprise runs a multi-tier analytics application on Google Kubernetes Engine (GKE). A backend workload running in the data-processing namespace requires access to Cloud Storage and Cloud Bigtable. The security team mandates the following requirements: The backend application must authenticate to Google Cloud APIs following the principle of least privilege, without managing or storing long-lived service account keys in the cluster. Pods running on the same node pool from other namespaces must not inherit the backend workload's Google Cloud API permissions. Network traffic must be restricted at Layer 4 so that backend Pods only allow authorized cluster communication and can reach the required Google Cloud endpoints. Which architectural approach should you implement to satisfy these requirements?

Container orchestration

IntermediateProfessional Cloud Architect

Want more questions like this?

Get a free certification question every week.

Last updated August 28, 2026

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Intermediate

Prepare and test your skills

Gke Autopilot Regional Ha Operational Overhead

Section: Container orchestration

An enterprise is planning to migrate a fleet of standard web services and background processing microservices to Google Kubernetes Engine (GKE).

The platform architecture must satisfy the following technical and operational criteria:

Provide high availability for the Kubernetes API control plane during maintenance and single-zone infrastructure disruptions
Eliminate the operational overhead of configuring node pools, OS patching, scaling parameters, and bin-packing
Optimize cloud spend by billing compute based on container resource requests rather than paying for unused worker node VM capacity

Which GKE cluster configuration should you recommend?

...

Deploy a regional GKE Standard cluster with manual node pool management

...

Deploy a zonal GKE Autopilot cluster with automatic node upgrades

...

Deploy a zonal GKE Standard cluster with Cluster Autoscaler enabled

...

Deploy a regional GKE Autopilot cluster

...

Explanations

What GKE Autopilot Regional Mode is

GKE Autopilot is a fully managed mode of operation in Google Kubernetes Engine where Google provisions, configures, and manages the entire underlying cluster infrastructure, including node scaling, OS maintenance, security hardening, and Pod bin-packing. All Autopilot clusters are inherently regional clusters, distributing control plane replicas and worker nodes across multiple compute zones within a region.

How it meets the requirements

High Availability & Zero Control Plane Maintenance Downtime: Because Autopilot clusters are regional, multiple control plane replicas run in different zones. During control plane updates or single-zone outages, remaining replicas ensure continuous availability of the Kubernetes API.
Minimal Operational Overhead: GKE manages node provisioning, security patching, auto-upgrades, and Pod scheduling automatically, removing the administrative burden of node pool sizing and maintenance.
Optimized Billing Model: Autopilot charges strictly for the CPU, memory, and ephemeral storage resources requested by running Pods, preventing charges for unused or idle node VM capacity.

Key advantages

Pre-configured Hardening: Enforces Kubernetes Pod Security Standards and Google security best practices out of the box.
Automated Node Lifecycle: Fully eliminates manual node pool creation, node resizing, and OS image updates.
Pod-level SLA: Offers financial Service Level Agreements at both the control plane and Pod level.
Automatic Dynamic Provisioning: Automatically provisions and scales machine resources based directly on workload specifications.

Why this is optimal

A regional Autopilot cluster completely aligns with the organization's goals by offering multi-zone resilience and a consumption-based pricing model while shifting Day-2 infrastructure operations entirely to Google Cloud.

...

View source documentation

Keep the momentum going with these hand-picked practice scenarios

IntermediateProfessional Cloud Architect

An e-commerce company runs an order processing application on Google Kubernetes Engine (GKE). The application experiences sudden, sharp traffic surges during flash sales and low activity overnight. The engineering team has identified the following requirements: The application must automatically scale the number of Pod replicas out and in based on incoming traffic volume to preserve responsiveness. Container CPU and memory resource requests must be continually right-sized over time to prevent over-allocation and optimize costs. The underlying VM node capacity must scale dynamically without manual intervention whenever new Pods cannot be scheduled due to insufficient compute resources. Autoscaling components must not compete or create scaling race conditions with one another. Which autoscaling architecture should you implement to satisfy these requirements?

Container orchestration

IntermediateProfessional Cloud Architect

An enterprise runs a multi-tier analytics application on Google Kubernetes Engine (GKE). A backend workload running in the data-processing namespace requires access to Cloud Storage and Cloud Bigtable. The security team mandates the following requirements: The backend application must authenticate to Google Cloud APIs following the principle of least privilege, without managing or storing long-lived service account keys in the cluster. Pods running on the same node pool from other namespaces must not inherit the backend workload's Google Cloud API permissions. Network traffic must be restricted at Layer 4 so that backend Pods only allow authorized cluster communication and can reach the required Google Cloud endpoints. Which architectural approach should you implement to satisfy these requirements?

Container orchestration

IntermediateProfessional Cloud Architect

Cloud Monitoring Metric Threshold Alerting Condition

Alerting strategies

IntermediateProfessional Cloud Architect

Apigee Cloud Armor reCAPTCHA WAAP Architecture

API management best practices (e.g., Apigee)

IntermediateProfessional Cloud Architect

DMS Foreign Key and Trigger Disabling

Assessing and migrating systems and data to support the solution (e.g., Google Cloud Migration Center)

FundamentalAssociate Data Practitioner

Pub/Sub to BigQuery Streaming Ingestion

Identify use cases for event-driven data ingestion from Pub/Sub to BigQuery

Want more questions like this?

Get a free certification question every week.

Last updated August 28, 2026

An enterprise is planning to migrate a fleet of standard web services and background processing microservices to Google Kubernetes Engine (GKE).

The platform architecture must satisfy the following technical and operational criteria:

Provide high availability for the Kubernetes API control plane during maintenance and single-zone infrastructure disruptions
Eliminate the operational overhead of configuring node pools, OS patching, scaling parameters, and bin-packing
Optimize cloud spend by billing compute based on container resource requests rather than paying for unused worker node VM capacity

Which GKE cluster configuration should you recommend?

Deploy a regional GKE Standard cluster with manual node pool management

Deploy a zonal GKE Autopilot cluster with automatic node upgrades

Deploy a zonal GKE Standard cluster with Cluster Autoscaler enabled

Deploy a regional GKE Autopilot cluster

Deploy a regional GKE Standard cluster with manual node pool management

Deploy a zonal GKE Autopilot cluster with automatic node upgrades

Deploy a zonal GKE Standard cluster with Cluster Autoscaler enabled

Deploy a regional GKE Autopilot cluster

What GKE Autopilot Regional Mode is

GKE Autopilot is a fully managed mode of operation in Google Kubernetes Engine where Google provisions, configures, and manages the entire underlying cluster infrastructure, including node scaling, OS maintenance, security hardening, and Pod bin-packing. All Autopilot clusters are inherently regional clusters, distributing control plane replicas and worker nodes across multiple compute zones within a region.

How it meets the requirements

High Availability & Zero Control Plane Maintenance Downtime: Because Autopilot clusters are regional, multiple control plane replicas run in different zones. During control plane updates or single-zone outages, remaining replicas ensure continuous availability of the Kubernetes API.
Minimal Operational Overhead: GKE manages node provisioning, security patching, auto-upgrades, and Pod scheduling automatically, removing the administrative burden of node pool sizing and maintenance.
Optimized Billing Model: Autopilot charges strictly for the CPU, memory, and ephemeral storage resources requested by running Pods, preventing charges for unused or idle node VM capacity.

Key advantages

Pre-configured Hardening: Enforces Kubernetes Pod Security Standards and Google security best practices out of the box.
Automated Node Lifecycle: Fully eliminates manual node pool creation, node resizing, and OS image updates.
Pod-level SLA: Offers financial Service Level Agreements at both the control plane and Pod level.
Automatic Dynamic Provisioning: Automatically provisions and scales machine resources based directly on workload specifications.

Why this is optimal

A regional Autopilot cluster completely aligns with the organization's goals by offering multi-zone resilience and a consumption-based pricing model while shifting Day-2 infrastructure operations entirely to Google Cloud.

Professional Cloud Architect

Gke Autopilot Regional Ha Operational Overhead

Related questions

Cloud Monitoring Metric Threshold Alerting Condition

Apigee Cloud Armor reCAPTCHA WAAP Architecture

DMS Foreign Key and Trigger Disabling

Pub/Sub to BigQuery Streaming Ingestion

Professional Cloud Architect

Gke Autopilot Regional Ha Operational Overhead

What GKE Autopilot Regional Mode is

How it meets the requirements

Key advantages

Why this is optimal

Related questions

Cloud Monitoring Metric Threshold Alerting Condition

Apigee Cloud Armor reCAPTCHA WAAP Architecture

DMS Foreign Key and Trigger Disabling

Pub/Sub to BigQuery Streaming Ingestion

What GKE Autopilot Regional Mode is

How it meets the requirements

Key advantages

Why this is optimal