Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
A DevOps team manages a fleet of GKE Standard clusters hosting mission-critical stateful workloads with long-lived active client connections. Following a blameless post-mortem regarding an outage during automated node patching and upgrades, the team discovered that GKE terminated pods when PodDisruptionBudget (PDB) constraints exceeded the default 1-hour timeout, and the team had no automated mechanism to validate workload stability before old nodes were deleted.
Which node pool upgrade configuration should the team implement to prevent forced pod terminations and enable rollback capabilities if anomalies occur?
Disable node auto-upgrades and implement a scheduled CronJob to manually execute gcloud container clusters resize and drain nodes during maintenance exclusions.
Configure the blue-green upgrade strategy for the node pool with customized soak time and validation thresholds.
Set the cluster autoscaler location policy to ANY and annotate all stateful pods with cluster-autoscaler.kubernetes.io/safe-to-evict: false.
Configure the surge upgrade strategy with maxSurge=1 and maxUnavailable=0, and configure a PodDisruptionBudget with minAvailable=100%.
Disable node auto-upgrades and implement a scheduled CronJob to manually execute gcloud container clusters resize and drain nodes during maintenance exclusions.
Configure the blue-green upgrade strategy for the node pool with customized soak time and validation thresholds.
A blue-green upgrade strategy in Google Kubernetes Engine (GKE) provisions an entirely new set of nodes (green pool) running the target Kubernetes version alongside the existing pool (blue pool). It controls workload migration incrementally and allows administrators to define validation criteria before decommissioning the old nodes.
Unlike surge upgrades—which mutate the existing pool and enforce rigid 1-hour PDB timeouts—blue-green upgrades decouple node provisioning from workload draining and give engineers full control over validation and rollbacks.
Set the cluster autoscaler location policy to ANY and annotate all stateful pods with cluster-autoscaler.kubernetes.io/safe-to-evict: false.
Configure the surge upgrade strategy with maxSurge=1 and maxUnavailable=0, and configure a PodDisruptionBudget with minAvailable=100%.