Q68Design High-Performing ArchitecturesMultiple answers
A company has built an application by using Docker containers and must run the application in the AWS Cloud by using a managed service to host it. The solution must: - scale in and out appropriately based on demand for the individual container services - avoid creating additional operational overhead or infrastructure to manage Which solutions meet these requirements? **(Choose two.)**
Select 2 answers.
← → navigate · a answer
Community votes
Discussion · 24
A, C 10
I don't want confuse other...
A, B 5
Selected Answer: AB
The question is asking for two options to run Docker containers in a serverless service with minimal effort.
Option C will take a lot of effort to configure the Lambda and the API Gateway to run the Container correctly.
Instead, just use EKS o ECS with Fargate to execute the container image
4
Dear MatAlves before you describe my answer as trolls try to study and focus
I will explain to you that C is not correct
Lambda is for running code in response to events and does not natively support running Docker containers in the traditional sense of a containerized application. Lambda can use container image as deployment packages but this setup isn't ideal for managing and calling complex containerized applications
So it's A + B
4
AWS Lambda can run Docker containers, but it is more suited for short-duration, event-driven functions rather than long-running services.
While you can use Lambda to run container images, it is typically used for microservices or functions rather than managing scalable containerized applications in the same way that ECS or EKS does.
A, B 3
API Gateway + Lamda are not designed for running Dockers containers directly
A, B 3
For sure
3
The question states itself. Which Solutions....?
3
Option AB
A, B 2
A or B is okay, why not C?
While AWS Lambda now supports running Linux-based container images, it is primarily designed for microservices or event-driven functions rather than managing scalable containerized applications like Amazon ECS or Amazon EKS
2
Are people picking A&B as alternate solutions? Is the question asking for alternates?? Am I missing something? Somebody explain please I'm super confused.
2
AB are using AWS Fargate which IS considered a managed service, option C does not run containers, , DE you have to manage your own EC2 instances thus not consider managed
2
I believe so. Based on other questions, they would have asked "which combination"
A, B 2
It should be AB, Container :ECS , EKS
2
It should be AB
A, C 2
- Container = ECS or EKS
- "managed service to host the application" = Fargate
- "not result in additional operational overhead or infrastructure to manage" = ECS for the win.
The main difference between ECS and EKS = simplicity vs flexibility.
https://aws.amazon.com/blogs/containers/amazon-ecs-vs-amazon-eks-making-sense-of-aws-container-services/
2
now, if instead of asking the "best" (combination) solution you want TWO SOLUTIONS, then I see value in A-B.
A, B 2
Everyone is picking AB too..
A, B 2
A or B is OK.
About C: Amazon API Gateway and AWS Lambda are not typically used for running Docker containers. Lambda is designed for serverless functions, and while you can use Lambda to invoke containerized tasks, it does not run containers directly.
A, B 2
glowies out reeeeeeeeeeeeeeee
2
Option AB
A, B 1
AWS Fargate:
Both ECS and EKS with Fargate provide a fully managed container orchestration service where you don't need to manage underlying infrastructure like EC2 instances, making it ideal for scaling and reducing operational overhead.
Scaling capabilities:
Both options allow for automatic scaling based on demand, meaning the container instances will automatically scale up or down based on application requirements.
1
Where do you read "best" solution?
1
No, I decided to change my option since this question is asking "Docker"&"AWS"
it is not asking local Kubernet, so AC should be the right answer.
1
Why so many trolls recently...