A finance company hosts a data lake in Amazon S3. The company receives financial data records over SFTP each night from several third parties. The company runs its own SFTP server on an Amazon EC2 ins

Question

Options

• AMove the EC2 instance into an Auto Scaling group.
• BMigrate the SFTP server to AWS Transfer for SFTP.
• CMigrate the SFTP server to a file gateway in AWS Storage Gateway.
• DPlace the EC2 instance behind a Network Load Balancer (NLB).

• A
  15% (5)
• B
  71% (24)
• C
  6% (2)
• D
  9% (3)

Explanation

AWS Transfer for SFTP (option B) is a fully managed service that handles SFTP natively, scales automatically without any EC2 management, and integrates directly with S3 - eliminating the cron job entirely and making the solution both more reliable and more scalable out of the box.

Option A (Auto Scaling group) doesn't work well for SFTP because SFTP sessions are stateful; scaling EC2 instances horizontally doesn't cleanly handle active connections, and you'd still need to manage the server software and cron job yourself.

Option D (NLB) improves availability slightly but doesn't address scalability of the underlying EC2 instance or the operational burden of managing the SFTP server and file-moving logic - it's a band-aid, not a solution.

Option C (Storage Gateway file gateway) is designed for on-premises systems to access S3 over NFS/SMB, not for hosting an internet-facing SFTP endpoint for third parties.

Memory tip: When you see "self-managed server on EC2" paired with a request for reliability/scalability, look for the AWS-managed equivalent service first - AWS Transfer for SFTP is that managed equivalent, and it writes directly to S3 without any glue code.

No community discussion yet for this question.