Q12 — AWS SAP-C02 Ch.3

Question 12 of 75 | ← Chapter 3

Q237. A delivery company needs to migrate its third-party route planning application to AWS.The third party supplies a supported Docker image from a public registry. The image can run in as many containers as required to generate the route map. The company has divided the delivery area into sections with supply hubs so that delivery drivers travel the shortest distance possible from the hubs to the customers. To reduce the time necessary to generate route maps, each section uses its own set of Docker containers with a custom configuration that processes orders only in the section's area. The company needs the ability to allocate resources cost-effectively based on the number of running containers Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: D. Create an Amazon Elastic Container Service (Amazon ECS) cluster on AWS Fargate. Use the AWS CLI run-task command and set enableECSManagedTags to true to launch the planning application. Use the-tags option to assign a custom tag to the task

Explanation

To migrate a third-party route planning application to AWS for a delivery company and allocate resources cost-effectively based on the number of running containers, a solutions architect should recommend creating an Amazon Elastic Container Service (Amazon ECS) cluster with AWS Fargate launch type. Then, use the AWS CLI run-task command and set enableECSManagedTags to true to launch the planning application while assigning a custom tag to the task. This approach provides cost-effective resource allocation based on the number of running containers, requires minimal operational overhead, and is a fully- managed solution. Therefore, option D is the correct answer. Option A suggests creating an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on Amazon EC2 and launching the planning application in pods using the Amazon EKS CLI with custom tags. While this might work, it introduces additional complexity when compared to using Amazon ECS with AWS Fargate launch type, which is a fully-managed service that requires less operational overhead. Option B suggests creating an Amazon Elastic Kubernetes Service (Amazon EKS) cluster on AWS Fargate and launching the planning application using the Amazon EKS CLI with custom tags. While this might work, it introduces additional complexity when compared to using Amazon ECS with AWS Fargate launch type. Option C suggests creating an Amazon ECS cluster on Amazon EC2 and launching the planning application using the AWS CLI with run-tasks and custom tags. While this might work, it introduces additional complexity when compared to using Amazon ECS with AWS Fargate launch type. Therefore, the best solution is to create an Amazon ECS cluster with AWS Fargate launch type, use the AWS CLI run-task command with enableECSManagedTags to launch the planning application, and assign a custom tag to the task. This approach provides cost-effective resource allocation based on the number of running containers, requires minimal operational overhead, and is a fully-managed solution.