Move the NAS share to EFS for immediate content updates and ship 200 TB with Snowball Edge
A company is migrating its blog platform to AWS. The company's on-premises servers connect to AWS through an AWS Site-to-Site VPN connection. The blog content is updated several times a day by multiple authors and is served from a file share on a network-attached storage (NAS) server. The company needs to migrate the blog platform without delaying the content updates. The company has deployed Amazon EC2 instances across multiple Availability Zones to run the blog platform behind an Application Load Balancer. The company also needs to move 200 TB of archival data from its on-premises servers to Amazon S3 as soon as possible. Which combination of stops will meet these requirements? (Choose two.)
Community Votes
100% of anonymous learners picked answer CD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
EFS can be mounted from both the on-premises servers and the EC2 instances, so the same copy of the content serves both sides and author updates are visible immediately rather than on a sync schedule, and 200 TB is far beyond what a network transfer over the existing VPN link can move in reasonable time.
A blog platform is served from a NAS file share that multiple authors update several times a day, the on-premises servers reach AWS over a Site-to-Site VPN, and the EC2 instances already run the platform across Availability Zones behind an ALB. Separately, 200 TB of archival data must move to S3 as soon as possible.
Keeping the on-premises NAS as the source of truth and syncing it to the EC2 instances on a schedule. A weekly or periodic sync means the content served from AWS lags behind the authors' updates, which is exactly the delay the requirement forbids, and it also leaves two systems to operate.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The content requirement is that updates must not be delayed, and the existing architecture has the NAS server on premises as the source of truth. Amazon EFS removes that dependency: the blog data is copied once into the EFS file system, the on-premises servers mount EFS so authors keep writing to the same location, and the EC2 instances mount the same EFS file system to serve the content. Any write is immediately visible to the servers serving it because there is only one copy, and the existing Site-to-Site VPN provides the path for the on-premises mounts. For the 200 TB of archival data, an AWS Snowball Edge Storage Optimized device moves the data physically in a fraction of the time a network transfer would take, and the device is shipped to AWS for import into S3.Why the Other Options Are Wrong
A: A weekly cron job means the EC2 instances serve content that is up to a week old, which directly violates the requirement not to delay content updates, and the multiple authors would be writing to two different systems. B: An EBS Multi-Attach volume gives shared block storage to the EC2 instances, but it does not solve the on-premises side, and writing custom code to synchronise an EBS volume with the NAS server weekly reintroduces the same delayed-update problem that the requirement rules out. E: Snowcone is a small portable device intended for edge compute and modest data volumes, and it is not sized for 200 TB, so it cannot move the archival data in a reasonable timeframe.Community Comment Notes
The community voted 100 to 0 for C and D, with the top comment linking the AWS announcement for the Snow family multi-petabyte data migration devices and noting the Snowball Edge Storage Optimized capacity. A commenter pointed out that Snowcone is discontinued and another explained why A and B fail, since the NAS server is not migrated and any weekly sync means stale content on the AWS side.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →