AWS Certified Solutions Architect Professional SAP-C02 Practice Question

The correct approach is to deploy the latency-sensitive front-end of the application in the AWS Local Zone located in Miami. AWS Local Zones are a type of infrastructure deployment that extends an AWS Region to place compute, storage, and other select services closer to large population and industry centers. They are specifically designed for applications that require single-digit millisecond latency to end-users. By deploying the front-end in the Miami Local Zone, the company can meet its latency target. The Local Zone maintains a high-bandwidth, secure connection to its parent Region (us-east-1), allowing the front-end to seamlessly communicate with the backend services, analytics, and control plane running in the highly available, multi-AZ environment of the parent region, thereby meeting the reliability requirement.

Using only Amazon CloudFront is incorrect because CloudFront is designed to cache content at edge locations to reduce latency for content delivery, not for application compute processing. The trade execution logic would still run in us-east-1, failing to meet the latency requirement.

Deploying an AWS Outposts rack is not the optimal solution. Outposts is a service that extends AWS infrastructure to a customer's on-premises data center. This would require the company to procure and manage a physical site in Miami, which adds significant operational overhead compared to using a fully managed AWS Local Zone. Local Zones are the more direct and fitting solution for extending AWS services to a metro area for latency purposes.

Using a multi-region strategy with latency-based routing would not work because no AWS Region is physically close enough to Miami to provide single-digit millisecond latency. Routing to the nearest region, us-east-1, would still result in latency that is too high for the trading platform's requirements.