Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your organization operates multiple Google Kubernetes Engine (GKE) clusters across staging and production environments. All production clusters are enrolled in the Regular release channel to ensure baseline operational stability. Due to strict corporate security policies, your team must ensure that newly published security patches are automatically applied to the control plane and nodes as quickly as possible without waiting for GKE's multi-week qualification period, while still strictly honoring configured maintenance windows and exclusions.
Which configuration should you apply to meet these requirements?
no_upgrades during business hours and execute manual surge upgrades overnight.A maintenance exclusion blocks automatic control plane and node pool upgrades during defined periods, such as peak business cycles. Surge upgrades allow node pools to upgrade incrementally by creating extra surge VMs.
no_upgrades exclusion prevents automatic upgrades rather than accelerating the consumption of new security patches.no_upgrades completely halts all automated maintenance and patching during the specified window.An organization needed to completely freeze all infrastructure changes during a major retail event or critical freeze period.
Accelerated patch auto-upgrades is a GKE feature designed for clusters enrolled in a release channel (such as Rapid, Regular, or Stable). When a new patch release is introduced to a release channel, GKE initially makes it available for new cluster creation and manual upgrades before qualifying it over a multi-day or multi-week window to become an automatic upgrade target.
This approach provides an automated, policy-compliant pipeline for rapid vulnerability remediation without requiring manual CLI interventions or moving production clusters to the higher-churn Rapid channel.
The Rapid release channel provides early access to new Kubernetes minor versions and patches before they qualify for the Regular and Stable channels.
The goal were to test pre-release Kubernetes minor versions and validate workload compatibility in a non-production or exploratory environment.
Disabling release channels places the GKE cluster on a static version, requiring administrators to manually discover, track, and execute version upgrades for both the control plane and node pools.
gcloud container clusters upgrade adds significant operational overhead, custom code maintenance, and failure modes.An enterprise required total manual control over exact version binaries and prohibited Google-managed automated control plane upgrades.
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