Performing Data Migration for Testing Tasks

Answer: A.

Option A is CORRECT because DynamoDB Point-in-Time Restore enables recovery of a DynamoDB table across AWS regions.

Further, it enables a full table to restore, as well restore of GSI's and LSI's.Restoring a DynamoDB table using Point-in-Time restore consumes no provisioned throughput.Data transfer charges between the regions are the only costs associated with this solution.

Option B is incorrect because this is not the optimal solution.It requires custom code associated with the Lambda function.

Further, there are additional costs associated with DynamoDB streams and Lambda function executions.

Option C is incorrect because this is not the optimal solution.It requires custom code associated with the AWS Glue job.Further, there are additional costs associated with the execution of the Glue job.

Option D is incorrect because this would enable a cross-region global table.

Thus, all the testing would be performed on the production table and data.

This is not the original requirement.

Reference:

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery_Howitworks.html https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.Tutorial.html

The optimal solution for achieving data migration for the purpose of performance testing and UAT on production-like data of a DynamoDB-based backend system in the European regions is option B: Enable DynamoDB Streams on the current DynamoDB table. Create a new DynamoDB table in the new region. Create a Lambda function to poll the current DynamoDB table stream and deliver batch records from streams to the new DynamoDB table.

Option A: Perform Point-in-Time Recovery of their current DynamoDB table into the new region is not a suitable solution because Point-in-Time Recovery is intended for disaster recovery and not for data migration purposes.

Option C: Create a new DynamoDB table in the new region. Create an AWS Glue job to perform a data export from the current DynamoDB table and data import into the new DynamoDB table is a feasible solution, but it involves more steps than necessary, and it requires the use of AWS Glue, which adds complexity to the solution.

Option D: Enable DynamoDB Streams. Add a European region to the current DynamoDB table Global Tables setting is not an optimal solution because Global Tables is designed to keep tables in sync across regions for the purpose of disaster recovery, and not for the purpose of migrating data for testing and UAT.

Option B, on the other hand, is the optimal solution because it involves setting up DynamoDB Streams on the current DynamoDB table to capture all changes made to the table, creating a new DynamoDB table in the new region, and setting up a Lambda function to read data from the DynamoDB stream and insert it into the new DynamoDB table in the European region. This solution is efficient, reliable, and scalable, and it does not require any additional AWS services or tools, making it a cost-effective solution as well.