Which solution will provide the LOWEST network latency between the AWS resources and the customers?
Place the resources in the AWS Region that is closest to the company’s headquarters. Move the resources to the Availability Zone that is closest to the customers.
Place all workloads in the AWS Region that is closest to the company’s headquarters.
Place all workloads in the AWS Region that is closest to the majority of customers.
Place the resources in AWS edge locations that are closest to the company’s headquarters.
Explanations:
Placing resources in the region closest to the company’s headquarters and moving them to a nearby availability zone does not minimize latency for customers, as the region may still be far from the customer base.
Placing all workloads in the region closest to the headquarters does not ensure low latency for customers if they are on a different continent, as the physical distance would still cause higher latency.
Placing all workloads in the region closest to the majority of customers minimizes the physical distance between resources and customers, thereby providing the lowest latency possible.
Edge locations are designed primarily for caching content in a content delivery network (CDN), not for hosting workloads. Placing resources only at edge locations will not provide the necessary infrastructure for all workloads.