Migrating 70 TB On-Premises NFS Data to Amazon S3
A company uses NFS to store large video files in on-premises network attached storage. Each video file ranges in size from 1 MB to 500 GB. The total storage is 70 TB and is no longer growing. The company decides to migrate the video files to Amazon S3. The company must migrate the video files as soon as possible while using the least possible network bandwidth. Which solution will meet these requirements?
Community Insight
The key constraints are migrating 70 TB as fast as possible with the least network bandwidth; the common trap is choosing an S3 File Gateway approach that still pushes all 70 TB over the network, or failing to account for Direct Connect provisioning delays of 1–2 months.
This question tests choosing the optimal data migration method to Amazon S3 for 70 TB of static video files when speed and minimal network bandwidth are required. AWS Snowball Edge is the correct answer because it physically transports data off-premises, avoiding network bandwidth entirely.
Choosing option C (S3 File Gateway with a public endpoint) or option D (Direct Connect with S3 File Gateway). Learners often think File Gateway avoids network usage, but it still transfers all 70 TB over the network. Option D adds weeks of Direct Connect provisioning time, failing the 'as soon as possible' requirement.
Community Discussion (201 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option B (AWS Snowball Edge) is the correct answer. Snowball Edge devices provide up to ~80 TB of usable storage per job, making 70 TB a standard use case. The data is copied locally onto the physical device and shipped back to AWS for import into S3 — meaning zero network bandwidth is consumed for the migration itself. The entire process typically completes in 6–9 working days, making it both the fastest and least bandwidth-intensive option. The fact that total storage is 'no longer growing' is a deliberate signal that Snowball Edge's fixed capacity is sufficient and ideal.
Why the Other Options Are Wrong
Option A uses the AWS CLI to upload 70 TB directly to S3 over the internet, consuming the full 70 TB of network bandwidth and taking weeks depending on connection speed — violating both requirements. Option C deploys an S3 File Gateway but transfers data over a public service endpoint, still pushing all 70 TB through the network; it does not reduce bandwidth usage. Option D adds Direct Connect, which typically takes 1–2 months to provision, making it the slowest option despite the dedicated bandwidth; the long provisioning time fails the 'as soon as possible' requirement.
Community Comment Notes
Gatt's analysis is the most thorough, calculating that Snowball Edge transfers 70 TB in under 2 hours locally and completes in 6–9 working days including shipping — far faster than network-based approaches. LuckyAro and th3cookie correctly identify that Direct Connect can take weeks to provision, invalidating option D. PhucVuu's breakdown correctly marks B as the answer because it uses no network bandwidth at all. The dissenting view from Uncolored8034 arguing for C is incorrect: Snowball Edge does not consume network bandwidth — the data is physically shipped, which is precisely why it satisfies the 'least possible network bandwidth' requirement.
Official Reference
Exam Strategy
When a question specifies a large static dataset with 'no longer growing' and demands minimal network bandwidth, immediately look for AWS Snowball Edge as the answer. Also watch for Direct Connect options — the long provisioning lead time (weeks to months) almost always makes DX the wrong choice for 'as soon as possible' migrations.
Frequently Asked Questions
Why doesn't S3 File Gateway count as using the least possible network bandwidth?
S3 File Gateway still transfers all 70 TB of data over the network (internet or Direct Connect) to reach S3. Unlike Snowball Edge, which physically ships data on a device, File Gateway relies entirely on network connectivity.
How long does Direct Connect provisioning take and why does it matter here?
Direct Connect typically takes 4–8 weeks to provision a new physical connection. Since the question requires migrating 'as soon as possible,' the long setup time makes Direct Connect unsuitable compared to Snowball Edge's 6–9 day timeline.
Can Snowball Edge handle files up to 500 GB?
Yes. Snowball Edge devices support large individual files well beyond 500 GB. The device capacity per job is approximately 80 TB, easily accommodating the 70 TB total dataset in this scenario.
Related Analysis
Practice All SAA-C03 Questions
Access 120 questions with complete answers and detailed explanations.
View Full SAA-C03 Practice Test →