AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
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?
Other
Community
UAnonymous
A
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.
B
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.
C
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.
D
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.
Explanation:
Explanation
Correct Answer: A
Why Option A is correct:
-
Minimizes operational overhead - AWS Fargate is a serverless compute engine for containers that eliminates the need to provision and manage servers. This significantly reduces operational overhead compared to managing EC2 instances.
-
Highly available architecture - Amazon ECS with Fargate automatically distributes containers across multiple Availability Zones within a region, providing high availability.
-
Scalability - Target tracking scaling policies automatically adjust the number of running tasks based on demand, ensuring the application can handle thousands of users.
-
Container management - Amazon ECR provides a secure, scalable container registry that integrates seamlessly with ECS.
Why other options are incorrect:
Option B: While this uses ECS and ECR, it uses the EC2 launch type which requires managing EC2 instances (including patching, scaling, and maintenance), increasing operational overhead.
Option C: This approach requires manual management of container repositories on EC2 instances and manual scaling decisions based on CloudWatch monitoring, which increases operational complexity and doesn't provide automated scaling.
Option D: This approach treats containers as part of an AMI, which is not a container-native approach. It requires managing EC2 instances and doesn't leverage AWS container services designed for container orchestration.
Key AWS Services:
- Amazon ECS (Elastic Container Service): Container orchestration service
- AWS Fargate: Serverless compute engine for containers
- Amazon ECR (Elastic Container Registry): Managed container registry
- Target Tracking Scaling: Automated scaling based on metrics
This solution provides a fully managed, highly available, and scalable container deployment with minimal operational overhead.
Comments
Loading comments...