Question #700
A company hosts its web application on Amazon EC2 instances behind an Auto Scaling group. Despite scaling during peak traffic, users globally report slow loading times for static assets. What should be done to reduce latency? (Choose two.)
Increase the number of instances in the Auto Scaling group.
Migrate the application to Amazon ECS with Fargate.
Upgrade the EC2 instance types to a larger size.
Implement Amazon CloudFront to cache static content.
Transfer static assets to Amazon S3.
Explanation
The issue stems from global users experiencing slow static asset loading, despite Auto Scaling. Scaling EC2 instances (A/C) or migrating to ECS Fargate (B) does not address network latency for static content.
D. Amazon CloudFront caches static content at edge locations, serving it from the nearest location to users, drastically reducing latency.
E. Amazon S3 optimizes static asset delivery by offloading traffic from EC2 and integrates seamlessly with CloudFront for global caching.
Key Points:
- Static content benefits from CDNs (CloudFront) and dedicated storage (S3).
- Scaling compute resources (A/B/C) does not resolve geographic latency issues.
- S3 + CloudFront is a best practice for global static content delivery.
Answer
The correct answer is: DE