Which additional steps should the solutions architect take to meet these requirements?

Explanations:

Deploying a second API Gateway regional API endpoint in us-east-1 and integrating it with the existing Lambda functions in us-east-1 is the correct way to make the API available in the new Region. This provides regional availability and ensures that requests are handled by Lambda functions in the same Region as the API Gateway endpoint.

While DynamoDB Streams can be used for data replication, it’s not the most efficient or cost-effective way to replicate an entire table for multi-Region availability. Streams are better suited for event-driven architectures where you need to react to individual data changes.

Creating a DynamoDB global table is the recommended and most efficient way to replicate data across multiple Regions for low-latency access and disaster recovery. Global tables automatically replicate data changes between Regions, ensuring that the API in both Regions has access to the same data.

Changing the API Gateway endpoint to edge-optimized would improve caching and reduce latency for users globally, but it does not make the APIavailablein us-east-1. The endpoint would still be primarily in eu-west-1. Edge-optimized endpoints cache responses, but they still route requests to the origin Region. Also, a single API Gateway cannot integrate with Lambda functions in multiple Regions.

DynamoDB read replicas are for scaling read capacity within a single Region, not for cross-Region replication. They do not automatically replicate data changes from the primary table in another Region.