A media production team is deploying a collaborative video editing application on AWS. The… — AWS Certified Solutions Architect - Associate

A media production team is deploying a collaborative video editing application on AWS. The application runs on a fleet of Amazon EC2 Linux instances that require concurrent read and write access to a shared directory. The workload is highly unpredictable, with aggregate throughput scaling rapidly from $50\text{ MB/s}$ to over $3\text{ GB/s}$ within seconds during active editing periods. The application requires latency of less than $1\text{ ms}$ for metadata operations and must not experience performance throttling during sudden spikes.

Which storage configuration meets these requirements with the lowest operational overhead?

Amazon Elastic File System (Amazon EFS) configured with General Purpose performance mode and Elastic throughput.Answer
B
Amazon Elastic File System (Amazon EFS) configured with Max I/O performance mode and Provisioned throughput set to $3\text{ GB/s}$ .
C
Amazon Elastic Block Store (Amazon EBS) gp3 volumes configured with EBS Multi-Attach enabled and formatted with a clustered file system.
D
Amazon FSx for Lustre persistent SSD file system configured with data repository integration to automatically sync with Amazon S3.

Answer

Amazon Elastic File System (Amazon EFS) configured with General Purpose performance mode and Elastic throughput.

The configuration of Amazon EFS with General Purpose performance mode and Elastic throughput satisfies all requirements. General Purpose mode ensures that metadata operations maintain sub-millisecond latencies. Elastic throughput is ideal for unpredictable workloads, automatically scaling up to

10\text{ GB/s}

for reads and

3\text{ GB/s}

for writes to accommodate sudden spikes without provisioning overhead.

Step-by-Step Solution

Analyze the access requirement.

The instances require concurrent read and write access to a shared directory, pointing to a shared file system solution such as Amazon EFS or Amazon FSx.

Amazon EBS volumes (except io1/io2 with Multi-Attach) cannot be attached to multiple instances simultaneously, and standard block storage is not a shared file system.

Evaluate latency and performance requirements.

Metadata operations must be under

1\text{ ms}

, which requires Amazon EFS General Purpose mode rather than Max I/O mode.

Max I/O mode trades higher metadata latencies for higher scale-out parallel throughput.

Select the appropriate throughput mode based on the scaling pattern.

The throughput is highly unpredictable, scaling rapidly up to

3\text{ GB/s}

. Elastic throughput handles this automatically without manual capacity management.

Elastic throughput automatically scales up and down to match workload demands, avoiding throttling and operational overhead.

Key Concept

Selecting and configuring the optimal Amazon EFS performance and throughput modes for low-latency, highly unpredictable shared storage workloads.

Estimated Time:2m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic