A company provides auction services for artwork and has users across North America and Europe. The company hosts its application in Amazon EC2 instances in the us-east-1 Region. Artists upload…

Question

Options

• ARedeploy the application to use S3 multipart uploads.
• BCreate an Amazon CloudFront distribution and point to the application as a custom origin.
• CConfigure the buckets to use S3 Transfer Acceleration.
• DCreate an Auto Scaling group for the EC2 instances and create a scaling policy.

• A
  10% (4)
• B
  5% (2)
• C
  83% (34)
• D
  2% (1)

Explanation

S3 Transfer Acceleration (C) is correct because it routes uploads through AWS's globally distributed CloudFront edge locations using optimized network paths, dramatically reducing latency for users far from the bucket's home region - exactly what European users need when uploading to a us-east-1 bucket.

A is wrong because multipart uploads improve performance for large files by splitting them into parallel chunks, but the data still travels the same slow transatlantic path - it doesn't solve the geographic latency problem.

B is wrong because CloudFront distributions are designed to cache and deliver content to end users (downloads/reads), not to accelerate uploads to an origin; it's a CDN, not an upload accelerator.

D is wrong because adding more EC2 instances via Auto Scaling addresses compute capacity and availability, but the bottleneck here is network latency between Europe and S3 - more servers don't shorten the distance data travels.

Memory tip: Think of Transfer Acceleration as "putting your S3 bucket on the autobahn" - uploads enter the AWS backbone at the nearest edge location and zip to the destination bucket over AWS's private, optimized network instead of the public internet.

No community discussion yet for this question.