Q6 — AWS SAA-C03 Ch.11

Question 6 of 100 | ← Chapter 11

Q706. A company is deploying a new application to Amazon Elastic Kubermetes Service (Amazon EKS) with an AWS Fargate cluster. The application needs a storage solution for data persistence. The solution must be highly available and fault tolerant The solution also must be shared between multiple application containers. Which solution will meet these requirements with the LEAST operational overhead?

Correct Answer: B. Create an Amazon Elastic File System (Amazon EFS) file system. Register the file system in a StorageClass object on an EKS cluster Use the same file system for all containers.

Explanation

To meet the requirements of a highly available and fault-tolerant storage solution for a new application deployed on Amazon Elastic Kubernetes Service (EKS) with an AWS Fargate cluster, with the least operational overhead, the recommended solution is:B. Create an Amazon Elastic File System (Amazon EFS) file system. Register the file system in a StorageClass object on an EKS cluster. Use the same file system for all containers. Option B provides a solution that meets the requirements with the least operational overhead:- Create an Amazon Elastic File System (Amazon EFS) file system: Amazon EFS is a fully managed, elastic, and scalable file storage service. It provides a shared file system that can be mounted concurrently by multiple containers, making it suitable for scenarios where data needs to be shared between containers.- Register the file system in a StorageClass object on an EKS cluster: In Kubernetes, StorageClass is used to define different storage configurations and classes. By registering the Amazon EFS file system in a StorageClass object on the EKS cluster, you can easily define and manage the storage requirements for the application.- Use the same file system for all containers: With Amazon EFS, multiple containers within the EKS cluster can mount and access the same file system simultaneously. This allows for data sharing between containers and ensures data persistence.Option A, creating Amazon Elastic Block Store (Amazon EBS) volumes in the same Availability Zones where EKS worker nodes are placed and using EBS Multi-Attach to share the data between containers, may provide shared storage, but EBS Multi-Attach is currently not supported for EKS clusters running on Fargate. Therefore, it does not meet the requirement of the least operational overhead.Option C, creating an Amazon EBS volume and using the same volume for all containers, does not provide shared storage between containers. Each container would need its own volume, which does not meet the requirement of data sharing between multiple containers.Option D, creating Amazon EFS file systems in the same Availability Zones where EKS worker nodes are placed and using an AWS Lambda function to synchronize the data between file systems, introduces additional complexity and operational overhead with the need for a custom synchronization mechanism. This does not meet the requirement of the least operational overhead.Therefore, the best solution to meet the requirements with the least operational overhead is B: Create an Amazon Elastic File System (Amazon EFS) file system, register it in a StorageClass object on the EKS cluster, and use the same file system for all containers. This solution provides a highly available and fault- tolerant shared file storage solution for the application.