Which solution will meet these requirements?

By:
On:
In: SAA-C03
Tagged:
With: 0 Comments
A company is building a containerized application on premises and decides to move the application to AWS.The application will have thousands of users soon after it is deployed.The company is unsure how to manage the deployment of containers at scale.The company needs to deploy the containerized application in a highly available architecture that minimizes operational overhead.

Which solution will meet these requirements?

Store container images in an Amazon Elastic Container Registry (Amazon ECR) repository. Use an Amazon Elastic Container Service (Amazon ECS) cluster with the AWS Fargate launch type to run the containers. Use target tracking to scale automatically based on demand.

Store container images in an Amazon Elastic Container Registry (Amazon ECR) repository. Use an Amazon Elastic Container Service (Amazon ECS) cluster with the Amazon EC2 launch type to run the containers. Use target tracking to scale automatically based on demand.

Store container images in a repository that runs on an Amazon EC2 instance. Run the containers on EC2 instances that are spread across multiple Availability Zones. Monitor the average CPU utilization in Amazon CloudWatch. Launch new EC2 instances as needed.

Create an Amazon EC2 Amazon Machine Image (AMI) that contains the container image. Launch EC2 instances in an Auto Scaling group across multiple Availability Zones. Use an Amazon CloudWatch alarm to scale out EC2 instances when the average CPU utilization threshold is breached.

Explanations:

This option uses Amazon ECR for storing container images and AWS Fargate for running containers, which abstracts the server management, minimizing operational overhead. Fargate also supports automatic scaling, making it ideal for handling thousands of users with high availability.

While this option uses Amazon ECR and ECS, it employs the Amazon EC2 launch type, which requires managing EC2 instances. This increases operational overhead, which does not align with the requirement to minimize it.

This option involves running a self-managed container image repository and requires managing EC2 instances, leading to higher operational overhead. Additionally, it lacks the automatic scaling provided by ECS and Fargate.

This option suggests creating an AMI with the container image and using EC2 instances in an Auto Scaling group. It also involves managing EC2 instances and lacks the container orchestration benefits of ECS and Fargate, leading to higher o

Leave a Reply

Your email address will not be published. Required fields are marked *

one × 4 =