A company's packaged application dynamically creates and returns single-use text files in response to user requests. The company is using Amazon CloudFront for distribution, but wants to further…

Question

Options

• AUse Lambda@Edge to compress the files as they are sent to users.
• BEnable Amazon S3 Transfer Acceleration to reduce the response times.
• CEnable caching on the CloudFront distribution to store generated files at the edge.
• DUse Amazon S3 multipart uploads to move the files to Amazon S3 before returning them to users.

• A
  67% (28)
• B
  12% (5)
• C
  17% (7)
• D
  5% (2)

Explanation

Lambda@Edge allows you to run functions at CloudFront edge locations, enabling modifications to content before it's delivered to users, including compression -- which directly reduces data "Lambda@Edge can be used to compress or modify your content before delivering it to end users, which reduces the amount of data transferred." Since code modifications aren't allowed, using Lambda@Edge is a non-invasive way to: Compress responses. Reduce transfer size = lower CloudFront cost. Incorrect Options: B: S3 Transfer Acceleration improves speed, not cost. C: Caching doesn't help if content is always unique (single-use). D: Multipart uploads help with large file uploads, not transfers.

No community discussion yet for this question.