ANS-C01 Question 8
Select 2You are designing an application that serves a global user base with low latency requirements. The application involves static content, dynamic content, and API traffic. To ensure optimal user performance and efficient traffic management, which combination of AWS services would you use?
- A
Amazon CloudFront with AWS Global Accelerator
- B
Amazon S3 Transfer Acceleration
- C
AWS Direct Connect
- D
Amazon Route 53 with latency-based routing
- E
AWS Elastic Load Balancer (ELB) configured with geolocation routing
Show answer and explanation
Correct answers: A, D
Explanation
To optimize user performance and traffic management for global architectures, Amazon CloudFront ensures low-latency delivery of static and dynamic content through its edge locations, while AWS Global Accelerator provides optimized routing for APIs and dynamic traffic. Combining this with Amazon Route 53's latency-based routing ensures traffic is routed to the closest and most optimal AWS region or endpoint, achieving the desired performance for a global user base.
- A. Correct.
Amazon CloudFront and AWS Global Accelerator together provide a highly optimized global distribution system for static and dynamic content. CloudFront caches content at edge locations for low latency, while Global Accelerator optimizes routing for dynamic content and APIs.
- B. Incorrect.
Amazon S3 Transfer Acceleration is designed for faster uploads of content to S3, but it is not suitable for optimizing the overall performance of a global application serving diverse types of traffic such as APIs or dynamic content.
- C. Incorrect.
AWS Direct Connect is a private network connection to AWS that improves performance for on-premises workloads. However, it does not optimize edge network performance for a global user base.
- D. Correct.
Amazon Route 53 with latency-based routing is ideal for directing user traffic to the most optimal AWS region based on latency, ensuring improved performance for a global user base.
- E. Incorrect.
AWS Elastic Load Balancer (ELB) does not directly provide geolocation routing. It is primarily used for distributing traffic within a single region or VPC, making it unsuitable for this global use case.