Ultimate access to all questions.
Answer-first summary for fast verification
Answer: Create an Amazon CloudFront distribution that has the S3 bucket and the ALB as origins. Configure Route 53 to route traffic to the CloudFront distribution.
## Explanation **Correct Answer: A** **Why Option A is correct:** 1. **CloudFront for both static and dynamic content**: Amazon CloudFront is a Content Delivery Network (CDN) that can cache static content from S3 and also serve dynamic content by routing requests to the ALB origin. 2. **Single distribution with multiple origins**: CloudFront supports multiple origins in a single distribution, allowing you to configure different behaviors for different content types (e.g., cache static content from S3, forward dynamic requests to ALB). 3. **Route 53 integration**: Route 53 can route traffic to the CloudFront distribution using an alias record, providing a single entry point for the application. 4. **Performance benefits**: CloudFront provides global edge locations that cache static content close to users and optimize routing for dynamic content, reducing latency for both types of data. **Why other options are incorrect:** **Option B**: This approach unnecessarily introduces AWS Global Accelerator for static content. Global Accelerator is designed for improving performance of non-HTTP applications or applications that require static IP addresses. For static content in S3, CloudFront is the optimal solution. **Option C**: This approach is overly complex and inefficient. Using Global Accelerator with CloudFront as an endpoint doesn't provide additional benefits for static content delivery and adds unnecessary complexity. **Option D**: This approach creates a fragmented architecture with two separate endpoints, which would require the application to handle different domains for different content types. This breaks the user experience and adds complexity to the application logic. **Key AWS Services Used:** - **Amazon CloudFront**: Global CDN for caching static content and optimizing dynamic content delivery - **Amazon S3**: Object storage for static content - **Application Load Balancer (ALB)**: For distributing traffic to EC2 instances - **Amazon Route 53**: DNS service for routing traffic **Best Practice**: Using a single CloudFront distribution with multiple origins and behaviors is the most efficient way to serve both static and dynamic content through a single endpoint while optimizing performance for each content type.
Author: LeetQuiz Editorial Team
No comments yet.
A global company hosts its web application on Amazon EC2 instances behind an Application Load Balancer (ALB). The web application has static data and dynamic data. The company stores its static data in an Amazon S3 bucket. The company wants to improve performance and reduce latency for the static data and dynamic data. The company is using its own domain name registered with Amazon Route 53.
What should a solutions architect do to meet these requirements?
A
Create an Amazon CloudFront distribution that has the S3 bucket and the ALB as origins. Configure Route 53 to route traffic to the CloudFront distribution.
B
Create an Amazon CloudFront distribution that has the ALB as an origin. Create an AWS Global Accelerator standard accelerator that has the S3 bucket as an endpoint. Configure Route 53 to route traffic to the CloudFront distribution.
C
Create an Amazon CloudFront distribution that has the S3 bucket as an origin. Create an AWS Global Accelerator standard accelerator that has the ALB and the CloudFront distribution as endpoints. Create a custom domain name that points to the accelerator DNS name. Use the custom domain name as an endpoint for the web application.
D
Create an Amazon CloudFront distribution that has the ALB as an origin. Create an AWS Global Accelerator standard accelerator that has the S3 bucket as an endpoint. Create two domain names. Point one domain name to the CloudFront DNS name for dynamic content. Point the other domain name to the accelerator DNS name for static content. Use the domain names as endpoints for the web application.