4.7k views
5 votes
A company has an on-premises application that exports log files about users of a website. These

log files range from 20 GB to 30 GB in size. A solutions architect has created an Amazon S3
bucket to store these files. The files will be uploaded directly from the application. The network
connection experiences intermittent failures, and the upload sometimes fails.

A solutions architect must design a solution that resolves this problem. The solution must
minimize operational overhead.


Which solution will meet these requirements?
A. Enable S3 Transfer Acceleration.
B. Copy the files to an Amazon EC2 instance in the closest AWS Region. Use S3 Lifecycle
policies to copy the log files to Amazon S3.
C. Use multipart upload to Amazon S3.
D. Upload the files to two AWS Regions simultaneously. Enable two-way Cross-Region Replication between the two Regions.

1 Answer

7 votes

Final answer:

The solution that will meet the requirements of uploading large log files from an on-premises application to an Amazon S3 bucket with intermittent network failures and minimal operational overhead is to use multipart upload to Amazon S3.

Step-by-step explanation:

The solution that will meet the requirements of uploading large log files from an on-premises application to an Amazon S3 bucket with intermittent network failures and minimal operational overhead is Option C: Use multipart upload to Amazon S3.

Multipart upload is a feature of Amazon S3 that allows large objects to be uploaded in parts. Each part is uploaded independently, and the upload can be resumed from where it left off if there is a failure. This is particularly useful for large files that may take a long time to upload, such as the 20-30 GB log files in this scenario.

By using multipart upload, the application can divide the log files into smaller parts and upload them individually. If there is a network failure, only the failed part needs to be re-uploaded, rather than the entire file. This minimizes the impact of failures and reduces operational overhead.

User Phenome
by
8.3k points