A photo platform stores 500 TB in us-east-1 S3 with only a curated /published/ prefix needed in eu-west-1 for local reads. It must keep EU latency low while cutting cross-Region transfer and storage spend. Which replication control provides cost-aware multi-Region access for this filtered dataset?
Select an answer to reveal the explanation.
Short Explanation
You don’t need to ship the whole warehouse when Europe only needs one curated shelf. Prefix filtering replicates just the published photos, reducing transfer and storage costs while keeping reads close to EU users.
Full Explanation
S3 Cross-Region Replication with a /published/ prefix filter copies only the curated photos that EU readers need, avoiding the transfer and storage costs of replicating the other objects while keeping the required data in eu-west-1 for low-latency reads. Replicating the entire bucket to mirrored storage would also serve EU readers quickly, but it would copy raw and intermediate objects that are not needed there, increasing spend. DynamoDB global tables replicate DynamoDB tables, not S3 photo objects, so they do not provide the required access to this dataset. S3 Batch Replication daily for all objects would copy unnecessary data and would not provide the intended filtered, ongoing replication. Exam caveat: live replication applies to eligible new objects; existing /published/ objects may need a one-time batch replication. Practical check: verify the prefix filter, destination bucket permissions, and replication status before relying on EU reads.