AWS Certified Solutions Architect Professional SAP-C02 Practice Question
A financial services company is building a high-frequency trading (HFT) platform on AWS. The core trading algorithms require the absolute lowest possible latency-ideally single-digit milliseconds-to process real-time market data feeds from a major stock exchange located in the New York City (NYC) metropolitan area. The goal is to minimize the round-trip time between the AWS-hosted application and the exchange's matching engine. Which networking and infrastructure strategy should a solutions architect propose to achieve this objective?
Deploy the application within an AWS Local Zone located in the NYC metropolitan area (e.g., us-east-1-nyc-1a).
Deploy the application in the us-east-1 (N. Virginia) Region and configure Amazon Route 53 with Geoproximity routing to the exchange.
Deploy the application in the us-east-1 (N. Virginia) Region and place an AWS Global Accelerator in front of the application endpoints.
Deploy the application to multiple Availability Zones in the us-east-1 (N. Virginia) Region and establish an AWS Direct Connect connection to the exchange.
The correct answer is to deploy the application within an AWS Local Zone in the NYC metropolitan area. AWS Local Zones are a type of infrastructure deployment that places AWS compute, storage, database, and other select services closer to large population, industry, and IT centers. This is the only option that physically places the compute resources within the same metropolitan area as the stock exchange, which is essential for achieving the single-digit millisecond latency required for HFT applications.
Deploying in the us-east-1 Region, even with a Direct Connect, is incorrect because of the physical distance. The us-east-1 region is in Northern Virginia, and the round-trip network latency to NYC would be too high for this HFT use case.
Using AWS Global Accelerator is incorrect because it is designed to optimize the network path from global end-users to applications on AWS by routing them over the AWS global network from the nearest edge location. It does not reduce the inherent physical latency between the AWS Region where the application is hosted and a fixed, non-AWS endpoint like a stock exchange.
Using Amazon Route 53 with Geoproximity routing is incorrect. Route 53 routing policies are used to direct end-user traffic at the DNS level. This service is not suited for optimizing latency for server-to-server communication with a fixed, external data source.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is an AWS Local Zone, and why is it ideal for low-latency applications?
Open an interactive chat with Bash
Why is AWS Direct Connect not sufficient for achieving the lowest latency in this scenario?
Open an interactive chat with Bash
How does AWS Global Accelerator differ from Local Zones when optimizing latency?
Open an interactive chat with Bash
AWS Certified Solutions Architect Professional SAP-C02
Design Solutions for Organizational Complexity
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access