Q54 — AWS SAA-C03 Ch.10

Question 54 of 100 | ← Chapter 10

Q654. A company built an application with Docker containers and needs to run the application in the AWS Cloud. The company wants to use a managed service to host the application. The solution must scale in and out appropriately according to demand on the individual container services The solution also must not result in additional operational overhead or infrastructure to manage. Which solutions will meet these requirements? (Select TWO)

Correct Answer: A. Use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate, B. Use Amazon Elastic Kubermetes Service Amazon EKS) with AWS Fargate

Explanation

To meet the requirements of hosting a Docker application in the AWS Cloud using a managed service that can scale appropriately without additional operational overhead or infrastructure to manage, the following solutions would be suitable:A. Use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate. B. Use Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Fargate.Here's the rationale behind these solutions:Option A: Use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate. Amazon ECS is a fully managed container orchestration service provided by AWS. AWS Fargate is a serverless compute engine for containers that works with ECS. It allows you to run containers without the need to manage underlying infrastructure. You can define the desired scaling behavior for your container services, and AWS Fargate will automatically scale in and out based on demand. This solution provides a managed environment for running containers, ensuring scalability and eliminating operational overhead.Option B: Use Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Fargate. Amazon EKS is a fully managed Kubernetes service provided by AWS. AWS Fargate is also available as a compute engine for EKS. With EKS and Fargate, you can deploy and manage Kubernetes clusters without managing the underlying infrastructure. AWS Fargate automatically scales your container workloads based on demand, ensuring efficient scalability without additional operational overhead.Option C: Provision an Amazon API Gateway API. Connect the API to AWS Lambda to run the containers. While Amazon API Gateway and AWS Lambda are powerful services for building serverless applications, they are not specifically designed for managing and scaling Docker containers. This option does not provide the same level of container orchestration and scalability as the ECS or EKS options.Option D: Use Amazon Elastic Container Service (Amazon ECS) with Amazon EC2 worker nodes. Using ECS with EC2 worker nodes would require managing the underlying infrastructure, such as EC2 instances, scaling groups, and cluster management. This option introduces additional operational overhead and infrastructure to manage, which contradicts the requirement of minimizing operational overhead. Option E: Use Amazon Elastic Kubernetes Service (Amazon EKS) with Amazon EC2 worker nodes. Using EKS with EC2 worker nodes would also require managing the underlying infrastructure, including EC2 instances, scaling groups, and cluster management. This option introduces additional operational overhead and infrastructure to manage, which contradicts the requirement of minimizing operational overhead.Therefore, the most suitable solutions that meet the requirements of a managed service for hosting Docker containers in the AWS Cloud, with appropriate scaling and minimal operational overhead, are to use Amazon Elastic Container Service (Amazon ECS) with AWS Fargate (Option A) or use Amazon Elastic Kubernetes Service (Amazon EKS) with AWS Fargate (Option B). Both options provide a managed environment for running containers, automatic scaling, and eliminate the need for managing underlying infrastructure.