SAP-C02 · Question #251
A company is running an application in the AWS Cloud. The company has several third-party services that integrate with the application through a RESTful API. The API is a serverless implementation…
The correct answer is A. Deploy a second API Gateway regional API endpoint in us-east-1. C. Modify the DynamoDB table to be a global table in eu-west-1 and in us-east-1. To make a serverless RESTful API and its data available in a second AWS Region, deploy a new regional API Gateway endpoint and configure the DynamoDB table as a Global Table.
Question
A company is running an application in the AWS Cloud. The company has several third-party services that integrate with the application through a RESTful API. The API is a serverless implementation with an Amazon API Gateway regional API endpoint that integrates with several different AWS Lambda functions. The application's data is nonrelational and is stored in an Amazon DynamoDB table. The application and the API are running in the eu-west-1 Region. The company needs the API to also be available in the us-east-1 Region. All data must be available in both Regions. A solutions architect already has deployed all the Lambda functions in us-east-1. Which additional steps should the solutions architect take to meet these requirements? (Select TWO.)
Options
- ADeploy a second API Gateway regional API endpoint in us-east-1.
- BEnable DynamoDB Streams on the table in eu-west-1.
- CModify the DynamoDB table to be a global table in eu-west-1 and in us-east-1.
- DChange the API Gateway API endpoint in eu-west-1 to an edge-optimized endpoint.
- ECreate a DynamoDB read replica in us-east-1.
How the community answered
(40 responses)- A55% (22)
- B8% (3)
- D25% (10)
- E13% (5)
Why each option
To make a serverless RESTful API and its data available in a second AWS Region, deploy a new regional API Gateway endpoint and configure the DynamoDB table as a Global Table.
To make the API accessible to users in the `us-east-1` Region, a second regional API Gateway endpoint must be deployed there, which will integrate with the already deployed Lambda functions in that Region.
Enabling DynamoDB Streams is a prerequisite for Global Tables, but it alone does not configure multi-region replication; it's an incomplete step.
Modifying the DynamoDB table to be a Global Table in both `eu-west-1` and `us-east-1` ensures that data is automatically replicated across both Regions, providing multi-master read/write capabilities and fulfilling the requirement for all data to be available in both Regions.
Changing the API Gateway endpoint to edge-optimized leverages CloudFront for lower latency, but it does not deploy the API into a new region or make it available there; it only optimizes access to the existing regional endpoint.
DynamoDB does not use 'read replicas' in the same way as relational databases; Global Tables are the correct solution for multi-region active-active read/write data availability.
Concept tested: Multi-region API Gateway and DynamoDB Global Tables
Source: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/GlobalTables.html
Community Discussion
No community discussion yet for this question.