A company wants to optimize its application architecture. They need to run compute resources closer to users in a metropolitan area that does not contain an AWS Region to achieve single-digit millisecond latency, and they also need to deliver static assets globally with minimum latency.
Which TWO options correctly describe how the company should leverage AWS Global Infrastructure components?
- AWS Local Zones should be used to deploy latency-sensitive applications in specific metropolitan areas, as they allow running AWS resources closer to end-users.Answer
- AWS Edge Locations should be utilized to cache static media files globally via Amazon CloudFront to reduce delivery latency.Answer
- CAWS Edge Locations should be used to host the primary application databases within a VPC to ensure localized database write operations.
- DAWS Local Zones operate as completely independent AWS Regions, meaning data stored in them is automatically isolated from the parent Region for regulatory compliance.
- EAWS Regions automatically mirror all deployed EC2 instances and EBS volumes to the nearest Edge Location to prevent data loss in the event of a physical disaster.
Answer
The correct options are the statements that AWS Local Zones should be used to deploy latency-sensitive applications in specific metropolitan areas, and that AWS Edge Locations should be utilized to cache static media files globally via Amazon CloudFront.
AWS Local Zones allow running latency-sensitive applications close to users in specific metropolitan areas by extending a parent Region. AWS Edge Locations are specifically designed to cache content globally via Amazon CloudFront to reduce retrieval latency.
Step-by-Step Solution
Key Concept
AWS Global Infrastructure Components (Local Zones vs Edge Locations)