A company website hosts patches for software that is sold globally. The website runs in AWS and performs well until a large software patch is released. The flood of downloads puts a strain on the…

Question

Options

• AUse an Amazon CloudFront distribution to cache static content, including software patches
• BIncrease the size of the NAT instance to improve throughput
• CScale out of web servers in advance of patch releases to reduce Auto Scaling delays
• DMove the content to IO1 and provision additional IOPS to the volume that contains the software

• A
  73% (16)
• B
  9% (2)
• C
  5% (1)
• D
  14% (3)

Explanation

Amazon CloudFront is a Content Delivery Network (CDN) that caches static content - like software patches - at edge locations worldwide, so users download from a nearby server rather than hammering the origin web servers. This directly addresses all three goals: better customer experience (faster downloads), higher availability (origin servers aren't overwhelmed), and lower cost (fewer compute resources needed at origin).

Why the distractors fail:

• B - A NAT instance handles outbound traffic from private subnets; it has nothing to do with inbound download throughput from customers.
• C - Pre-scaling reduces Auto Scaling lag but still routes all traffic through your web servers, keeping costs high and not solving the fundamental bottleneck.
• D - IO1 with provisioned IOPS improves disk I/O performance, but the bottleneck here is network throughput and web server load - not disk read speed.

Memory tip: When you see "static content + global users + cost-effective + spike traffic," think CloudFront first. The pattern is: patch/image/file downloads → CDN caching → origin offload.

No community discussion yet for this question.