Answer-first summary for fast verification
Answer: You terminated the container instance while it was in STOPPED state, that lead to this synchronization issues
You terminated the container instance while it was in STOPPED state, that lead to this synchronization issues - If you terminate a container instance while it is in the STOPPED state, that container instance isn't automatically removed from the cluster. You will need to deregister your container instance in the STOPPED state by using the Amazon ECS console or AWS Command Line Interface. Once deregistered, the container instance will no longer appear as a resource in your Amazon ECS cluster. Incorrect options: You terminated the container instance while it was in RUNNING state, that lead to this synchronization issues - This is an incorrect statement. If you terminate a container instance in the RUNNING state, that container instance is automatically removed, or deregistered, from the cluster. The container instance has been terminated with AWS CLI, whereas, for ECS instances, Amazon ECS CLI should be used to avoid any synchronization issues - This is incorrect and has been added as a distractor. A custom software on the container instance could have failed and resulted in the container hanging in an unhealthy state till restarted again - This is an incorrect statement. It is already mentioned in the question that the developer has terminated the instance.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A junior developer has terminated a container instance in Amazon Elastic Container Service (Amazon ECS) following the team lead's instructions. Despite the termination, the container instance still appears listed as a resource in the ECS cluster.
As an AWS Certified Developer Associate, which of the following actions would you suggest to appropriately address and resolve this issue?
A
You terminated the container instance while it was in STOPPED state, that lead to this synchronization issues
B
The container instance has been terminated with AWS CLI, whereas, for ECS instances, Amazon ECS CLI should be used to avoid any synchronization issues
C
A custom software on the container instance could have failed and resulted in the container hanging in an unhealthy state till restarted again
D
You terminated the container instance while it was in RUNNING state, that lead to this synchronization issues
No comments yet.