Exam AWS Certified Database - Specialty topic 1 question 131 discussion

I think the answer is C https://aws.amazon.com/premiumsupport/knowledge-center/dynamodb-cross-account-migration/

Create a DynamoDB table in your source account. Create an Amazon Simple Storage Service (Amazon S3) bucket in the destination account. Attach an AWS Identity and Access Management (IAM) policy to the Data Pipeline default roles in the source account. Create an S3 bucket policy in the destination account. Create and activate a pipeline in the source account. Create a DynamoDB table in the destination account. Restore the DynamoDB export in the destination account. https://aws.amazon.com/de/blogs/database/how-to-migrate-amazon-dynamodb-tables-from-one-aws-account-to-another-with-aws-data-pipeline/

The correct answer is C, because: https://aws.amazon.com/blogs/database/how-to-migrate-amazon-dynamodb-tables-from-one-aws-account-to-another-with-aws-data-pipeline/

I think it is A

Migrate your DynamoDB table to a different AWS account with one of these methods that suit your use case: https://repost.aws/knowledge-center/dynamodb-cross-account-migration - AWS Backup - DynamoDB import and export to Amazon Simple Storage Service (Amazon S3) - Amazon S3 and AWS Glue - Amazon EMR

C looks like the best option https://aws.amazon.com/premiumsupport/knowledge-center/dynamodb-cross-account-migration/

A. Why not?

You can migrate your DynamoDB tables to a different AWS account by choosing one of the following methods depending on your use case: AWS Backup DynamoDB import and export to Amazon Simple Storage Service (Amazon S3) Amazon S3 and AWS Glue AWS Data Pipeline Amazon EMR

Configure Amazon DynamoDB Streams for the DynamoDB table in the current account. Create an AWS Lambda function to read from the stream and write to a file in Amazon S3. Create another Lambda function to read the S3 file and restore the items to a DynamoDB table in the new account. This approach leverages DynamoDB Streams, which captures item-level modifications to a table, including creates, updates, and deletes. The DynamoDB Streams data can be used to replicate data in near real-time across different AWS accounts. The approach allows for minimal administrative work as it only requires the creation of two Lambda functions to read and write to S3 and DynamoDB tables, respectively. This approach also ensures that data consistency is maintained during the migration process.

https://aws.amazon.com/premiumsupport/knowledge-center/dynamodb-cross-account-migration/ . I initially thought answer was 'A' since answer had the word 'existing blueprint' . but , I went for C based on the link pasted above. Scroll to the 'Data Pipeline' section in there .

DATAPIEPLINE is the correct one "Note: The destination account can't access the DynamoDB data in S3 bucket. To work with the data, restore it to a DynamoDB table. Data Pipeline provides the easiest method to move the table with the least manual effort. However, there are fewer options for customization."

https://aws.amazon.com/premiumsupport/knowledge-center/dynamodb-cross-account-migration/ export dynamoDB to S3 in other account -> use Glue job (or data pipeline or EMR) to import data C. Use AWS Data Pipeline in the current account to export the data from the DynamoDB table to a file in Amazon S3. Use Data Pipeline to import the data from the S3 file to a DynamoDB table in the new account.

Why not A? being glue serverless wouldn't it be easier to do this way?

Agree with C, LEAST amount of work.

I agree with C and also that the question is a bit ambigupus

C https://aws.amazon.com/premiumsupport/knowledge-center/data-pipeline-account-access-dynamodb-s3/

A seems to be the answer. https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-dynamo-db-cross-account.html