DOP-C02 · Question #512
A company uses Amazon Elastic Kubernetes Services (Amazon EKS) to host containerized applications that are available in Amazon Elastic Container Registry (Amazon ECR). The company currently launches…
The correct answer is A. Run the aws eks update-cluster-version command. Providing appropriate arguments such as. Using the AWS CLI aws eks update-cluster-version command is the most direct, lowest-effort way to upgrade the EKS control plane for existing clusters when you already provision clusters and add-ons with the AWS CLI. This approach keeps the upgrade workflow consistent with the…
Question
A company uses Amazon Elastic Kubernetes Services (Amazon EKS) to host containerized applications that are available in Amazon Elastic Container Registry (Amazon ECR). The company currently launches EKS clusters in the company's development environment by using the AWS CLI aws eks create-cluster command. The company uses the aws eks create- addon command to install required add-ons. All installed add-ons are currently version compatible with the version of Kubernetes that the company uses. All clusters exclusively use managed node groups for compute capacity. Some of the EKS clusters require a version upgrade. A DevOps engineer must ensure that upgrades continuously occur within the AWS standard support schedule. Which solution will meet this requirement with the LEAST operational overhead?
Options
- ARun the aws eks update-cluster-version command. Providing appropriate arguments such as
- BEnable EKS Auto Mode on all EKS clusters. Remove all existing managed node groups.
- CRun the eksctl command to upgrade the EKS clusters. Provide appropriate arguments such as
- DRefactor the environment to create EKS clusters by using infrastructure as code (IaC). Upgrade
How the community answered
(33 responses)- A91% (30)
- B6% (2)
- C3% (1)
Explanation
Using the AWS CLI aws eks update-cluster-version command is the most direct, lowest-effort way to upgrade the EKS control plane for existing clusters when you already provision clusters and add-ons with the AWS CLI. This approach keeps the upgrade workflow consistent with the current operational model and allows the engineer to regularly move clusters to supported Kubernetes versions within the standard support timeline with minimal additional tooling or
Topics
Community Discussion
No community discussion yet for this question.