SAA-C03 Design High-Performing Architectures Practice Question

A media company serves on-demand video to viewers worldwide from an Amazon S3 bucket in us-east-1. Viewers in Asia and Europe report slow start times because the first byte takes several seconds to arrive. The videos are already stored as objects and must remain in the us-east-1 bucket as the origin. Which solution improves global read performance with the LEAST operational effort?

⚠ Common exam trap

The trap here is assuming that replicating or accelerating data movement is the same as caching content close to viewers, when only an edge cache removes the repeated long-haul fetch.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Create an Amazon CloudFront distribution with the S3 bucket as the origin and serve objects through the distribution.

CloudFront is the managed content delivery layer for S3 origins: it caches objects at edge locations close to viewers and retrieves uncached content over the AWS backbone, cutting first-byte latency for globally distributed users. It needs no data duplication and no application rewrite, so it satisfies both the performance goal and the least-effort requirement while keeping the origin bucket in us-east-1.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Enable S3 Cross-Region Replication to replicate objects into buckets in ap-southeast-1 and eu-west-1, then point each region's viewers at its local bucket.
Why it's wrong here
Cross-Region Replication does place copies closer to viewers, but it requires creating and maintaining destination buckets, replication rules, IAM roles, and per-region endpoint logic. The question states the objects must remain in the us-east-1 bucket as the origin, and this approach adds significant operational overhead compared with a managed CDN caching layer.
✗
Move the bucket to an S3 Multi-Region Access Point and configure the application to read through the access point.
Why it's wrong here
Multi-Region Access Point is built on S3 Cross-Region Replication and requires replicating data into multiple buckets, plus routing configuration and application changes. It accelerates access by routing to the nearest replica, but it does not cache objects at the edge, and it imposes replication and management overhead that conflicts with the requirement to keep objects in the existing us-east-1 bucket with least effort.
✓
Create an Amazon CloudFront distribution with the S3 bucket as the origin and serve objects through the distribution.
Why this is correct
CloudFront caches objects at edge locations near viewers and uses the AWS global backbone to fetch from the us-east-1 origin, so first-byte latency drops for Asia and Europe without duplicating data or changing the bucket. Because it is a managed service configured against the existing origin, operational effort is minimal and the objects stay where they are.
✗
Enable S3 Transfer Acceleration on the bucket and rewrite the application to upload and download through the accelerated endpoint.
Why it's wrong here
Transfer Acceleration speeds up transfers by routing through edge locations, but it is designed primarily for uploads and for clients that can use the accelerated endpoint. It does not provide cached read replicas near viewers, so repeated downloads still traverse the network to us-east-1, and the application must be changed, adding effort without solving the read-latency problem.

Quick reference

AWS S3 Storage Class Comparison

Storage Class	Min Duration	Retrieval	Use Case
S3 Standard	None	Immediate	Frequently accessed data
S3 Standard-IA	30 days	Immediate	Infrequent access, rapid retrieval
S3 One Zone-IA	30 days	Immediate	Non-critical infrequent data
S3 Intelligent-Tiering	None	Immediate–hours	Unknown or changing access patterns
S3 Glacier Instant	90 days	Milliseconds	Archive with instant retrieval
S3 Glacier Flexible	90 days	Minutes–hours	Archive, flexible retrieval
S3 Glacier Deep Archive	180 days	Hours	Long-term compliance archive

Go deeper

SAA-C03 Design High-Performing Architectures Practice Question

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question