Which set of actions will improve website performance for users worldwide?
Create an Amazon CloudFront distribution and configure the ALB as an origin. Then update the Amazon Route 53 record to point to the CloudFront distribution.
Create a latency-based Amazon Route 53 record for the ALB. Then launch new EC2 instances with larger instance sizes and register the instances with the ALB.
Launch new EC2 instances hosting the same web application in different Regions closer to the users. Then register instances with the same ALB using cross- Region VPC peering.
Host the website in an Amazon S3 bucket in the Regions closest to the users and delete the ALB and EC2 instances. Then update an Amazon Route 53 record to point to the S3 buckets.
Explanations:
Using Amazon CloudFront as a content delivery network (CDN) will cache static content closer to users globally, reducing latency and improving load times. The ALB can serve as the origin, and updating the Route 53 record to point to CloudFront will enhance performance for dynamic content as well by leveraging edge locations.
While a latency-based Route 53 record can direct users to the nearest ALB, simply increasing EC2 instance sizes does not guarantee improved performance for users worldwide, especially if instances are still located in a single region. This option lacks a CDN or regional distribution of content.
Launching new EC2 instances in different regions may reduce latency for users in those regions, but using a single ALB with cross-region VPC peering is not a standard practice and can complicate management. Additionally, it does not utilize a CDN for caching and optimizing content delivery.
Hosting the website solely in an S3 bucket is suitable for static content, but it would not support dynamic content typically served by EC2 instances. Deleting the ALB and EC2 instances would not provide a comprehensive solution for mixed content types, and there would be limitations on functionalities that are usually supported by web servers.