A company is building a high-performance computing (HPC) application on AWS that runs across a fleet of Linux-based Amazon EC2 instances. The application has two distinct storage requirements: first, it requires high-throughput, lowest-latency block storage for storing temporary scratch files that are discarded when the instances terminate; second, it requires a shared, POSIX-compliant directory structure that all EC2 instances in the fleet can mount simultaneously to read and write application configuration files. Which AWS storage solutions should the company select to meet these requirements? (Select TWO.)
- Amazon EC2 Instance Store to serve as the low-latency block storage for temporary scratch filesCevap
- Amazon Elastic File System (Amazon EFS) to serve as the shared, POSIX-compliant file system for the fleetCevap
- CAmazon Elastic Block Store (Amazon EBS) gp3 volumes to serve as the shared, POSIX-compliant file system for the fleet
- DAmazon Simple Storage Service (Amazon S3) Standard to serve as the low-latency block storage for temporary scratch files
- EAmazon S3 Glacier Deep Archive to serve as the shared, POSIX-compliant file system for the fleet
Cevap
The correct answers are Amazon EC2 Instance Store to serve as the low-latency block storage for temporary scratch files, and Amazon Elastic File System (Amazon EFS) to serve as the shared, POSIX-compliant file system for the fleet.
The correct options are Amazon EC2 Instance Store and Amazon Elastic File System (Amazon EFS). Amazon EC2 Instance Store provides temporary, low-latency block storage directly attached to the host instance, making it ideal for scratch space. Amazon Elastic File System (Amazon EFS) offers a shared, POSIX-compliant file system that allows multiple EC2 instances to mount and access it simultaneously.
Adım Adım Çözüm
Anahtar Kavram
Selecting appropriate AWS storage services based on access patterns, durability requirements, and file systems.