Which solution will meet these requirements?
Deploy the applications in eu-central-1. Extend the company’s VPC from eu-central-1 to an edge location in Amazon CloudFront.
Deploy the applications in AWS Local Zones by extending the company’s VPC from eu-central-1 to the chosen Local Zone.
Deploy the applications in eu-central-1. Extend the company’s VPC from eu-central-1 to the regional edge caches in Amazon CloudFront.
Deploy the applications in AWS Wavelength Zones by extending the company’s VPC from eu-central-1 to the chosen Wavelength Zone.
Explanations:
Edge locations in Amazon CloudFront are primarily used for content delivery, not for deploying full applications. Extending the VPC to an edge location does not support application hosting or compute resources and will not provide single-digit millisecond latency for application operations.
AWS Local Zones provide compute and storage services close to end-users for low-latency requirements. By extending the VPC from eu-central-1 to a Local Zone, the company can deploy applications in the Local Zone, achieving single-digit millisecond latency without needing to host in eu-central-1, complying with regulations.
Regional edge caches in Amazon CloudFront are used for caching content and optimizing delivery, not for deploying applications or providing compute resources. Extending the VPC to a regional edge cache will not meet the application latency or hosting requirements.
AWS Wavelength Zones are designed for ultra-low latency applications over 5G networks, specifically tailored to mobile edge use cases. They are not applicable to general-purpose applications or on-premises requirements without a 5G use case, making it an unsuitable solution for this scenario.
I strategize that the answer is:
Deploy the applications in AWS Local Zones by extending the company’s VPC from eu-central-1 to the chosen Local Zone.