What should a solutions architect recommend?
Create an Amazon Elastic Container Service (Amazon ECS) cluster using the Fargate launch type. Create a task definition for the web application. Create an ECS service with a desired count of three tasks.
Create an Amazon Elastic Container Service (Amazon ECS) cluster using the Amazon EC2 launch type with three container instances in one Availability Zone. Create a task definition for the web application. Place one task for each container instance.
Create an Amazon Elastic Container Service (Amazon ECS) cluster using the Fargate launch type with one container instance in three different Availability Zones. Create a task definition for the web application. Create an ECS service with a desired count of three tasks.
Create an Amazon Elastic Container Service (Amazon ECS) cluster using the Amazon EC2 launch type with one container instance in two different Availability Zones. Create a task definition for the web application. Place two tasks on one container instance and one task on the remaining container instance.
Explanations:
Amazon ECS with Fargate is cost-effective, as it eliminates the need to manage EC2 instances, and it can scale automatically. Running three tasks across multiple Availability Zones ensures high availability and meets the demand increase.
Placing three container instances in one Availability Zone does not meet high availability requirements, as it could lead to a single point of failure.
Fargate does not use container instances; specifying “one container instance in three different Availability Zones” is invalid.
Using EC2 with two container instances across two Availability Zones is less cost-effective and does not provide high availability across three tasks.
It seems to me that the answer is:
Create an Amazon Elastic Container Service (Amazon ECS) cluster using the Fargate launch type. Create a task definition for the web application. Create an ECS service with a desired count of three tasks.