A media company is closing a remote production studio and must move 600 TB of archived video from an on-premises NAS into Amazon S3. The studio site has a single 50 Mbps internet link that the facilities team needs for daily operations, and the migration must finish within four weeks without saturating that link. The data is then deleted from the NAS. Which transfer mechanism MOST appropriately meets the deadline and the link constraint?
- ADeploy an AWS DataSync agent on the studio network and schedule transfer tasks during off-hours to push the archive over the existing 50 Mbps internet link into the destination S3 bucket.
- BEnable Amazon S3 Transfer Acceleration on the destination bucket and use the multipart upload API from the studio so the archive routes over the optimised CloudFront edge path into S3.
- COrder multiple AWS Snowball Edge devices, copy the archive locally over the studio LAN, and ship them to AWS for ingestion into S3 so the migration never touches the internet link. Correct
- DSet up AWS Transfer Family with an SFTP endpoint backed by the bucket and have the studio scripts upload the archive to that managed endpoint over the public internet connection.
Why A is wrong: DataSync optimises and parallelises transfers, but 600 TB over a 50 Mbps link would take far longer than four weeks and would still compete for the bandwidth facilities relies on.
Why B is wrong: Transfer Acceleration improves long-distance throughput per connection but is still capped by the 50 Mbps origin link, so it cannot deliver 600 TB in four weeks and competes for bandwidth.
Why C is correct: Snowball Edge moves bulk data offline at LAN speed and ships physically, completing a 600 TB transfer within the deadline while leaving the 50 Mbps link untouched for operations.
Why D is wrong: Transfer Family exposes a managed SFTP front door for ongoing exchange, but it still sends bytes over the same constrained 50 Mbps link and adds nothing to bulk migration speed.