A company wants to migrate an on-premises data center to AWS. The data center hosts an SFTP server that stores its data on an NFS-based file system. The server holds 200 GB of data that needs to be transferred. The server must be hosted on an Amazon EC2 instance that uses an Amazon Elastic File System (Amazon EFS) file system.
Which combination of steps should a solutions architect take to automate this task? (Choose two.)
To automate the migration of an on-premises data center hosting an SFTP server to AWS, two key steps need to be taken. First, installing an AWS DataSync agent in the on-premises data center is essential. This agent facilitates the transfer of data from the on-premises location to AWS efficiently and with minimal manual intervention. Second, using AWS DataSync to create a suitable location configuration for the on-premises SFTP server is necessary. This configuration ensures that DataSync knows where the data resides on the on-premises NFS-based file system, enabling it to transfer the data to the Amazon EC2 instance using the Amazon EFS file system seamlessly and automatically. These steps together harness the automation capabilities of AWS DataSync to complete the migration process effectively.
Answer and HOW-TO B. Install an AWS DataSync agent in the on-premises data center. E. Use AWS DataSync to create a suitable location configuration for the on-premises SFTP server. To automate the process of transferring the data from the on-premises SFTP server to an EC2 instance with an EFS file system, you can use AWS DataSync. AWS DataSync is a fully managed data transfer service that simplifies, automates, and accelerates transferring data between on-premises storage systems and Amazon S3, Amazon EFS, or Amazon FSx for Windows File Server. To use AWS DataSync for this task, you should first install an AWS DataSync agent in the on-premises data center. This agent is a lightweight software application that you install on your on-premises data source. The agent communicates with the AWS DataSync service to transfer data between the data source and target locations.
Next, you should use AWS DataSync to create a suitable location configuration for the on-premises SFTP server. A location represents a data source or a data destination in an AWS DataSync task. You can create a location for the on-premises SFTP server by specifying the IP address, the path to the data, and the necessary credentials to access the data. Once you have created the location configuration for the on-premises SFTP server, you can use AWS DataSync to transfer the data to the EC2 instance with the EFS file system. AWS DataSync handles the data transfer process automatically and efficiently, transferring the data at high speeds and minimizing downtime.
Explanation of other options A. Launch the EC2 instance into the same Availability Zone as the EFS file system. This option is not wrong, but it is not directly related to automating the process of transferring the data from the on-premises SFTP server to the EC2 instance with the EFS file system. Launching the EC2 instance into the same Availability Zone as the EFS file system can improve the performance and reliability of the file system, as it reduces the latency between the EC2 instance and the file system. However, it is not necessary for automating the data transfer process.
C. Create a secondary Amazon Elastic Block Store (Amazon EBS) volume on the EC2 instance for the data. This option is incorrect because Amazon EBS is a block-level storage service that is designed for use with Amazon EC2 instances. It is not suitable for storing large amounts of data that need to be accessed by multiple EC2 instances, like in the case of the NFS-based file system on the on-premises SFTP server. Instead, you should use Amazon EFS, which is a fully managed, scalable, and distributed file system that can be accessed by multiple EC2 instances concurrently.
D. Manually use an operating system copy command to push the data to the EC2 instance. This option is not wrong, but it is not the most efficient or automated way to transfer the data from the on-premises SFTP server to the EC2 instance with the EFS file system. Manually transferring the data using an operating system copy command would require manual intervention and would not scale well for large amounts of data. It would also not provide the same level of performance and reliability as a fully managed service like AWS DataSync.
**A**. Launch the EC2 instance into the same Availability Zone as the EFS file system. Makes sense to have the instance in the same AZ the EFS storage is. **B**. Install an AWS DataSync agent in the on-premises data center. The DataSync with move the data to the EFS, which already uses the EC2 instance (see the info provided). No more things are required... C. Create a secondary Amazon Elastic Block Store (Amazon EBS) volume on the EC2 instance for the data. This secondary EBS volume isn't required... the data should be move on to EFS... D. Manually use an operating system copy command to push the data to the EC2 instance. Potentially possible (instead of A), BUT the "automate this task" premise goes against any "manually" action. So, we should keep A. E. Use AWS DataSync to create a suitable location configuration for the on-premises SFTP server. I don't get the relationship between DataSync and the configuration for SFTP "on-prem"! Nonsense. So, anwers are A&B
E is correct https://aws.amazon.com/blogs/storage/migrating-storage-with-aws-datasync/
Use AWS Transfer Family instead of DataSync for SFTP. So E seems incorrect. When do I use AWS DataSync and when do I use AWS Transfer Family? A: If you currently use SFTP to exchange data with third parties, AWS Transfer Family provides a fully managed SFTP, FTPS, FTP, and AS2 transfer directly into and out of Amazon S3, while reducing your operational burden. If you want an accelerated and automated data transfer between NFS servers, SMB file shares, Hadoop clusters, self-managed or cloud object storage, AWS Snowcone, Amazon S3, Amazon EFS, and Amazon FSx, you can use AWS DataSync. DataSync is ideal for customers who need online migrations for active data sets, timely transfers for continuously generated data, or replication for business continuity.
will A,B work without E?
CORRECT ANSWER: B&E Steps 4 &5 https://aws.amazon.com/datasync/getting-started/?nc1=h_ls
Just go to AWS Console, to DataSync and choose "Create Location Configuration". Locations configurations are endpoints used in DataSync task. A location can be the source endpoint of the task, e.g. a NFS on-premise filesystem. So E is helping in the automation process. A is not even part of this automation process, it is a solution already agreed to have EC2 with EFS, how you connect EC2 to EFS is not part of the solution!
the questions says combinations of two steps, so AB makes more sense
Apparently it's not B, as it says: "Install" an AWS DataSync agent in the on-premises data center. You actually don't install it. You deploy it as a vm or EC2. So I guess it's the terminology that hints at "E"
B and E is the most logical solution, launching the instance in the same AZ as the EFS is not cruicial, C and D negate the automation part and the part where it says that we need to use EFS.
I don't think E is correct. You create an EC2, and DataSync to migrate the NFS to EFS. That's it. You don't need to migrate anything on the on-presmise sftp server
A could be the right choice but here have to choose 2 options so alone with AB and with E it won't work so correct combination is BE
BE for sure
did think AB and now im thinking B and E. the questions and answers seem a bit vague like something is missing but have a look at the info on the AWS page. Use Datasync for migrations between NFS servers. Q: When do I use AWS DataSync and when do I use AWS Transfer Family? A: If you currently use SFTP to exchange data with third parties, AWS Transfer Family provides a fully managed SFTP, FTPS, FTP, and AS2 transfer directly into and out of Amazon S3, while reducing your operational burden. If you want an accelerated and automated data transfer between NFS servers, SMB file shares, Hadoop clusters, self-managed or cloud object storage, AWS Snowcone, Amazon S3, Amazon EFS, and Amazon FSx, you can use AWS DataSync. DataSync is ideal for customers who need online migrations for active data sets, timely transfers for continuously generated data, or replication for business continuity.
AWS DataSync does not support SFTP
The most appropriate combination of steps to automate the task of migrating the on-premises SFTP server to an Amazon EC2 instance using Amazon EFS is: A. Launch the EC2 instance into the same Availability Zone as the EFS file system. E. Use AWS DataSync to create a suitable location configuration for the on-premises SFTP server. Explanation: A. Launching the EC2 instance into the same Availability Zone as the EFS file system ensures optimal performance and low-latency access to the file system. E. AWS DataSync can be used to automate and accelerate the transfer of data between on-premises systems and AWS. Creating a suitable location configuration for the on-premises SFTP server with AWS DataSync facilitates the migration process. Therefore, options A and E together provide an efficient and automated approach to migrate the data.
My choice is B and E. Data Sync is used to transfer data between on-premises and AWS. It is required to deploy AWS Data Sync Agent in on-premises and configure the location FROM/TO in AWS Data Sync.
***The question is confusing and misleading!!!*** This part of question remains unanswered: "The server must be hosted on an Amazon EC2 instance that uses an Amazon Elastic File System (Amazon EFS) file system" and A doesn't actually make sense. BE doesn't fulfil this requirement. AB doesn't work without a location. I think something is missing in the dump
It's already given EC2 with EFS opted for the solution. Which combination of steps should a solutions architect take to automate this task? BE
Are you saying the question is about automating the transfer and not migrating the SFTP server?
Correct answer BE A is not correct. EFS is region specific not AZ
BE is correct
Data Sync is agent based solution that allows to transfer between on-premises NFS/SMB shares and AWS, between AWS storage services and between different Clouds. it supports EFS,S3, and Fsx.. it requires an agent installation on-prem