Which option meets these requirements?
Create a DynamoDB global table to replicate data between us-east-1 and eu-west-1. Enable continuous backup on the DynamoDB table in us-east-1. Enable versioning on the S3 bucket.
Create an AWS Lambda function triggered by Amazon CloudWatch Events to make regular backups of the DynamoDB table. Set up S3 cross-region replication from us-east-1 to eu-west-1. Set up MFA delete on the S3 bucket in us-east-1.
Create a DynamoDB global table to replicate data between us-east-1 and eu-west-1. Enable versioning on the S3 bucket. Implement strict ACLs on the S3 bucket.
Create a DynamoDB global table to replicate data between us-east-1 and eu-west-1. Enable continuous backup on the DynamoDB table in us-east-1. Set up S3 cross-region replication from us-east-1 to eu-west-1.
Explanations:
While creating a DynamoDB global table and enabling continuous backup protects against data loss, it does not address cross-region replication of S3 data. Versioning helps in data recovery but does not prevent loss of connectivity to the region.
This option relies on manual backups of DynamoDB, which could lead to data inconsistency and loss. S3 cross-region replication provides redundancy for S3 objects but does not ensure continuous data availability in DynamoDB, nor does it guarantee data integrity.
Creating a global table ensures replication of DynamoDB data, and versioning on the S3 bucket protects against accidental deletions, but strict ACLs do not provide redundancy or data recovery. This option lacks cross-region replication for S3.
This option implements a DynamoDB global table for data replication, enabling continuous backup for added protection against data loss. Additionally, it includes S3 cross-region replication, ensuring that data is preserved and accessible in both regions, addressing both connectivity and data corruption concerns.