Question

Difficulty: MediumHigh-Performing and Scalable Storage Solutions

A company is deploying a containerized application across a fleet of Amazon EC2 instances distributed across multiple Availability Zones. The application requires a shared file system where all EC2 instances can concurrently read and write files with sub-millisecond latency. The storage solution must scale throughput automatically based on workload demand without requiring manual provisioning. Which storage solution should a solutions architect recommend to meet these requirements?

  1. Deploy Amazon Elastic File System (Amazon EFS) configured with Elastic Throughput.Answer
  2. B
    Provision an Amazon EBS General Purpose SSD (gp3) volume and mount it to the instances using a shared file system configuration.
  3. C
    Provision an Amazon EBS Provisioned IOPS SSD (io2) volume, enable EBS Multi-Attach, and mount it to all instances.
  4. D
    Create an Amazon S3 bucket and mount it as a local directory on all EC2 instances using the s3fs-fuse utility.

Answer

Deploy Amazon Elastic File System (Amazon EFS) configured with Elastic Throughput.
Amazon Elastic File System (Amazon EFS) is a serverless, shared file system designed to be mounted concurrently by EC2 instances across multiple Availability Zones. By configuring it with Elastic Throughput, the file system automatically scales throughput capacity in response to workload activity, meeting the requirement for automated scaling without manual provisioning.

Step-by-Step Solution

1
Analyze workload requirements.
Identify that the system requires shared concurrent file access across multiple Availability Zones, automatic scaling of throughput, and sub-millisecond latencies.
This establishes the constraints needed to filter out block-level or single-AZ storage solutions.
2
Evaluate EBS options against the multi-AZ concurrent access constraint.
Determine that EBS gp3 and io2 do not natively support multi-AZ shared access.
EBS gp3 is limited to a single instance, and io2 Multi-Attach is restricted to a single Availability Zone and requires cluster-aware application coordination.
3
Evaluate Amazon EFS and S3 file gateway solutions.
Select Amazon EFS as the native POSIX-compliant shared file system.
S3 mounts via FUSE utilities cannot guarantee low-latency POSIX operations, while EFS is designed for shared, scalable multi-AZ access.
4
Configure the throughput mode for EFS.
Choose Elastic Throughput mode.
Elastic Throughput automatically adjusts throughput performance in response to the application's workload, satisfying the automated scaling constraint.

Key Concept

Shared file systems across multiple Availability Zones with automated throughput provisioning using Amazon EFS.
Estimated Time:1m 30s
Rate this question