AWS Certified Solutions Architect – Professional — Question 210

A company has developed a new release of a popular video game and wants to make it available for public download. The new release package is approximately
5 GB in size. The company provides downloads for existing releases from a Linux-based, publicly facing FTP site hosted in an on-premises data center. The company expects the new release will be downloaded by users worldwide. The company wants a solution that provides improved download performance and low transfer costs, regardless of a user's location.
Which solutions will meet these requirements?

Answer options

• A. Store the game files on Amazon EBS volumes mounted on Amazon EC2 instances within an Auto Scaling group. Configure an FTP service on the EC2 instances. Use an Application Load Balancer in front of the Auto Scaling group. Publish the game download URL for users to download the package.
• B. Store the game files on Amazon EFS volumes that are attached to Amazon EC2 instances within an Auto Scaling group. Configure an FTP service on each of the EC2 instances. Use an Application Load Balancer in front of the Auto Scaling group. Publish the game download URL for users to download the package.
• C. Configure Amazon Route 53 and an Amazon S3 bucket for website hosting. Upload the game files to the S3 bucket. Use Amazon CloudFront for the website. Publish the game download URL for users to download the package.
• D. Configure Amazon Route 53 and an Amazon S3 bucket for website hosting. Upload the game files to the S3 bucket. Set Requester Pays for the S3 bucket. Publish the game download URL for users to download the package.

Correct answer: C

Explanation

The correct answer is C because using Amazon S3 with CloudFront allows for efficient content delivery worldwide, providing better performance and lower costs for users. Options A and B involve more complex setups with EC2 instances and FTP, which do not optimize global downloads as effectively as S3 with CloudFront. Option D, while utilizing S3, introduces Requester Pays, which could complicate the user experience and is less straightforward than using CloudFront for distribution.