Which combination of steps will resolve the latency issue?

Explanations:

Doubling the Auto Scaling group’s maximum number of servers will not directly address the latency issue caused by serving static content from the EC2 instance. This could lead to increased costs without resolving the core issue.

Hosting the application code on AWS Lambda is not relevant to resolving high latency for static content. Lambda is more suited for serverless architectures and does not specifically address content delivery.

Scaling vertically by resizing the EC2 instances may improve performance, but it does not specifically target the static content latency issue. Moreover, vertical scaling has limitations and may not effectively address the high latency experienced globally.

Creating an Amazon CloudFront distribution will cache the static content closer to users around the world, significantly reducing latency as CloudFront delivers content from edge locations near the users.

Storing the application’s static content in Amazon S3 allows for scalable and durable storage, and when combined with CloudFront, it further enhances content delivery speed and reduces latency by offloading static content from the EC2 instance.