AWS Certified Cloud Practitioner
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company wants to use Amazon EC2 instances to provide a static website to users all over the world. The company needs to minimize latency for the users.
Which solution meets these requirements?
Real Exam
Community
RRitesh
0
A
Use EC2 instances in multiple edge locations.
B
Use EC2 instances in the same Availability Zone but in different AWS Regions.
C
Use Amazon CloudFront with the EC2 instances configured as the source.
D
Use EC2 instances in the same Availability Zone but in different AWS accounts.
Explanation:
Explanation
Amazon CloudFront is AWS's Content Delivery Network (CDN) service designed specifically to minimize latency for users accessing content globally. Here's why option C is correct:
Key Points:
- CloudFront's Global Edge Network: CloudFront has a global network of edge locations that cache content closer to end users, reducing latency significantly.
- Static Website Optimization: For static websites, CloudFront can cache content at edge locations, serving it directly to users without hitting the origin EC2 instances for every request.
- Origin Configuration: EC2 instances can be configured as the origin for CloudFront, allowing CloudFront to fetch content from EC2 when needed and cache it at edge locations.
Why Other Options Are Incorrect:
- Option A: EC2 instances are not available in edge locations. Edge locations are specifically for services like CloudFront, not for running EC2 instances.
- Option B: Placing EC2 instances in the same Availability Zone but different Regions doesn't address global latency. Users far from those Regions would still experience high latency.
- Option D: Using different AWS accounts doesn't reduce latency. The physical location of the instances is what matters for latency, not the account structure.
Best Practice:
For global static websites, the recommended AWS architecture is:
- Host static content on EC2 instances (or better yet, Amazon S3 for cost efficiency)
- Configure CloudFront as a CDN with the EC2/S3 as the origin
- Enable caching at CloudFront edge locations
- Use Route 53 for DNS routing if needed
This architecture ensures users get content from the nearest edge location, minimizing latency regardless of their geographic location.
Comments
Loading comments...