
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A solutions architect needs to host a high performance computing (HPC) workload in the AWS Cloud. The workload will run on hundreds of Amazon EC2 instances and will require parallel access to a shared file system to enable distributed processing of large datasets. Datasets will be accessed across multiple instances simultaneously. The workload requires access latency within 1 ms. After processing has completed, engineers will need access to the dataset for manual postprocessing.
Which solution will meet these requirements?
A
Use Amazon Elastic File System (Amazon EFS) as a shared file system. Access the dataset from Amazon EFS.
B
Mount an Amazon S3 bucket to serve as the shared file system. Perform postprocessing directly from the S3 bucket.
C
Use Amazon FSx for Lustre as a shared file system. Link the file system to an Amazon S3 bucket for postprocessing.
D
Configure AWS Resource Access Manager to share an Amazon S3 bucket so that it can be mounted to all instances for processing and postprocessing.
Explanation:
Correct Answer: C - Use Amazon FSx for Lustre as a shared file system. Link the file system to an Amazon S3 bucket for postprocessing.
Why this is correct:
Low latency requirement (1 ms): Amazon FSx for Lustre is specifically designed for high-performance computing workloads and provides sub-millisecond latency, which meets the 1 ms requirement.
Parallel access to shared file system: FSx for Lustre is a parallel file system that supports concurrent access from hundreds of EC2 instances simultaneously, which is essential for HPC workloads.
Integration with Amazon S3: FSx for Lustre can be linked to an S3 bucket, allowing:
HPC optimization: Lustre is specifically designed for HPC workloads with features like:
Why other options are incorrect:
A. Amazon EFS: While EFS provides a shared file system, it typically has higher latency (single-digit milliseconds) and is optimized for general-purpose workloads, not HPC workloads requiring sub-millisecond latency.
B. Mounting S3 bucket: S3 cannot be mounted as a traditional file system with POSIX semantics. While there are tools like S3FS, they don't provide the low latency (1 ms) required and aren't suitable for parallel processing from hundreds of instances.
D. AWS Resource Access Manager (RAM): This service is for sharing AWS resources across accounts, not for creating a high-performance shared file system. S3 buckets shared via RAM still have the same limitations as option B.
Key AWS Services: