A company is building a web application on AWS. When a customer sends a request, the application will generate reports and then make the reports…

This solution effectively meets all requirements with minimal operational overhead. Amazon S3 is the ideal service for storing objects of any size, such as reports, and server-side encryption secures the data at rest. Generating a presigned URL provides secure, time-limited access (configurable to 8 hours) to a specific report for a customer without exposing the underlying S3 bucket. S3 Lifecycle configuration rules are a managed feature that can automatically delete objects after a specified period (2 days), eliminating the need for custom scripts or scheduled tasks, thus ensuring the least operational overhead.

A: Amazon DynamoDB has a maximum item size limit of 400 KB, which is insufficient for reports larger than 1 MB. Storing large objects would require complex chunking logic, increasing overhead.

B: This option does not address the 8-hour access limit for customers or the 2-day deletion requirement for old reports. It would require additional components to meet these requirements.

D: Storing large binary files (blobs) in an Amazon RDS database is inefficient and not a recommended practice compared to object storage. Managing a scheduled Lambda function adds more operational overhead than a simple S3 Lifecycle rule.

1. Amazon S3 Developer Guide

Sharing objects using presigned URLs: "A presigned URL gives you access to the object identified in the URL

provided that the creator of the presigned URL has permissions to access that object. That is

if you receive a presigned URL to upload an object

you can upload the object only if the creator of the presigned URL has the necessary permissions to upload that object... All presigned URLs have an expiration date and time." This supports the use of presigned URLs for temporary

secure access.

2. Amazon S3 User Guide

Managing your storage lifecycle: "To manage your objects so that they are stored cost effectively throughout their lifecycle

configure their S3 Lifecycle. An S3 Lifecycle configuration is a set of rules that define actions that Amazon S3 applies to a group of objects... For example... Expire objects - Delete objects after a specified period of time." This confirms that S3 Lifecycle rules are the managed

low-overhead solution for automatic deletion.

3. Amazon DynamoDB Developer Guide

Service

account

and table quotas in Amazon DynamoDB: Under "Item size"

the documentation states

"The maximum size of an item in DynamoDB is 400 KB

which includes both attribute names and values (binary and string)." This confirms why option A is incorrect.

4. AWS Whitepaper

AWS Best Practices for Storing Large Objects (Archived

but principle remains valid): While specific whitepapers evolve

the established best practice is to use Amazon S3 for large

unstructured data (blobs) and databases like RDS for structured

transactional data. Storing large objects in a relational database can lead to performance degradation and higher costs. The "Performance Efficiency" pillar of the AWS Well-Architected Framework also emphasizes selecting the appropriate data store for the workload.