GCP Associate Cloud Engineer Practice Question 56: GKE Release Channels
Google Cloud Associate Cloud Engineer · Test 6 · question 6 of 10
A team runs a production GKE Standard cluster and wants GKE to manage its control plane and node version automatically. They are not chasing new Kubernetes features and want each version GKE applies to have already run in other customers' clusters the longest, so it carries the lowest risk of introducing an upgrade-related outage. They also plan to set a maintenance window so upgrades only happen overnight.
Which release channel should they enroll the cluster in?
Show answer and explanation
Answer:
GKE promotes a Kubernetes version through Rapid, then Regular, then Stable, so a version only reaches Stable after it has already run for a period in the other two channels. That makes Stable the channel with the most real-world validation and the lowest upgrade risk, which fits a team that wants proven versions over new features. A cluster enrolled in any release channel, including Stable, can still define a maintenance window and maintenance exclusions to control when GKE is allowed to apply those automatic upgrades.
Option A (Rapid) is the opposite choice: it delivers new minor versions as soon as they are available, before they have had time to prove themselves in production elsewhere. Option B (Regular) is validated more than Rapid but is promoted to clusters well before Stable, so it does not meet the "longest-running, lowest risk" requirement. Option D turns off automatic version management entirely, so GKE stops rolling out new versions on the team's behalf and an administrator must upgrade manually, which does not satisfy the requirement to have GKE manage the version automatically.
Reference: About release channels