An organization is designing a high-frequency financial analytics platform. The architecture has two primary requirements:
1. The relational database tier must support synchronous replication and automatic failover across physically separated facilities while remaining within a single national boundary for compliance.
2. The data ingestion compute tier must run as close as possible to users in metropolitan areas that do not host a full AWS Region, to minimize network latency.
Which of the following deployment strategies should the organization use to meet these requirements? (Select TWO.)
- ADeploy the relational database tier across multiple AWS Regions to achieve synchronous replication.
- Deploy the relational database tier across multiple Availability Zones in a single AWS Region.Cevap
- Deploy the data ingestion compute tier in AWS Local Zones located in the targeted metropolitan areas.Cevap
- DDeploy the data ingestion compute tier in AWS Edge Locations using Amazon CloudFront.
- EDeploy the relational database tier in AWS Wavelength Zones to guarantee ultra-low latency.
Cevap
Deploying the relational database tier across multiple Availability Zones in a single AWS Region, and deploying the data ingestion compute tier in AWS Local Zones located in the targeted metropolitan areas.
To achieve high availability with synchronous replication and automatic failover within a single national boundary, the database must be deployed across multiple Availability Zones within a single AWS Region. To deliver ultra-low latency compute to metropolitan areas without a local AWS Region, AWS Local Zones should be utilized to host the data ingestion tier close to the end-users.
Adım Adım Çözüm
Anahtar Kavram
Understanding the distinct use cases and architectural properties of AWS Regions, Availability Zones, Local Zones, and Edge Locations.