Shared HA Storage for EKS Fargate

SAA-C03 By islever Editorial Last updated

Design highly available and/or fault-tolerant architectures. Determine high-performing and/or scalable storage solutions.

Short answer

B Create an Amazon EFS file system and register it in a StorageClass to provide shared, highly available storage for EKS Fargate containers.

Question

A company is deploying a new application to Amazon Elastic Kubernetes 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?
  1. Create Amazon Elastic Block Store (Amazon EBS) volumes in the same Availability Zones where EKS worker nodes are placed. Register the volumes in a StorageClass object on an EKS cluster. Use EBS Multi-Attach to share the data between containers.
  2. 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. Correct Answer
  3. Create an Amazon Elastic Block Store (Amazon EBS) volume. Register the volume in a StorageClass object on an EKS cluster. Use the same volume for all containers.
  4. Create Amazon Elastic File System (Amazon EFS) file systems in the same Availability Zones where EKS worker nodes are placed. Register the file systems in a StorageClass object on an EKS cluster. Create an AWS Lambda function to synchronize the data between file systems.

Key Takeaways

The question tests choosing a shared, highly available file system for EKS Fargate; the common trap is selecting EBS Multi-Attach, which lacks multi-AZ high availability.

Amazon EFS provides a highly available, fault-tolerant, and shared storage solution for Amazon EKS Fargate clusters. This page establishes that using a single EFS file system registered in a StorageClass meets data persistence and sharing requirements with minimal operational overhead.

Common mistake: Choosing EBS Multi-Attach (Option A) because it allows sharing, but failing to recognize it is restricted to a single Availability Zone and lacks multi-AZ fault tolerance.

Expert Analysis

Why the Answer Is Correct

Amazon EFS is a fully managed, highly available, and fault-tolerant file system that can be concurrently shared across multiple containers and Availability Zones. By registering a single EFS file system in a StorageClass on the EKS cluster, containers can mount the same file system without complex configurations, meeting all requirements with the least operational overhead.

Why the Other Options Are Wrong

Option A uses EBS Multi-Attach, which is restricted to a single Availability Zone and thus does not provide the multi-AZ high availability required. Option C attempts to attach a single standard EBS volume to multiple containers, which is not supported. Option D introduces massive operational overhead by using multiple EFS file systems and a Lambda function for synchronization, which is unnecessary since EFS natively replicates data across AZs.

Community Comment Notes

Commenters correctly noted that EFS is inherently highly available and shared, while EBS is not. As boluwatito pointed out, "EFS provides a highly available, fault-tolerant, and shared storage solution". Marunio highlighted that "EBS isnt HA", and jaswantn added that "EBS with multi attach does not provide HA".

Official Reference

https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

For EKS storage questions requiring shared access and high availability across multiple pods, always prefer Amazon EFS over Amazon EBS. Remember that EBS volumes are zonal and cannot be shared across multiple Availability Zones.

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 7 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 7

  1. boluwatito 👍 4 Answered B
    Overall, Amazon EFS provides a highly available, fault-tolerant, and shared storage solution with minimal operational overhead, making it the ideal choice for persisting data in an Amazon EKS Fargate cluster.
  2. Naveena_Devanga 👍 4
    B, The solution also must be shared between multiple application containers so attaching to each container is not a practical solution.
  3. Marunio 👍 3 Answered B
    B is correct answer because it is high available - EBS isnt HA for that so A isn't dealing with request.
  4. jaswantn 👍 2
    Option A... EBS with multi attach does not provide HA so option B is more appropriate.
  5. Andy_09 👍 4
    Correct answer is B
Show 2 more comments
  1. TruthWS 👍 3
    B bcs EBS only attack one EC2
  2. asdfcdsxdfc 👍 3 Answered B
    B looks correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide