Question #656
A logistics company needs to migrate a third-party data processing application to AWS. The third party provides a supported Docker image from a public registry, which can run in multiple containers. The company has divided its operations into regions, each with dedicated processing nodes that handle data specific to their region. To optimize processing times, each region uses its own Docker containers with custom configurations. The company requires the ability to allocate resources cost-effectively based on the number of active containers.
Which solution will meet these requirements with the LEAST operational overhead?
Create an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on Amazon EC2. Use the Amazon EKS CLI to deploy the application in pods, using the --tags parameter to assign region-specific tags to the pods.
Create an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on AWS Fargate. Deploy the application using the Amazon EKS CLI and apply region-specific tags via the AWS CLI tag-resource API.
Create an Amazon Elastic Container Service (Amazon ECS) cluster on Amazon EC2. Use the AWS CLI with run-task to launch containers, applying region-specific tags using the --tags parameter.
Create an Amazon Elastic Container Service (Amazon ECS) cluster on AWS Fargate. Use the AWS CLI run-task command with enableECSManagedTags set to true and apply region-specific tags using the --tags parameter.
Explanation
Answer D is correct because:
1. AWS Fargate removes the need to manage EC2 instances, reducing operational overhead.
2. Amazon ECS simplifies container orchestration compared to Kubernetes (EKS), aligning with the requirement for minimal management.
3. Using run-task with enableECSManagedTags and --tags ensures region-specific configurations are applied dynamically.
Other options are incorrect because:
- A & C involve EC2, requiring manual scaling and server management.
- B uses EKS, which introduces Kubernetes complexity unnecessary for this use case.
Key Points:
- Fargate > EC2 for operational simplicity.
- ECS > EKS when Kubernetes features are not required.
- Tags enable cost-effective resource allocation per region.
Answer
The correct answer is: D