Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 346 discussion

I read all articles and my conclusion is "A". Here are two links that prove it 1. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-placement.html By default, Fargate tasks are spread across Availability Zones. With all other tasks, default task placement strategies depend on whether you are running tasks manually or within a service. 2. https://aws.amazon.com/blogs/containers/amazon-ecs-availability-best-practices/ Fargate ensures Availability Zone spread while removing the complexity of managing EC2 infrastructure and works to ensure that Tasks in a Replica Service are balanced across Availability Zones. For RunTask launches with a Fargate launch type Fargate will look to spread Task placement across all available Availability Zones ensuring even distribution of the Task Definition Family that the Task belongs to.

C. 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.

A is the answer

fargate is Costlier. Good for variable, short running tasks, ECS is a better choice.

C is an answer

IMO: A is more accessible & has same cost level: https://aws.amazon.com/blogs/containers/theoretical-cost-optimization-by-amazon-ecs-launch-type-fargate-vs-ec2/

A seems correct.

A is right. Instances here means web instances, not EC2 instances. C is not right because by using Fargate you cannot specify the VM level configuration.

A. "AWS Fargate is a compute engine for ECS that removes the need to configure, manage, and scale EC2 instances. Fargate ensures Availability Zone spread while removing the complexity of managing EC2 infrastructure and works to ensure that Tasks in a Replica Service are balanced across Availability Zones" https://aws.amazon.com/blogs/containers/amazon-ecs-availability-best-practices/ Also remember, an instance can be a pod or task or en reference

Fargate being an serverless component always ensures the task is running and it is AWS responsibility to handle it

C is ans

The replica scheduling strategy places and maintains the desired number of tasks across your cluster. You can use task placement strategies and constraints to customize task placement decisions. https://docs.aws.amazon.com/AmazonECS/latest/userguide/scheduling_tasks.html

B,C,D look incorrect; A 'ECS cluster' is a group of 'containers instances'(NOT 'containers'). 'Container instance' is essentially an EC2.How can it be in multiple AZ at same time? Moreover,C talks about using Fargate(serverless) with container instances which is incorrect. Scalability is not addressed in any. 'Container instance' contains many 'tasks' "service" defines min and max no of 'tasks'(having same task definition). Each 'task' contains multiple 'containers'. A is the answer.

One thing is for sure that the Management is highly demanding

the key point here "Management is extremely sensitive to cost" Answer "A" is the cheapest option. Hence A is the correct answer.

How could D satisify " The application must be able to scale to meet increases in demand." ?

I will choose A.