Exam AWS Certified Solutions Architect - Associate SAA-C02 topic 1 question 556 discussion

CloudFront with CloudFront signed URLs should provide a good balance of performance and cost. Answer should be B

Based on below data I choose CloudFront (ANS B) S3 transfer costs based on US region - S3 ingress: free • S3 to Internet: $0.09 per GB S3 Transfer Acceleration: • Faster transfer times (50 to 500% better) • Additional cost on top of Data Transfer - Pricing: +$0.04 to $0.08 per GB S3 to CloudFront: $0.00 per GB CloudFront to Internet: $0.085 per GB (slightly cheaper than S3) • Caching capability (lower latency) • Reduce costs associated with S3 Requests - Pricing (7x cheaper with CloudFront) S3 Cross Region Replication: $0.02 per GB

B is the answer

CloudFront would lower the cost, S3 Transf Acceleration would improve performance but increase the cost. The maximum file supported by CloudFront is 30GB, datasets are huge but we don't know the actual size of the files. I'd vote for B but cannot be 100% sure.

Q. How should I choose between Transfer Acceleration and Amazon CloudFront’s PUT/POST? Transfer Acceleration optimizes the TCP protocol and adds additional intelligence between the client and the S3 bucket, making Transfer Acceleration a better choice if a higher throughput is desired. If you have objects that are smaller than 1GB or if the data set is less than 1GB in size, you should consider using Amazon CloudFront's PUT/POST commands for optimal performance. Here we talk about Huge file so Transfer Acceleration.

Condition 1) Customers are located across North America and Europe. 2) lower transfer cost Using CloudFront signed url is a suitable choice

Amazon S3 Transfer Acceleration is a bucket-level feature that enables fast, easy, and secure transfers of files over long distances between your client and an S3 bucket. Transfer Acceleration is designed to optimize transfer speeds from across the world into S3 buckets. Transfer Acceleration takes advantage of the globally distributed edge locations in Amazon CloudFront. As the data arrives at an edge location, the data is routed to Amazon S3 over an optimized network path Why use Transfer Acceleration? You might want to use Transfer Acceleration on a bucket for various reasons: Your customers upload to a centralized bucket from all over the world. You transfer gigabytes to terabytes of data on a regular basis across continents. You can't use all of your available bandwidth over the internet when uploading to Amazon S3. https://docs.aws.amazon.com/AmazonS3/latest/userguide/transfer-acceleration.html

CloudFront is not able to cache a large amounts of data and Transfer acceleration is cheaper

Why not C ?(C. Set up a second S3 bucket in the eu-central-1 Region with S3 Cross-Region Replication between the buckets. Direct customer requests to the closest Region. Continue to use S3 signed URLs for access control.) As it goes about huge files and Cloudfront allows files up to 30 Gb only?

I would Go with B. https://stackoverflow.com/questions/36882595/are-there-any-difference-between-amazon-cloudfront-and-amazon-s3-transfer-accele S3 transfer acceleration is for Uploads to S3.

B is correct . A is out as Transfer Acceleration is not supported in all EU regions as question explicitly saying customer are in US and EU. Please refer https://docs.aws.amazon.com/AmazonS3/latest/userguide/transfer-acceleration.html Note Transfer Acceleration is currently not supported for buckets located in the following Regions: Africa (Cape Town) (af-south-1) Asia Pacific (Hong Kong) (ap-east-1) Asia Pacific (Osaka) (ap-northeast-3) Europe (Stockholm) (eu-north-1) Europe (Milan) (eu-south-1) Middle East (Bahrain) (me-south-1)

Its A because CloudFront won't cache that large amount of data

B is secure and fast way of doing it.

I would go with A, they are talking about HUGE datasets which should be delivered, but the CloudFront does have a 20GB limit per file which should be cached. Transfer acceleration does not have any file size limit

B is correct. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/PrivateContent.html

AAAAAAAAA

B is the answer