AWS Certified Solutions Architect - Associate
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 runs a web-based portal that provides users with global breaking news, local alerts, and weather updates. The portal delivers each user a personalized view by using a mixture of static and dynamic content. Content is served over HTTPS through an API server running on an Amazon EC2 instance behind an Application Load Balancer (ALB). The company wants the portal to provide this content to its users across the world as quickly as possible.
How should a solutions architect design the application to ensure the LEAST amount of latency for all users?
Other
Community
UAnonymous
A
Deploy the application stack in a single AWS Region. Use Amazon CloudFront to serve all static and dynamic content by specifying the ALB as an origin.
B
Deploy the application stack in two AWS Regions. Use an Amazon Route 53 latency routing policy to serve all content from the ALB in the closest region.
C
Deploy the application stack in a single AWS Region. Use Amazon CloudFront to serve the static content. Serve the dynamic content directly from the ALB.
D
Deploy the application stack in two AWS Regions. Use an Amazon Route 53 geolocation routing policy to serve all content from the ALB in the closest Region.
Explanation:
Explanation
Correct Answer: A
Why Option A is correct:
- Amazon CloudFront is AWS's Content Delivery Network (CDN) service that caches content at edge locations worldwide, reducing latency for users regardless of their geographic location.
- By serving both static and dynamic content through CloudFront with the ALB as the origin, users benefit from:
- Edge caching for static content (images, CSS, JavaScript, etc.)
- Dynamic content acceleration via CloudFront's optimized network paths and TCP optimizations
- HTTPS termination at the edge, reducing SSL/TLS handshake latency
- Global distribution through 400+ edge locations
- CloudFront automatically routes users to the nearest edge location, minimizing latency for both static and dynamic content.
- A single region deployment with CloudFront is more cost-effective and simpler to manage than multi-region deployments.
Why other options are incorrect:
Option B: Deploying in two regions with Route 53 latency routing helps, but:
- Users still connect directly to the ALB in the closest region, which may still be far from their location
- No edge caching benefits for static content
- Higher operational complexity and cost for multi-region deployment
- Dynamic content doesn't get the acceleration benefits of CloudFront
Option C: Serving only static content through CloudFront while dynamic content goes directly to the ALB:
- Misses the opportunity to accelerate dynamic content via CloudFront's optimized routing
- Users experience higher latency for personalized/dynamic content
- Doesn't fully leverage CloudFront's capabilities
Option D: Using geolocation routing instead of latency routing:
- Geolocation routing directs traffic based on geographic location, not actual network latency
- Latency routing is superior as it measures actual network performance and routes to the region with lowest latency
- Still lacks the edge caching and acceleration benefits of CloudFront
Key AWS Services for Low-Latency Global Applications:
- Amazon CloudFront - Global CDN with edge caching and dynamic content acceleration
- AWS Global Accelerator - Improves availability and performance by using AWS's global network infrastructure
- Amazon Route 53 - DNS service with latency-based routing capabilities
For global applications with mixed static and dynamic content, CloudFront provides the best latency reduction by serving content from edge locations closest to users.
Comments
Loading comments...