Examkin

Question

Difficulty: MediumHigh-Performing and Scalable Storage Solutions

A software development company is migrating a collaborative code compilation platform to AWS. The platform runs on a fleet of Amazon EC2 instances distributed across multiple Availability Zones. The build workers require concurrent, shared access to a POSIX-compliant repository. The repository must support sub-millisecond latencies for file metadata operations and scale throughput dynamically to handle build bursts. Which two storage configurations should the solutions architect recommend to meet these requirements?

  1. Create an Amazon EFS file system configured with Elastic Throughput.Answer
  2. Provision an Amazon FSx for NetApp ONTAP file system in a Multi-AZ deployment.Answer
  3. C
    Provision an Amazon EBS gp3 volume and enable Multi-Attach to share it across the EC2 instances.
  4. D
    Provision an Amazon EBS io2 volume with Multi-Attach enabled, format it with the ext4 file system, and attach it to the instances in different Availability Zones.
  5. E
    Create an Amazon S3 bucket and configure AWS Transfer Family to mount the bucket as a local POSIX-compliant drive.

Answer

The solutions architect should recommend creating an Amazon EFS file system configured with Elastic Throughput and provisioning an Amazon FSx for NetApp ONTAP file system in a Multi-AZ deployment.
The solution requires a shared, POSIX-compliant storage system that can be accessed concurrently by EC2 instances across multiple Availability Zones with dynamic throughput scaling. Amazon EFS with Elastic Throughput meets these requirements by providing POSIX-compliant shared access that automatically scales to handle throughput spikes. Amazon FSx for NetApp ONTAP in a Multi-AZ deployment also supports concurrent multi-AZ access via NFS and provides high performance with sub-millisecond latencies.

Step-by-Step Solution

1
Identify that the workload requires concurrent read/write shared access from multiple EC2 instances across different Availability Zones, pointing to a network-attached shared file system rather than block storage.
Candidate options must support shared POSIX-compliant file access across multiple Availability Zones.
Block storage like standard EBS is limited to a single Availability Zone and cannot be shared natively across zones.
2
Evaluate Amazon EFS with Elastic Throughput.
EFS supports multi-AZ POSIX-compliant shared file access and automatically scales throughput to meet unpredictable spike requirements.
Elastic Throughput dynamically scales based on workload activity without manual provisioning.
3
Evaluate Amazon FSx for NetApp ONTAP.
FSx for ONTAP provides Multi-AZ deployment options with low-latency POSIX-compliant NFS access and scales performance to handle bursty workloads.
It matches the performance requirements (sub-millisecond latency) and supports cross-AZ file sharing.
4
Evaluate and eliminate EBS options.
EBS volumes cannot span Availability Zones, gp3 does not support Multi-Attach, and io2 Multi-Attach requires a cluster-aware file system to prevent data corruption.
EBS is an AZ-scoped block storage service and standard file systems like ext4 lack write coordination.
5
Evaluate and eliminate S3 options.
S3 is object storage and AWS Transfer Family is for file transfer protocols, not mountable POSIX drives.
S3 does not natively provide POSIX file system capabilities.

Key Concept

Shared POSIX-compliant storage solutions that support concurrent multi-AZ access and scale throughput dynamically.
Rate this question

Topics

High-Performing and Scalable Storage Solutions

More questions from this topic