A retailer wants to configure Cross-Region Replication (CRR) from its orders bucket in eu-west-1 to a backup bucket in eu-central-1. The source bucket already has versioning enabled. What else must be true for the replication configuration to succeed?
- Nothing further is required; only the source bucket needs versioning enabled
- The destination bucket must also have versioning enabled
- The destination bucket must be in the same AWS account as the source bucket
- The source bucket must first be converted to a Requester Pays bucket
Correct answer: B. The destination bucket must also have versioning enabled
AWS documentation on replication requirements states plainly that both the source and destination buckets must have versioning enabled before a replication configuration can be created; if the destination bucket does not have versioning enabled, the replication configuration will not succeed. This makes the second option correct and the first option incorrect, since versioning on the source alone is not sufficient. Cross-account replication is explicitly supported by S3 as long as the destination bucket owner grants the source account permission through a bucket policy, so replication does not require both buckets to belong to the same account, making the third option wrong. Requester Pays is unrelated to enabling replication on the source side; in fact, AWS documentation notes that in a cross-account scenario the destination bucket specifically cannot be configured as Requester Pays, but nothing requires the source bucket to become Requester Pays, making the fourth option incorrect.
Source: AWS S3 documentation: Requirements and considerations for replication — versioning must be enabled on both source and destination buckets