Q48 — AWS SAA-C03 Ch.12

Question 48 of 100 | ← Chapter 12

Q848. A company recently migrated its application to AWS. The application runs on Amazon EC2 Linux instances in an Auto Scaling group across multiple Availability Zones. The application stores data in an Amazon Elastic File System (Amazon EFS) file system that uses EFS Standard-Infrequent Access storage. The application indexes the company's files. The index is stored in an Amazon RDS database.The company needs to optimize storage costs with some application and services changes.Which solution will meet these requirements MOST cost-effectively?

• A. Create an Amazon S3 bucket that uses an Intelligent-Tiering lifecycle policy. Copy all files to the S3 bucket. Update the application to use Amazon S3 API to store and retrieve files. ✓
• B. Deploy Amazon FSx for Windows File Server file shares. Update the application to use CIFS protocol to store and retrieve files.
• C. Deploy Amazon FSx for OpenZFS file system shares. Update the application to use the new mount point to store and retrieve files.
• D. Create an Amazon S3 bucket that uses S3 Glacier Flexible Retrieval. Copy all files to the S3 bucket.Update the application to use Amazon S3 API to store and retrieve files as standard retrievals.

Correct Answer: A. Create an Amazon S3 bucket that uses an Intelligent-Tiering lifecycle policy. Copy all files to the S3 bucket. Update the application to use Amazon S3 API to store and retrieve files.

Explanation

To optimize storage costs for the application that runs on EC2 instances with EFS storage and an RDS database, the solution that will be most cost-effective is:A. Create an Amazon S3 bucket that uses an Intelligent-Tiering lifecycle policy. Copy all files to the S3 bucket. Update the application to use the Amazon S3 API to store and retrieve files.Here's why:Option A suggests creating an S3 bucket with an Intelligent-Tiering lifecycle policy and updating the application to use the S3 API for storing and retrieving files.By using an Intelligent-Tiering lifecycle policy, S3 automatically moves objects between different storage tiers (Frequent Access and Infrequent Access) based on access patterns. This allows you to optimize storage costs by storing less frequently accessed data in the lower-cost Infrequent Access tier.Copying all files from the EFS file system to the S3 bucket allows you to transition the storage of the files from EFS to S3. This eliminates the need for EFS, which can be more expensive compared to S3 storage.Updating the application to use the S3 API for storage and retrieval ensures compatibility with the new storage solution. The S3 API provides a straightforward and cost-effective way to manage files in S3.Option B suggests deploying Amazon FSx for Windows File Server file shares and updating the application to use the CIFS protocol. While FSx for Windows File Server provides a managed file storage solution, it may not be the most cost-effective option compared to transitioning to S3 storage.Option C suggests deploying Amazon FSx for OpenZFS file system shares and updating the application to use the new mount point. While FSx for OpenZFS provides a managed file storage solution, it may not be the most cost-effective option compared to transitioning to S3 storage.Option D suggests creating an S3 bucket that uses S3 Glacier Flexible Retrieval and updating the application to use the S3 API with standard retrievals. While this option may provide cost savings compared to the standard S3 storage, it introduces additional complexities with Glacier retrieval options.Therefore, the most cost-effective solution to optimize storage costs is to create an S3 bucket with an Intelligent-Tiering lifecycle policy, copy all files to the S3 bucket, and update the application to use the S3 API for storing and retrieving files. This approach leverages S3's cost-effective storage tiers and provides a seamless transition from EFS storage.