Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 163 discussion

AWS Fargate

A is minimal overhead. B has EC2 overhead C EC2 instance overhead + container repository running on EC2 overhead D AMII, CloudWatch alarm is overhead++

fargate is the compute managed for you.. A

ECR+ECS+Fargate = Less overhead

ECR+ECS+Fargate = Less overhead

Fargate

Highly available architecture that minimizes operational overhead = Severless = Elastic Container Registry, Amazon Elastic Container Service with AWS Fargate launch type

Using ECR provides a fully managed container image registry. ECS with Fargate launch type allows running containers without managing servers or clusters. Fargate will handle scaling and optimization. Target tracking autoscaling will allow automatically adjusting capacity based on demand. The serverless approach with Fargate minimizes operational overhead.

AWF Fargate should be the best chonice

A is the right answers undoubtedly.

ECR provides a secure and scalable repository to store and manage container images. ECS with the Fargate launch type allows you to run containers without managing the underlying infrastructure, providing a serverless experience. Target tracking in ECS can automatically scale the number of tasks or services based on a target value such as CPU or memory utilization, ensuring that the application can handle increasing demand without manual intervention. Option B is not the best choice because using the EC2 launch type requires managing and scaling EC2 instances, which increases operational overhead. Option C is not the optimal solution as it involves managing the container repository on an EC2 instance and manually launching EC2 instances, which adds complexity and operational overhead. Option D also requires managing EC2 instances, configuring ASGs, and setting up manual scaling rules based on CloudWatch alarms, which is not as efficient or scalable as using Fargate in combination with ECS.

ECS + Fargate satisfy requirements, hence option A is the best solution.

minimize operational overhead = Serverless Fargate is Serverless

Correct is "A"

You can place Fargate launch type all in one AZ, or across multiple AZs.But Option A does not take care of High Availability requirement of question. With Option C we have multi AZ.

A Why ? Because fargate provisioned on demand resource

Option A AWS Fargate is a technology that you can use with Amazon ECS to run containers without having to manage servers or clusters of Amazon EC2 instances. With Fargate, you no longer have to provision, configure, or scale clusters of virtual machines to run containers. This removes the need to choose server types, decide when to scale your clusters, or optimize cluster packing.