Question #860
A company is migrating a logging application to the AWS Cloud. The application runs in an on-premises data center and writes thousands of log files into a mounted NFS file system daily. After migration, the company will host the application on an Amazon EC2 instance with a mounted Amazon Elastic File System (Amazon EFS) file system. The company uses AWS Direct Connect. Before the migration cutover, a solutions architect must create a process to replicate newly generated on-premises log files to the EFS file system. What is the MOST operationally efficient way to replicate the logs?
Configure a periodic process to run the aws s3 sync command from the on-premises file system to Amazon S3. Use an AWS Lambda function triggered by S3 event notifications to copy the logs from Amazon S3 to the EFS file system.
Deploy an AWS Storage Gateway file gateway with an NFS mount point. Mount the file gateway file system on the on-premises server. Schedule a process to periodically copy the logs to the mount point.
Deploy an AWS DataSync agent to an on-premises server with access to the NFS file system. Transfer data over the Direct Connect connection to an S3 bucket using a public VIF. Use an AWS Lambda function triggered by S3 events to copy the logs from Amazon S3 to the EFS file system.
Deploy an AWS DataSync agent to an on-premises server with access to the NFS file system. Transfer data over the Direct Connect connection to an AWS PrivateLink interface VPC endpoint for Amazon EFS using a private VIF. Configure a DataSync scheduled task to replicate the logs to the EFS file system every 24 hours.
Explanation
Option D is correct because it leverages AWS DataSync, which is purpose-built for transferring large datasets between on-premises and AWS storage services. By deploying a DataSync agent on-premises and configuring a scheduled task, logs are replicated directly to EFS over AWS Direct Connect using a private VIF, ensuring secure and fast transfers. This approach minimizes operational complexity by avoiding intermediate steps (e.g., S3 and Lambda in Options A/C) and integrates seamlessly with EFS. DataSync also supports incremental transfers and scheduling, aligning with the requirement to replicate logs periodically. Other options introduce unnecessary layers: Option A/B involve S3 and Lambda (added complexity), while Option C uses a public VIF, which is less secure. Option D's use of AWS PrivateLink via a private VIF ensures data remains within the AWS network, enhancing security and efficiency.
Answer
The correct answer is: D