Move the NAS share to EFS for immediate content updates and ship 200 TB with Snowball Edge

SAP-C02 By islever Editorial Last updated

Determine the optimal migration approach for existing workloads. Select existing workloads and processes for potential migration. Determine a new architecture for existing workloads.

Short answer

CD Mount EFS from both on-premises and EC2, and move the 200 TB of archival data with a Snowball Edge Storage Optimized device.

Question

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.)
  1. Create a weekly cron job in Amazon EventBridge. Use the cron job to invoke an AWS Lambda function to update the EC2 instances from the NAS server.
  2. Configure an Amazon Elastic Block Store (Amazon EBS) Multi-Attach volume for the EC2 instances to share for content access. Write code to synchronize the EBS volume with the NAS server weekly.
  3. Mount an Amazon Elastic File System (Amazon EFS) file system to the on-premises servers to act as the NAS server. Copy the blog data to the EFS file system. Mount the EFS file system to the C2 instances to serve the content. Correct Answer
  4. Order an AWS Snowball Edge Storage Optimized device. Copy the static data artifacts to the device. Ship the device to AWS. Correct Answer
  5. Order an AWS Snowcons SSD device. Copy the static data artifacts to the device. Ship the device to AWS.

Key Takeaways

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.

Common mistake: 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.

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

https://docs.aws.amazon.com/efs/latest/ug/efs-on-prem.html

This link opens the official vendor documentation in a new tab.

Community Votes

CD
100%

100% of anonymous learners picked answer CD. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 6 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 6

  1. AhmedSalem 👍 3
    Answer is CD C. EFS provides a scalable, shared file storage that can be accessed by both on-premises servers and EC2 instances. This ensures that updates to the content are immediately available to the blog platform without the need for synchronization. D. Snowball Edge is designed for large-scale data transfers, providing an efficient way to move 200 TB of data to Amazon S3 quickly and securely.
  2. kupo777 👍 1
    A, B The NAS server has not been migrated. E AWS Snowcone does not have enough capacity. Snowball Edge Storage Optimized can handle up to 210 TB of NVMe capacity. The answers are C and D.
  3. ITguy_10 👍 1
    C & D https://aws.amazon.com/about-aws/whats-new/2023/05/aws-snow-family-multi-pb-data-migration-210tb-device/
  4. ebbff63 👍 4
    Answer CD
  5. awsaz 👍 4
    C And D
Show 1 more comment
  1. altonh 👍 1
    Snowcone is discontinued.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Modernize centralized firewall appliances with a Gateway Load Balancer and Auto Scaling

S-grade

Use Lambda over a CloudWatch Logs stream to count unique users per client

S-grade

Serve global game assets with Route 53 latency records and health checks

S-grade

Reach a cross-account S3 data lake through a gateway endpoint and an access point bucket policy

S-grade

Practice All SAP-C02 Questions

Access 85 questions with complete answers and detailed explanations.

View Full SAP-C02 Practice Test →

← Back to SAP-C02 Study Guide