Question

Difficulty: HardHigh-Performing and Scalable Storage Solutions

An enterprise is migrating a latency-sensitive high-performance compute (HPC) application to AWS. The workload runs on a cluster of Linux EC2 instances distributed across multiple Availability Zones in a Region. The application requires a shared file system that is POSIX-compliant, supports NFS, and must deliver consistent sub-millisecond latencies, up to 80,00080,000 IOPS, and 2 GB/s2\text{ GB/s} of throughput to handle concurrent read and write operations. Which storage solution should a solutions architect recommend to meet these requirements?

  1. A
    Configure Amazon EBS io2 volumes with Multi-Attach enabled and mount them to the EC2 instances.
  2. B
    Configure an Amazon EFS file system using Elastic throughput mode.
  3. Configure an Amazon FSx for NetApp ONTAP file system in a Multi-AZ deployment.Answer
  4. D
    Configure an Amazon FSx for Lustre file system using a Persistent deployment type.

Answer

Configure an Amazon FSx for NetApp ONTAP file system in a Multi-AZ deployment.
The correct option is the FSx for NetApp ONTAP file system in a Multi-AZ deployment because it provides POSIX-compliant NFS shares across multiple Availability Zones with sub-millisecond latencies (leveraging NVMe caching) and easily scales to 80,00080,000 IOPS and 2 GB/s2\text{ GB/s} throughput.

Step-by-Step Solution

1
Analyze the availability zone and shared storage requirements.
The solution must support multiple EC2 instances across multiple Availability Zones simultaneously using a POSIX-compliant, NFS-supported file system.
This rules out single-AZ solutions or block storage that cannot span multiple Availability Zones.
2
Evaluate the performance constraints (sub-millisecond latency, 80,00080,000 IOPS, 2 GB/s2\text{ GB/s} throughput).
Amazon EFS is ruled out because it typically operates with low single-digit millisecond latency rather than sub-millisecond latency.
EFS does not meet the strict latency requirement of the HPC application.
3
Assess the multi-AZ and protocol capabilities of the remaining options.
Amazon EBS io2 with Multi-Attach is limited to a single AZ. Amazon FSx for Lustre only supports Single-AZ deployments. Amazon FSx for NetApp ONTAP supports Multi-AZ deployments with synchronous replication and delivers sub-millisecond latency via NVMe caching.
FSx for NetApp ONTAP is the only solution that satisfies all shared access, protocol, multi-AZ, and performance requirements.

Key Concept

Selecting high-performing, multi-AZ shared storage solutions based on latency, throughput, and protocol requirements.
Estimated Time:2m 30s
Rate this question