ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 141 - DVA-C02 discussion

Report
Export

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?

A.
The developer did not successfully create the new AWS account.
Answers
A.
The developer did not successfully create the new AWS account.
B.
The developer added a new tag to the Docker image.
Answers
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.
Answers
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.
Answers
D.
The developer pushed the changes to a new Docker image tag.
Suggested answer: C

Explanation:

The correct answer is C) The developer did not update the Docker image tag to a new version.

C) The developer did not update the Docker image tag to a new version. This is correct. When deploying an application to Amazon EKS, the developer needs to specify the Docker image tag that contains the application code and configuration. If the developer does not update the Docker image tag to a new version after making changes to the application, the EKS cluster will continue to use the old Docker image tag that references the original backend resources. To fix this issue, the developer should update the Docker image tag to a new version and redeploy the application to the EKS cluster.

A) The developer did not successfully create the new AWS account. This is incorrect. The creation of a new AWS account is not related to the application's connection to the backend resources. The developer can use any AWS account to host the EKS cluster and the backend resources, as long as they have the proper permissions and configurations.

B) The developer added a new tag to the Docker image. This is incorrect. Adding a new tag to the Docker image is not enough to deploy the changes to the application. The developer also needs to update the Docker image tag in the EKS cluster configuration, so that the EKS cluster can pull and run the new Docker image.

D) The developer pushed the changes to a new Docker image tag. This is incorrect. Pushing the changes to a new Docker image tag is not enough to deploy the changes to the application. The developer also needs to update the Docker image tag in the EKS cluster configuration, so that the EKS cluster can pull and run the new Docker image.

1: Amazon EKS User Guide, ''Deploying applications to your Amazon EKS cluster'', https://docs.aws.amazon.com/eks/latest/userguide/deploying-applications.html

2: Amazon ECR User Guide, ''Pushing an image'', https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-push-ecr-image.html

3: Amazon EKS User Guide, ''Updating an Amazon EKS cluster'', https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html

asked 16/09/2024
RYAN UBANA
39 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first