Q79 — AWS SAA-C03 Ch.11

Question 79 of 100 | ← Chapter 11

Q779. A company has an application that uses Docker containers in its local data center. The application runs on a container host that stores persistent data in a volume on the host. The container instances use the stored persistent data.The company wants to move the application to a fully managed service because the company does not want to manage any servers or storage infrastructure.Which solution will meet these requirements?

Correct Answer: B. Use Amazon Elastic Container Service (Amazon ECS) with an AWS Fargate launch type. Create an Amazon Elastic File System (Amazon EFS) volume. Add the EFS volume as a persistent storage volume mounted in the containers.

Explanation

To meet the requirement of moving the application to a fully managed service without managing any servers or storage infrastructure, the following solution can be implemented:B. Use Amazon Elastic Container Service (Amazon ECS) with an AWS Fargate launch type. Create an Amazon Elastic File System (Amazon EFS) volume. Add the EFS volume as a persistent storage volume mounted in the containers.\1. Use Amazon Elastic Container Service (Amazon ECS) with an AWS Fargate launch type: Amazon ECS is a fully managed container orchestration service provided by AWS. With the Fargate launch type, you can run containers without having to manage the underlying infrastructure.\2. Create an Amazon Elastic File System (Amazon EFS) volume: Amazon EFS is a scalable and fully managed file storage service provided by AWS. It is designed to be highly available and durable. By creating an EFS volume, you can store the persistent data for your containers.\3. Add the EFS volume as a persistent storage volume mounted in the containers: AWS Fargate supports the use of EFS as a persistent storage solution. You can configure your ECS task definition to mount the EFS volume as a persistent storage volume in the containers. This ensures that the containers have access to the stored persistent data.Here's why the other options are not the most suitable choices:A. Use Amazon Elastic Kubernetes Service (Amazon EKS) with self-managed nodes. Create an Amazon Elastic Block Store (Amazon EBS) volume attached to an Amazon EC2 instance. Use the EBS volume as a persistent volume mounted in the containers:While Amazon EKS is a managed Kubernetes service provided by AWS, it still requires managing the underlying EC2 instances. In this option, the EBS volume would be attached to the EC2 instance, which means you would still need to manage the server and storage infrastructure.C. Use Amazon Elastic Container Service (Amazon ECS) with an AWS Fargate launch type. Create an Amazon S3 bucket. Map the S3 bucket as a persistent storage volume mounted in the containers:Amazon S3 is an object storage service provided by AWS and is not suitable for mounting as a file system within containers. It does not provide file-level access and is optimized for storing and retrieving large objects. It is not designed for persistent storage within containers.D. Use Amazon Elastic Container Service (Amazon ECS) with an Amazon EC2 launch type. Create an Amazon Elastic File System (Amazon EFS) volume. Add the EFS volume as a persistent storage volume mounted in the containers:While using Amazon ECS with an EC2 launch type can provide greater flexibility and control over the underlying infrastructure compared to AWS Fargate, it still requires managing and scaling the EC2 instances. The requirement states that the company wants to move away from managing servers, which makes this option less suitable.Therefore, the most suitable solution to meet the requirement of moving the application to a fully managed service without managing any servers or storage infrastructure is:B. Use Amazon Elastic Container Service (Amazon ECS) with an AWS Fargate launch type. Create an Amazon Elastic File System (Amazon EFS) volume. Add the EFS volume as a persistent storage volume mounted in the containers.