Answer-first summary for fast verification
Answer: Configure node auto-upgrades for node pools in the maintenance windows.
Option A is the correct answer because it leverages GKE's built-in node auto-upgrade feature, which is a cloud-native, reliable, and scalable solution for automated node patching. It eliminates manual intervention, ensures timely application of critical patches, and allows configuration of maintenance windows to minimize disruption. Option B is inefficient and error-prone, as it requires custom scripting and maintenance, contradicting cloud-first principles. Option C is unnecessary and counterproductive, as migrating to self-managed Kubernetes increases operational overhead and reduces the benefits of GKE's managed services. Option D is unreliable and risky, as daily reboots do not guarantee patch application and can cause unnecessary downtime without addressing the root cause of missed patches.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your organization runs numerous containerized applications on Google Kubernetes Engine (GKE), and node updates are currently performed manually. An audit has revealed that a critical patch was missed because of a failed notification. You need to design a more reliable, cloud-native, and scalable process for applying node updates. What is the recommended approach?
A
Configure node auto-upgrades for node pools in the maintenance windows.
B
Develop a custom script to continuously check for patch availability, download patches, and apply the patches across all components of the cluster.
C
Migrate the cluster infrastructure to a self-managed Kubernetes environment for greater control over the patching process.
D
Schedule a daily reboot for all nodes to automatically upgrade.
No comments yet.