A hospital group must keep a second, independent copy of every object written to its records bucket, purely for internal redundancy and faster local access by a separate analytics team in the same country, and has no requirement to store any copy in a different AWS Region. Which S3 Replication configuration fits this requirement without introducing cross-Region data transfer?
- Cross-Region Replication (CRR) to a bucket in a neighbouring Region
- S3 Transfer Acceleration between the two buckets
- S3 Object Lock replication rules, which are Region-independent
- Same-Region Replication (SRR) to a second bucket within the same AWS Region
Why D? And why not the others?
Correct answer: D. Same-Region Replication (SRR) to a second bucket within the same AWS Region
Same-Region Replication (SRR) creates a second copy of objects in a different bucket within the same AWS Region as the source, which fits a requirement for redundancy and faster local access without any data ever leaving the Region, unlike Cross-Region Replication, which by definition copies data into a different Region and does not fit a same-country, no-cross-Region requirement. Transfer Acceleration only optimises the speed of client uploads and downloads over long distances using CloudFront edge locations; it does not create a second persistent copy of the data at all. Object Lock only prevents deletion or modification of objects during a retention period and has no replication mechanism of its own; whether Region-independent or not, it does not copy data anywhere.
Source: AWS S3 docs: Replicating objects within the same AWS Region