Which reason can explain why the application is not connecting to the new resources?
The developer did not successfully create the new AWS account.
The developer added a new tag to the Docker image.
The developer did not update the Docker image tag to a new version.
The developer pushed the changes to a new Docker image tag.
Explanations:
The scenario indicates that the developer successfully tested the changes and deployed the pipeline, suggesting that the new AWS account was created correctly and the configuration changes were made.
Adding a new tag to the Docker image does not affect the application’s configuration to connect to the backend resources. The application would still reference the old resources unless explicitly updated in the configuration.
If the developer did not update the Docker image tag to a new version that contains the updated configuration, the application would continue to use the old image with the original configuration, leading it to connect to the old backend.
Pushing changes to a new Docker image tag does not guarantee that the application will use the new resources unless the deployment or the configuration was also updated to reference the new image tag. If the image tag is not updated in the deployment configuration, the application would still reference the old backend.
I measure that the answer is:
The developer did not update the Docker image tag to a new version.
If memory serves me right, the answer is:
The developer did not update the Docker image tag to a new version.