A media production studio is deploying a collaborative video rendering pipeline on AWS usi… — AWS Certified Solutions Architect - Associate

A media production studio is deploying a collaborative video rendering pipeline on AWS using a fleet of $150$ Amazon EC2 instances. The rendering nodes require concurrent read/write access to a shared file system. The storage solution must deliver sub-millisecond latencies, scale up to $12\text{ GiB/s}$ of aggregate throughput, and support millions of IOPS. The studio's source assets are currently stored in an Amazon S3 bucket, and all rendered outputs must be automatically exported back to the same S3 bucket. Which combination of actions should a solutions architect take to meet these requirements? (Select TWO.)

Provision an Amazon FSx for Lustre file system using SSD storage, and configure it with a Persistent-2 deployment type.Answer
Configure a Data Repository Association (DRA) between the Amazon FSx for Lustre file system and the Amazon S3 bucket.Answer
C
Configure an Amazon EFS file system with Elastic throughput mode, and mount it on the EC2 instances using the EFS mount helper.
D
Provision Amazon EBS io2 Block Express volumes with Multi-Attach enabled, and use AWS DataSync to copy assets from Amazon S3.
E
Provision an Amazon FSx for OpenZFS file system, mount it via NFS on the EC2 instances, and run a cron job to sync data with Amazon S3.

Answer

Provision an Amazon FSx for Lustre file system using SSD storage with a Persistent-2 deployment type, and configure a Data Repository Association (DRA) between the FSx for Lustre file system and the Amazon S3 bucket.

To meet the demands of a collaborative media rendering fleet of

150

EC2 instances, a parallel file system like Amazon FSx for Lustre is required. Configuring it with SSD storage and a Persistent-2 deployment type delivers sub-millisecond latencies, millions of IOPS, and allows scaling aggregate throughput to

12\text{ GiB/s}

or more. Creating a Data Repository Association (DRA) between the FSx for Lustre file system and the S3 bucket automates the lifecycle of importing assets and exporting rendered files back to S3 asynchronously.

Step-by-Step Solution

Analyze workload requirements and scale constraints.

The requirements include a shared parallel file system supporting 150 instances, sub-millisecond latency,

12\text{ GiB/s}

throughput, millions of IOPS, and bidirectional S3 synchronization.

Determines the threshold limits for storage volume, file system type, and interface capabilities.

Evaluate candidate shared storage architectures.

EBS Multi-Attach is ruled out due to its 16-instance limit. EFS is ruled out because its Elastic throughput limit (

10\text{ GiB/s}

read,

3\text{ GiB/s}

write) falls short of the

12\text{ GiB/s}

target. FSx for Lustre SSD satisfies the performance and scale parameters.

Isolates the storage engine that matches high-performance computing and media rendering profiles.

Select data synchronization mechanisms.

FSx for Lustre's Data Repository Association (DRA) natively links to S3 for automated, low-overhead file ingestion and export, whereas FSx for OpenZFS or EFS would require complex, manual tooling.

Identifies the mechanism that fulfills the S3 integration requirement with the lowest operational overhead.

Key Concept

High-Performance Shared Parallel Storage with Amazon FSx for Lustre and S3 Integration

Estimated Time:2m 30s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic