AWS Certified Developer – Associate (DVA-C02) — Question 277

A developer is migrating an application to Amazon Elastic Kubernetes Service (Amazon EKS). The developer migrates the application to Amazon Elastic Container Registry (Amazon ECR) with an EKS cluster. As part of the application migration to a new backend, the developer creates a new AWS account. The developer makes configuration changes to the application to point the application to the new AWS account and to use new backend resources. The developer successfully tests the changes within the application by deploying the pipeline.

The Docker image build and the pipeline deployment are successful, but the application is still connecting to the old backend. The developer finds that the application's configuration is still referencing the original EKS cluster and not referencing the new backend resources.

Which reason can explain why the application is not connecting to the new resources?

Answer options

• A. The developer did not successfully create the new AWS account.
• B. The developer added a new tag to the Docker image.
• C. The developer did not update the Docker image tag to a new version.
• D. The developer pushed the changes to a new Docker image tag.

Correct answer: C

Explanation

If the deployment manifest or Kubernetes configuration is not updated to point to the new Docker image tag, EKS will continue to run the cached or older version of the container image containing the old backend configuration. Even though the pipeline successfully built a new image, the deployment resource still references the old tag, preventing the new changes from being rolled out. Updating the image tag in the deployment specification forces EKS to pull and run the newly built container with the updated configuration.