A multi-national logistics provider is launching a tracking application. The architecture must satisfy two distinct requirements:
1. Static assets (such as tracking portal images and stylesheets) must be cached and delivered with sub-millisecond latency to customers globally.
2. The core transactional database containing customer shipment records must be kept within a specific geographic area to comply with local data sovereignty regulations.
Which combination of AWS infrastructure components best addresses these requirements?
- AAWS Regions for caching static assets, and Availability Zones for database data sovereignty.
- BAvailability Zones for caching static assets, and Edge Locations for database data sovereignty.
- Edge Locations for caching static assets, and a specific AWS Region for database data sovereignty.Answer
- DEdge Locations for caching static assets, and Amazon EBS volumes for database data sovereignty.
Answer
Edge Locations for caching static assets, and a specific AWS Region for database data sovereignty.
Edge Locations are used to cache static assets close to end-users, ensuring sub-millisecond delivery latency. AWS Regions are independent geographic areas, and deploying resources in a specific Region guarantees that data remains in that Region, satisfying data sovereignty requirements.
Step-by-Step Solution
Key Concept
AWS Global Infrastructure components (Regions and Edge Locations) and their distinct use cases for data residency and latency optimization.
Estimated Time:1m 15s