Question #1121
A company is migrating an on-premises FTP server to AWS. The server uses an NFS-based file system with 200 GB of data. The new setup requires hosting the server on an Amazon EC2 instance connected to an Amazon Elastic File System (EFS). Which combination of steps should a solutions architect take to automate this migration? (Choose two.)
Deploy the EC2 instance in the same Availability Zone as the EFS file system.
Configure an AWS DataSync agent on the on-premises server.
Attach a secondary Amazon Elastic Block Store (EBS) volume to the EC2 instance for data storage.
Transfer the data manually using a command-line utility like scp.
Set up an AWS DataSync location configuration for the on-premises FTP server.
Explanation
The correct answers are B and E. Here's why:
- B (Configure DataSync agent): AWS DataSync requires an agent to be installed on-premises to securely transfer data to AWS services like EFS. This automates the migration process.
- E (Set up DataSync location): DataSync needs a source location configuration pointing to the on-premises FTP server to initiate the transfer.
Why others are incorrect:
- A: EFS is accessible across Availability Zones, so EC2 placement in the same AZ isn't required.
- C: EFS is the target storage, not EBS.
- D: Manual transfers (e.g., scp) don't meet the automation requirement.
Key Points:
1. Use AWS DataSync for automated, fast data transfers between on-premises and AWS.
2. DataSync requires an agent on-premises and proper location configurations.
3. EFS is multi-AZ, eliminating the need for EC2 co-location.
Answer
The correct answer is: BE