A financial services firm is designing a high-frequency trading platform on AWS. The system must meet two major requirements: it must provide single-digit millisecond latency to an on-premises trading environment in a metropolitan area where no AWS Region exists, and it must replicate transaction logs to a geographically isolated recovery site located more than 250 miles away to satisfy disaster recovery regulations.
Which TWO of the following AWS infrastructure components or deployment models should the firm choose to meet these requirements?
- Deploying latency-sensitive application components in an AWS Local Zone located in the metropolitan area.Answer
- Replicating transaction logs to an AWS Region located at least 250 miles away from the primary site.Answer
- CDeploying latency-sensitive application components in an AWS Edge Location using Amazon CloudFront.
- DReplicating transaction logs to a different Availability Zone within the same primary AWS Region.
- EInstalling AWS Outposts directly at a nearby AWS Edge Location to run the trading applications.
Answer
The firm should deploy the latency-sensitive components in an AWS Local Zone in the metropolitan area and replicate transaction logs to a different AWS Region located at least 250 miles away.
AWS Local Zones extend AWS infrastructure into metropolitan areas, providing the necessary single-digit millisecond latency to on-premises systems without requiring a full Region. To meet the disaster recovery requirement of 250+ miles of separation, replication must cross between distinct AWS Regions, as Availability Zones within a single Region are located in the same geographic area for low-latency clustering.
Step-by-Step Solution
Key Concept
AWS Regions vs. Availability Zones vs. Local Zones and Edge Locations
Estimated Time:3m 0s