Cost-Effective NFS Backup to Amazon S3

SAA-C03 By islever Editorial Last updated

Design cost-optimized storage solutions.

Short answer

B Set up an AWS DataSync agent on the on-premises servers, and sync the data to Amazon S3.

Question

A company has NFS servers in an on-premises data center that need to periodically back up small amounts of data to Amazon S3. Which solution meets these requirements and is MOST cost-effective?
  1. Set up AWS Glue to copy the data from the on-premises servers to Amazon S3.
  2. Set up an AWS DataSync agent on the on-premises servers, and sync the data to Amazon S3. Correct Answer
  3. Set up an SFTP sync using AWS Transfer for SFTP to sync data from on premises to Amazon S3.
  4. Set up an AWS Direct Connect connection between the on-premises data center and a VPC, and copy the data to Amazon S3.

Key Takeaways

The question tests selection of data transfer tools based on volume and frequency; the trap is choosing high-overhead services like Glue or expensive infrastructure like Direct Connect for simple file replication.

AWS DataSync is the most cost-effective solution for periodically backing up small amounts of data from on-premises NFS servers to Amazon S3, avoiding the overhead of ETL or dedicated network links.

Common mistake: Candidates often select AWS Direct Connect (D) believing a dedicated link is required for reliability, or AWS Glue (A) confusing data ingestion with file synchronization, missing the cost implications for 'small' periodic backups.

Expert Analysis

Why the Answer Is Correct

AWS DataSync is purpose-built for automating data movement between on-premises storage and AWS services like S3. It optimizes transfers by using block-level changes and parallelism, making it ideal for periodic backups. For 'small amounts of data,' the managed service incurs minimal cost compared to provisioning dedicated hardware or complex pipelines.

Why the Other Options Are Wrong

AWS Glue (A) is an ETL service designed for transforming large datasets, not simple file copying, making it overkill and inefficient for this use case. AWS Transfer for SFTP (C) requires managing server instances and is generally more expensive and less automated than DataSync for scheduled syncs. Direct Connect (D) involves significant setup costs and monthly fees, which are unjustified for transferring small volumes of data periodically.

Community Comment Notes

The community consensus strongly favors option B. As user BillaRanga noted, options A, C, and D are either 'overkill' or have 'high setup cost' for the described scenario. Users Andy_09, Scheldon, and Darshan07 also confirmed that DataSync is the correct choice for this specific requirement.

Official Reference

https://aws.amazon.com/datasync/

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

Exam Strategy

Always evaluate the scale ('small amounts') and frequency ('periodically') when selecting data transfer solutions. Prefer managed services like DataSync for file replication over custom scripts or heavy infrastructure like Direct Connect unless bandwidth or latency requirements dictate otherwise.

Frequently Asked Questions

Why is AWS Glue inappropriate for NFS backup?

Glue is an ETL tool for transforming structured/semi-structured data, not for simple file replication. It adds unnecessary complexity and cost for syncing files.

When should I use Direct Connect instead of DataSync?

Use Direct Connect when you need consistent, high-throughput connectivity for large-scale data migration or hybrid cloud applications, not for small periodic backups.

More SAA-C03 FAQ →

Community Votes

B
100%

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

Discussion 3 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 3

  1. BillaRanga 👍 9 Answered B
    A -> Used for ETL not copying B -> Works C -> Works, but overkill for the described scenario of periodic small backups, high cost D -> Works but it may not be necessary for transferring small amounts of data periodically. High setup cost
  2. Andy_09 👍 9
    B is the correct option
  3. Scheldon 👍 2 Answered B
    AnswerB Should be sufficient

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.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide