Q96 — AWS SAA-C03 Ch.15
Question 96 of 100 | ← Chapter 15
Q1196. A company deploys a new payroll application on a set of two Amazon EC2 instances that run Amazon Linux. The instances have one root volume that stores the operating system and the application.The application needs to store temporary files and provide long-term file storage for all payroll data. Both storage options must have high performance and be compatible with Linux. Both EC2 instances must be able to access long-term payroll data from a single location.The long-term payroll data must be highly available.Which combination of actions will meet these requirements? (Select TWO.)
- A. Change the instances to an instance family that supports instance store volumes for the temporary data. ✓
- B. Deploy an Amazon ElastiCache (Redis OSS) instance. Configure the EC2 instances to save the temporary data to the ElastiCache (Redis OSS) instance.
- C. Create an Amazon S3 bucket. Configure the EC2 instances to save temporary data to the S3 bucket.
- D. Create and attach a new Amazon Elastic Block Store (Amazon EBS) volume to each of the two EC2 instances to store the long-term data.
- E. Deploy an Amazon Elastic File System (Amazon EFS) Regional file system to store the long-term data. ✓
Correct Answer: A. Change the instances to an instance family that supports instance store volumes for the temporary data., E. Deploy an Amazon Elastic File System (Amazon EFS) Regional file system to store the long-term data.
Explanation
To meet the requirements of storing temporary files and providing long-term file storage for payroll data with high performance, Linux compatibility, and high availability, the following combination of actions is most suitable:A. Change the instances to an instance family that supports instance store volumes for the temporary data.Why: Instance store volumes provide temporary block-level storage that is physically attached to the host computer. They are suitable for temporary data storage because they offer high I/O performance and are directly accessible by the EC2 instance. However, it's important to note that instance store volumes are ephemeral, meaning data is lost if the instance is stopped or terminated. For temporary files, this is acceptable as long as the application can handle the loss of this data. E. Deploy an Amazon Elastic File System (Amazon EFS) Regional file system to store the long-term data.Why: Amazon EFS provides a scalable, fully managed, elastic NFS file system for use with AWS Cloud services and on-premises resources. It is designed for high availability and durability, making it suitable for storing long-term payroll data. EFS can be accessed by multiple EC2 instances simultaneously, which meets the requirement that both instances must be able to access the long-term data from a single location. Additionally, EFS is compatible with Linux and offers high performance for file-based workloads.Why the Other Options Are Not Suitable:B. Deploy an Amazon ElastiCache (Redis OSS) instance. Configure the EC2 instances to save the temporary data to the ElastiCache (Redis OSS) instance.Why Not: ElastiCache (Redis OSS) is an in-memory data store that is optimized for high-performance, low- latency access to data. While it is suitable for caching and certain types of temporary data storage, it is not designed for storing large amounts of temporary files or long-term data. Additionally, Redis is a key-value store, not a file system, so it would not be a good fit for storing files. C. Create an Amazon S3 bucket. Configure the EC2 instances to save temporary data to the S3 bucket. Why Not: Amazon S3 is an object storage service that is designed for storing and retrieving any amount of data at any time. While it is highly available and durable, it is not optimized for high-performance file-based workloads, especially for temporary data that requires frequent read/write operations. S3 is better suited for storing large objects, backups, and archives rather than temporary files. D. Create and attach a new Amazon Elastic Block Store (Amazon EBS) volume to each of the two EC2 instances to store the long-term data.Why Not: While Amazon EBS provides persistent block storage for EC2 instances, it is not designed for shared access by multiple instances. Each EBS volume can only be attached to one EC2 instance at a time. Therefore, this option would not meet the requirement that both instances must be able to access the long-term data from a single location. Additionally, while EBS volumes can be highly available, they do not provide the same level of scalability and ease of management as EFS for shared file storage.Conclusion:The combination of actions A and E meets the requirements by providing high-performance temporary storage using instance store volumes and highly available, shared long-term storage using Amazon EFS.