Q20 — AWS DOP-C02 Ch.2

Question 20 of 100 | ← Chapter 2

A company deploys an application across multiple AWS Regions. The application creates and stores artifacts in an Amazon S3 bucket located in the same Region as the application. All deployments of the application require access to artifacts and associated metadata from every Region. The company has configured bidirectional replication between S3 buckets and enabled S3 Replication Metrics on each bucket. If an object fails to replicate, developers must implement a solution that retries the replication process.

• A. Create an Amazon EventBridge rule to listen for S3 event notifications of failed replication events. Create an AWS Lambda function that downloads the failed replication object and then runs the aws s3 cp command to the destination bucket. Configure the EventBridge rule to invoke the Lambda function to handle unrepliable objects.
• B. Create an Amazon Simple Queue Service (SQS) queue. Configure S3 event notifications to send failed replication notifications to the SQS queue. Create an AWS Lambda function that downloads the failed replication object and then runs the aws s3 cp command to the destination bucket. Configure the Lambda function to poll the queue to process notifications.
• C. Create an Amazon EventBridge rule that listens for S3 event notifications of failed replication. Create an AWS Lambda function that downloads the failed replication object and then runs the aws s3 cp command to the destination bucket.
• D. Use S3 Batch Operations to retry replication on existing objects that failed. Configure S3 event notifications to send failed replication notifications to a Lambda function. ✓

Correct Answer: D. Use S3 Batch Operations to retry replication on existing objects that failed. Configure S3 event notifications to send failed replication notifications to a Lambda function.

Explanation

For S3 replication failures, S3 Batch Operations is designed to re-execute replication tasks at scale. AWS documentation states that S3 Batch Operations is suitable for large-scale operations on existing objects, such as re-replicating. Option D uses S3 event notifications to forward failure events to Lambda, which then invokes S3 Batch Operations — directly leveraging S3’s native replication logic without manual object handling. Other options rely on Lambda downloading and uploading objects, risking loss of metadata or incorrect version handling, whereas Batch Operations integrates natively with S3 replication, ensuring consistency.