A training company stores its video files in an S3 bucket in one Region. Learners in Australia and Brazil report several seconds of delay before playback starts, while learners near the Region are happy. Every learner watches the same files. What is the standard fix?

AWS Certified Cloud Practitioner (CLF-C02), objective 3. Cloud technology and services medium

Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.

Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.

The options

Correct Serve the videos through Amazon CloudFront

Correct. CloudFront caches the files at edge locations close to viewers, so the second and subsequent requests in a city are served from that city rather than from across an ocean. Identical content for everyone is the ideal case for a cache.

Not correct Copy the bucket into several Regions and tell each learner which URL to use

Wrong in practice. It can be made to work, but you have taken on the replication, the storage bill in every Region and the job of routing each learner to the right copy — all of which the content delivery network does for you.

Not correct Move the bucket to a Region closer to Australia

Wrong. This trades one unhappy group for another. Moving the origin cannot make one location close to every continent.

Not correct Deploy the workload into an AWS Local Zone near each city

Wrong tool. Local Zones place compute and storage close to a specific metropolitan area for latency-sensitive applications, which is a real answer to a different question. For serving the same static files worldwide, the edge cache is both simpler and far more widely distributed.

Why

The global infrastructure has three tiers worth separating in your head. Regions hold your resources. Availability Zones are the fault-isolated facilities inside a Region. Edge locations are a much larger, much thinner tier used for caching (CloudFront), DNS (Route 53) and traffic entry (Global Accelerator) — you do not launch EC2 instances there. Latency for repeatable content is an edge problem; latency for a whole application in one metro is what Local Zones exist for.

Where this comes from

Cited
AWS exam guide task statement 3.2

Practise this

Reading one question is not practice. The trainer will draw a set from objective 3 and space the ones you get wrong.

Practise AWS Certified Cloud Practitioner (CLF-C02)

More questions on this objective

All questions on Cloud technology and services